Sends Slack/Teams notifications when specific fields change on configured tables.

[shivamvish160]

PR Description:

AuditFieldChangeNotifier

Description

A ServiceNow Script Include that audits changes to specific fields and sends real-time notifications to Slack or Microsoft Teams using a webhook.
It helps teams monitor important updates like priority or assignment changes without needing to check the platform.

Features

• Monitors field-level changes on any table
• Sends rich notifications to Slack/Teams
• Easy to configure via system properties
• Can be reused across multiple tables via Business Rules

---

How to Use

1. Create a System Property

• Name: x_custom.audit_notifier.webhook_url
• Value: Your Slack or Teams webhook URL

2. Create a Script Include

• Name: AuditFieldChangeNotifier
• Paste the provided Script Include code

3. Create a Business Rule

• Table: e.g. incident
• When: after update
• Add this script:

  (function executeRule(current, previous) {
      var notifier = new AuditFieldChangeNotifier();
      notifier.notifyOnFieldChange(current, previous, ['priority', 'state', 'assigned_to']);
  })(current, previous);

4. Test It

• Update one of the watched fields.
• A message should appear in your Slack/Teams channel like:

   ServiceNow — Field Update Notification
  Record: Incident INC0010001
  Description: Unable to access VPN
  • priority changed from 4 - Low → 2 - High
  • assigned_to changed from John → Alex
  

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]

Thanks @shivamvish160 for the contribution.