Prevent duplicate incidents submission

[Indra-kolge]

PR Description:

This Business rule prevents users from creating duplicate incidents within a recent time frame ( last 7 days).

When a user tries to create an incident with the same short description and caller, the system:
• Stops the new record from being created.
• Displays an info message with a clickable link to the existing incident.

This helps reduce ticket clutter and ensures users track existing issues instead of repeatedly logging new ones.

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

[Indra-kolge]

Hi @rohi-v,

Looping you in just for visibility since the PR is currently unassigned.

Thanks!

[ravichandra1998g]

Hello @Indra-kolge

Thank you for submitting.

We cannot merge it as we already have another code snippet that prevents incident creation for the same user (for the same issue) #1956

However, we appreciate the efforts you put in for this PR so I will mark this as Hactoberfest accepted so that it still counts towards your submission.