Feature/Email Regex Validation

[Dhruvyadav2000]

PR Description:

Email Validation for ServiceNow Catalog Items

Summary

Adds client-side email validation for catalog item fields with real-time feedback and submission prevention.

Changes

• onSubmit Script: Validates email before form submission
• onChange Script: Real-time validation as users type
• README: Implementation guide and usage instructions

Features

• Regex-based email format validation (user@domain.com)
• User-friendly error/success messages
• Prevents invalid form submissions
• Immediate feedback for better UX

Benefits

• Improved data quality in catalog requests
• Reduced form rejection rates
• Better user experience with instant validation

Testing Checklist

• Valid email formats accepted
• Invalid email formats rejected
• Error messages display correctly
• Form submission prevention works
• Real-time validation functions properly

Setup

Replace 'email_field_name' with actual variable name before deployment.

Pull Request Checklist

Overview

• Put an x inside of the square brackets to check each item.
• I have read and understood the CONTRIBUTING.md guidelines
• My pull request has a descriptive title that accurately reflects the changes and the description has been filled in above.
• I've included only files relevant to the changes described in the PR title and description
• I've created a new branch in my forked repository for this contribution

Code Quality

• My code is relevant to ServiceNow developers
• My code snippets expand meaningfully on official ServiceNow documentation (if applicable)
• I've disclosed use of ES2021 features (if applicable)
• I've tested my code snippets in a ServiceNow environment (where possible)

Repository Structure Compliance

• I've placed my code snippet(s) in one of the required top-level categories:
  • Core ServiceNow APIs/
  • Server-Side Components/
  • Client-Side Components/
  • Modern Development/
  • Integration/
  • Specialized Areas/
• I've used appropriate sub-categories within the top-level categories
• Each code snippet has its own folder with a descriptive name

Documentation

• I've included a README.md file for each code snippet
• The README.md includes:
  • Description of the code snippet functionality
  • Usage instructions or examples
  • Any prerequisites or dependencies
  • (Optional) Screenshots or diagrams if helpful

Restrictions

• My PR does not include XML exports of ServiceNow records
• My PR does not contain sensitive information (passwords, API keys, tokens)
• My PR does not include changes that fall outside the described scope

[Atul-LNG]

Hi @Dhruvyadav2000
I noticed that you checked three files. If you want to code the same on two different levels, I’d suggest creating two separate PRs. Also, please avoid changing the name of the README file.

[Dhruvyadav2000]

Hi @Dhruvyadav2000 I noticed that you checked three files. If you want to code the same on two different levels, I’d suggest creating two separate PRs. Also, please avoid changing the name of the README file.

Hi @Atul-LNG, sure. I will create two separate PRs as suggested and make readme file name consistent.