Merge branch 'ServiceNowDevProgram:main' into main

Author: sivamuruganandam-coder

CONTRIBUTING.md

@@ -31,10 +31,25 @@ If you plan to submit another pull request while your original is still pending,
 - **Descriptive Pull Request Titles**: Your pull request must have explicit and descriptive titles that accurately represent the changes made.
 - **Scope Adherence**: Changes that fall outside the described scope will result in the entire pull request being rejected.
 - **Quality Over Quantity**: Low-effort or spam pull requests will be marked accordingly.
-- **Expanded Snippets**: Code snippets reused from the [ServiceNow Documentation](https://docs.servicenow.com/) or [API References](https://developer.servicenow.com/dev.do#!/reference/) are acceptable only if they are expanded in a meaningful way (e.g., with additional context, documentation, or variations). Remember: *“QUANTITY IS FUN, QUALITY IS KEY.”*
+- **Expanded Snippets**: Code snippets reused from the [ServiceNow Documentation](https://docs.servicenow.com/) or [API References](https://developer.servicenow.com/dev.do#!/reference/) are acceptable only if they are expanded in a meaningful way (e.g., with additional context, documentation, or variations). Remember: *"QUANTITY IS FUN, QUALITY IS KEY."*
 - **Relevance**: Code should be relevant to ServiceNow Developers.
 - **ES2021 Compatibility**: While ES2021 is allowed, we encourage you to disclose if your code is using ES2021 features, as not everyone may be working with ES2021-enabled applications.
 
+## Core Documentation File Changes
+
+**IMPORTANT**: For changes to core documentation files (README.md, CONTRIBUTING.md, LICENSE, etc.), contributors must:
+
+1. **Submit an Issue First**: Before making any changes to core documentation files, create an issue describing:
+   - What you intend to edit
+   - Why the change is needed
+   - Your proposed approach
+
+2. **Get Assignment**: Wait to be assigned to the issue by a maintainer before submitting a PR.
+
+3. **Reference the Issue**: Include the issue number in your PR title and description.
+
+This process helps prevent merge conflicts when multiple contributors want to update the same documentation files and ensures all changes align with the project's direction.
+
 ## Repository Structure
 
 **IMPORTANT**: The repository has been reorganized into major categories. All new contributions MUST follow this structure for PR approval.

Client-Side Components/Client Scripts/Color-coded Priority field for improved UX/README.md

@@ -0,0 +1,19 @@
+# Field Color-Coding Based on Choice Values
+
+## Purpose
+Dynamically change the background color of any choice field on a form based on the selected backend value.
+
+## How to Use
+1. Create an OnChange client script on the desired choice field.
+2. Replace `'your_field_name'` in the script with your actual field name.
+3. Update the `colorMap` with relevant backend choice values and colors.
+4. Save and test on the form.
+
+## Key Points
+- Works with any choice field
+- Uses backend values of choices for mapping colors.
+
+## Demo
+
+<img width="1710" height="557" alt="image" src="https://github.com/user-attachments/assets/9fb9e68a-1ade-4eb5-81cc-c947c970bd6f" />
+

Client-Side Components/Client Scripts/Color-coded Priority field for improved UX/setColor.js

@@ -0,0 +1,15 @@
+function onChange(control, oldValue, newValue, isLoading) {
+
+  var colorMap = {
+    '1': '#e74c3c',  // Critical - strong red
+    '2': '#e67e22',  // High - bright orange
+    '3': '#f1c40f',  // Moderate - yellow
+    '4': '#3498db',  // Low - blue
+    '5': '#27ae60'   // Planning - green
+  };
+
+  var priorityField = g_form.getControl('priority');
+  if (!priorityField) return;
+
+  priorityField.style.backgroundColor = colorMap[newValue] || '';
+}

Core ServiceNow APIs/GlideAggregate/Count All Open Incidents Per Priority/readme.md

@@ -0,0 +1,21 @@
+# Count Open Incidents per Priority Using GlideAggregate
+
+## Overview
+This script dynamically calculates the **number of open incidents** for each priority level using **server-side scripting** in ServiceNow.  
+Priority levels typically include:  
++ 1 – Critical  
++ 2 – High  
++ 3 – Moderate  
++ 4 – Low  
+
+The solution leverages **GlideAggregate** to efficiently count records grouped by priority. This approach is useful for:  
++ Dashboards  
++ Automated scripts  
++ Business rules  
++ SLA monitoring and reporting  
+
+---
+
+## Table and Fields
++ **Table:** `incident`  
++ **Fields:** `priority`, `state`  

Core ServiceNow APIs/GlideAggregate/Count All Open Incidents Per Priority/script.js

@@ -0,0 +1,23 @@
+(function() {
+    // Create GlideAggregate object on 'incident' table
+    var ga = new GlideAggregate('incident');
+    
+    // Filter only open incidents (state != Closed (7))
+    ga.addQuery('state', '!=', 7);
+    
+    // Group results by priority
+    ga.groupBy('priority');
+    
+    // Count number of incidents per priority
+    ga.addAggregate('COUNT');
+    
+    ga.query();
+    
+    gs.info('Open Incidents by Priority:');
+    
+    while (ga.next()) {
+        var priority = ga.priority.getDisplayValue(); // e.g., Critical, High
+        var count = ga.getAggregate('COUNT');
+        gs.info(priority + ': ' + count);
+    }
+})();

Core ServiceNow APIs/GlideDateTime/Find Incidents Older Than X Days/readme.md

@@ -0,0 +1,10 @@
+## Overview
+This script retrieves incidents that were opened more than X days ago using **GlideDateTime** and **GlideRecord**.  
+Useful for reporting, escalations, notifications, and cleanup tasks.
+
+## Table and Field
+- **Table:** `incident`
+- **Field:** `opened_at`
+
+## Parameters
+- **X (number of days):** Defines the threshold for old incidents (e.g., 30 days).

Core ServiceNow APIs/GlideDateTime/Find Incidents Older Than X Days/script.js

@@ -0,0 +1,18 @@
+(function() {
+    var days = 30; // Change this to your required number of days
+
+    // Calculate the date X days ago
+    var cutoffDate = new GlideDateTime();
+    cutoffDate.addDaysUTC(-days);
+
+    // Query incidents opened before the cutoff date
+    var gr = new GlideRecord('incident');
+    gr.addQuery('opened_at', '<', cutoffDate);
+    gr.query();
+
+    gs.info('Incidents opened more than ' + days + ' days ago:');
+
+    while (gr.next()) {
+        gs.info('Incident Number: ' + gr.number + ', Opened At: ' + gr.opened_at.getDisplayValue());
+    }
+})();

Core ServiceNow APIs/GlideJsonPath/Basic-Example/README.md

@@ -0,0 +1,9 @@
+# Querying JSON with JSONPath to extract values
+
+GlideJsonPath is a class which can be used to use JSONPath in ServiceNow. It can be useful when working with JSON Payloads, especially highly nested or in general complex structures.
+
+References:
+- [RFC 9535: JSONPath: Query Expressions for JSON](https://datatracker.ietf.org/doc/rfc9535/)
+- [Play with JSONPath outside of ServiceNow](https://jsonpath.com/)
+- [Good Examples to start with](https://restfulapi.net/json-jsonpath/)
+- [ServiceNow API Documentation](https://www.servicenow.com/docs/bundle/zurich-api-reference/page/app-store/dev_portal/API_reference/GlideJsonPath/concept/GlideJsonPathAPI.html)

Core ServiceNow APIs/GlideJsonPath/Basic-Example/examples.js

@@ -0,0 +1,53 @@
+// Run in background script
+var json = { 
+	"store": 
+	{
+		"book": [
+			{ 
+				"category": "reference",
+				"author": "Nigel Rees",
+				"title": "Sayings of the Century",
+				"price": 8.95
+			},
+			{ 
+				"category": "fiction",
+				"author": "Evelyn Waugh",
+				"title": "Sword of Honour",
+				"price": 12.99
+			},
+			{ 
+				"category": "fiction",
+				"author": "Herman Melville",
+				"title": "Moby Dick",
+				"isbn": "0-553-21311-3",
+				"price": 8.99
+			},
+			{ 
+				"category": "fiction",
+				"author": "J. R. R. Tolkien",
+				"title": "The Lord of the Rings",
+				"isbn": "0-395-19395-8",
+				"price": 22.99
+			}
+		],
+		"bicycle": {
+			"color": "red",
+			"price": 19.95
+		}
+	}
+};
+
+var path1 = 'store.book[0].author'; // The author of the first book
+var path2 = 'store.book[*].author'; // All authors
+var path3 = 'store..price'; // All prices
+var path4 = '$..book[?(@.price<10)]'; // All books cheaper than 10
+var path5 = '$..book[?(@.isbn)]'; // All books with an ISBN number
+var path6 = '$..*'; // All members of JSON structure
+
+var gjp = new GlideJsonPath(JSON.stringify(json));
+gs.info('Path: ' + path1 + ' Result: ' + gjp.read(path1));
+gs.info('Path: ' + path2 + ' Result: ' + gjp.read(path2));
+gs.info('Path: ' + path3 + ' Result: ' + gjp.read(path3));
+gs.info('Path: ' + path4 + ' Result: ' + gjp.read(path4));
+gs.info('Path: ' + path5 + ' Result: ' + gjp.read(path5));
+gs.info('Path: ' + path6 + ' Result: ' + gjp.read(path6));

README.md

@@ -1,9 +1,20 @@
 ![Code Snippets Banner](https://github.com/ServiceNowDevProgram/code-snippets/assets/31702109/f9fa072a-4c0c-426b-8eed-200c6616ff60)
 
+<div align="center">
+
+[![Contributions Welcome](https://img.shields.io/badge/contributions-welcome-brightgreen.svg?style=flat-square)](CONTRIBUTING.md)
+[![Hacktoberfest](https://img.shields.io/badge/Hacktoberfest-Participating-orange?style=flat-square)](https://github.com/ServiceNowDevProgram/Hacktoberfest)
+
+</div>
+
+# ServiceNow Code Snippets Repository
+
 Welcome to ServiceNow's Code Snippets community repository, managed by the Developer Program and the sndevs Slack community.
 
 Inside this repository, you will find community submitted code-snippets and their variants for different use-cases.
 
+**[📝 Contribution Guidelines](CONTRIBUTING.md)** | **[📚 Browse Categories](#repository-organization)** | **[🔍 How to Use](#how-to-use-this-repository)**
+
 > Interested in our other ServiceNow Hacktoberfest projects? See the main repository [here](https://github.com/ServiceNowDevProgram/Hacktoberfest) or see our official blog post [here](https://devlink.sn/hacktoberfest).
 
 **Note:** ServiceNowDevProgram has many repositories that can be imported directly into ServiceNow, this is not one of them; This repository is meant to be edited directly in GitHub or any other Git-enabled IDE like VS Code.
@@ -28,6 +39,25 @@ We appreciate your participation and contributions to this community-driven proj
 **_CONTRIBUTORS must follow all guidelines in [CONTRIBUTING.md](CONTRIBUTING.md)_** or run the risk of having your Pull Requests labeled as spam.<br>
 🔔🔔🔔
 
+## Table of Contents
+
+- [How to Use This Repository](#how-to-use-this-repository)
+- [Repository Organization](#repository-organization)
+- [Finding Snippets](#finding-snippets)
+- [Folder Structure](#folder-structure)
+- [Contributing](#we-invite-you-to-contribute)
+- [Disclaimer](#disclaimer)
+
+## How to Use This Repository
+
+This repository contains code snippets that you can use in your ServiceNow instance. Here's how to make the most of it:
+
+1. **Browse by Category**: Navigate through the [six major categories](#repository-organization) to find snippets relevant to your needs.
+2. **Copy and Adapt**: Once you find a useful snippet, copy the code and adapt it to your specific use case in your ServiceNow instance.
+3. **Read the Documentation**: Each snippet folder contains a README.md file that explains how the snippet works and how to implement it.
+4. **Search by Topic**: Use GitHub's search functionality to find snippets by keywords (e.g., "GlideRecord", "REST", "UI Action").
+5. **Contribute Your Own**: If you have a useful snippet, consider [contributing](#we-invite-you-to-contribute) to help others.
+
 ## Repository Organization
 
 The repository is organized into **6 major categories** that cover all aspects of ServiceNow development:
@@ -50,16 +80,65 @@ External system integrations, data import/export utilities, RESTMessageV2 exampl
 ### 🎯 [Specialized Areas](Specialized%20Areas/)
 Domain-specific functionality including CMDB utilities, ITOM scripts, Performance Analytics, ATF Steps, Agile Development tools, and other specialized use cases.
 
+## Finding Snippets
+
+There are several ways to find the snippets you need:
+
+1. **By Category**: Browse the six major categories listed above.
+2. **By Search**: Use GitHub's search functionality with keywords like:
+   - API names: `GlideRecord`, `GlideSystem`, `GlideAjax`
+   - Component types: `Business Rule`, `Client Script`, `UI Action`
+   - Functionality: `REST`, `SOAP`, `Import`, `Export`
+   - Use cases: `Authentication`, `Notification`, `Workflow`
+
+3. **By Tags**: Many snippets include common keywords in their README files that can be searched.
+
+## Folder Structure
+
+The repository follows a consistent structure to make navigation easier:
+
+```
+Top-Level Category/
+  ├── Sub-Category/
+  │   ├── Specific Snippet/
+  │   │   ├── README.md         # Description and usage instructions
+  │   │   ├── snippet_file.js   # The actual code snippet
+  │   │   └── variant.js        # Variations of the snippet (if applicable)
+```
+
+For example:
+```
+Core ServiceNow APIs/
+  ├── GlideRecord/
+  │   ├── Query Performance Optimization/
+  │   │   ├── README.md
+  │   │   ├── basic_query.js
+  │   │   └── optimized_query.js
+```
+
 ## We invite you to contribute!
 
-To contribute, just follow these steps:
+We welcome contributions from the ServiceNow developer community! Your knowledge and experience can help others solve common challenges.
+
+## 🌐 Contribute from the Web (No Setup Needed!)
+
+This repository has been approved by Hacktoberfest in spirit of learning source control and getting started in your open-source journey. You can contribute directly from your browser without needing a ServiceNow instance:
+
+1. Click **Fork** at the top-right corner of this page
+2. Open the folder where you want to add or edit a file
+3. Click **Add file → Create new file** (or edit an existing one)
+4. Scroll down, add a **commit message**, and select  
+   > "**Create a new branch for this commit and start a pull request**"
+5. Click **Propose changes → Create pull request**
+
+That's it! **For detailed contribution instructions, please read our [CONTRIBUTING.md](CONTRIBUTING.md) guide before submitting.**
 
-1. Fork this repo (you get a point just by forking!)
-2. Create a new branch on your fork
-3. Add/Update the repo
-4. Submit a pull request!
+### What makes a good contribution?
 
-That's it! More detailed contribution instructions can be found [here](CONTRIBUTING.md)
+- **Useful snippets** that solve common ServiceNow development challenges
+- **Well-documented code** with clear comments explaining how it works
+- **Proper organization** following the repository structure
+- **Variations** of snippets for different use cases when applicable
 
 ## Leaderboard