Skip to content

Conversation

@iamshankha
Copy link
Contributor

@iamshankha iamshankha commented Oct 7, 2025

PR Description:

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

Incident Auto-Tagging
Automatically detects keywords like email, VPN, or server from the incident’s short description and description.
Creates a corresponding Label (if not already present) and a Label Entry linked to that incident to fulfill the requirement of auto tagging.

Benefit:
Helps automatically tag incidents with relevant keywords, improving searchability, categorization, and visibility across the platform.

Type: Before Business Rule
Table: Incident [incident]
Incident Auto-Tagging

Automatically detects keywords like email, VPN, or server from the incident’s short description and description.
Creates a corresponding Label (if not already present) and a Label Entry linked to that incident to fulfill the requirement of auto tagging.

Benefit:
Helps automatically tag incidents with relevant keywords, improving searchability, categorization, and visibility across the platform.

Type: Before Business Rule
Table: Incident [incident]
@shreyawani98 shreyawani98 self-assigned this Oct 7, 2025
@shreyawani98
Copy link
Contributor

Hi @iamshankha

Looks good!
Thank you for your contribution.

@shreyawani98 shreyawani98 merged commit 56bf277 into ServiceNowDevProgram:main Oct 7, 2025
2 checks passed
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