Skip to content

Conversation

@vhudlikar
Copy link
Contributor

PR Description:

Validates the Goods and Services Tax Identification Number (GSTIN) used in India.

  1. It should be 15 characters long.
  2. The first 2 characters should be a number.
  3. The next 10 characters should be the PAN number of the taxpayer.
  4. The 13th character (entity code) should be a number from 1-9 or an alphabet.
  5. The 14th character should be Z.
  6. The 15th character should be an alphabet or a number.

Pull Request Checklist

Overview

  • I have read and understood the CONTRIBUTING.md guidelines
  • My pull request has a descriptive title that accurately reflects the changes
  • 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

@rohi-v rohi-v self-assigned this Oct 3, 2025
@rohi-v
Copy link
Contributor

rohi-v commented Oct 3, 2025

ThankYou for your contribution

We already have a RegexUtil Scriptinclude in our repository RegexUtils

Closing this for now. Once you make additional changes, feel free to re-open this Pull Request or create a new one.

@rohi-v rohi-v closed this Oct 3, 2025
@vhudlikar
Copy link
Contributor Author

Hi @rohi-v

Trying to understand your comment, so I need to add function under script include mentioned? As regular expression has its own folder so placed this one there. Also util is not having this check.

@rohi-v
Copy link
Contributor

rohi-v commented Oct 4, 2025

Hi @vhudlikar

We already have regexutils available with the same underlying logic. The only difference in this case is the regex expression being used, which can be provided as an input to the existing utility method.

Therefore, this appears to be just an example rather than a new enhancement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants