Merge branch 'ServiceNowDevProgram:main' into feature/bookmarklet/show-user-info/bookmarklet

Author: JohanDC-1999

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.

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));

Server-Side Components/Background Scripts/Find Top-Level Manager Hierarchy/Readme.md

@@ -0,0 +1,13 @@
+The script retrieves the top-level manager for the currently logged-in user  by traversing the manager hierarchy in the sys_user table.
+
+It starts from the current user and moves up through each manager until it reaches a user who does not have a manager.
+
+The script starts with the current user (e.g., Employee).
+
+It checks if the user has a manager.
+
+If yes, it moves up the hierarchy to the manager.
+
+It repeats this process until it reaches a user who does not have a manager.
+
+That user is considered the Top-Level Manager.

Server-Side Components/Background Scripts/Find Top-Level Manager Hierarchy/script.js

@@ -0,0 +1,25 @@
+var currentUser = gs.getUser(); // Current logged-in user
+var userGR = new GlideRecord('sys_user');
+var maxLevels = 7; 
+var currentLevel = 0;
+
+if (userGR.get(currentUser.getID())) {
+
+    // Loop until we find a user who has no manager or reach max level
+    while (userGR.manager && currentLevel < maxLevels) {
+        var managerID = userGR.getValue('manager');
+        var managerGR = new GlideRecord('sys_user');
+
+        if (managerGR.get(managerID)) {
+            userGR = managerGR; // Move up one level
+            currentLevel++;    
+			// gs.print(" Level " + currentLevel + " Manager: " + userGR.getDisplayValue('name'));
+        } else {
+            break; // Manager record not found
+        }
+    }
+
+    gs.print("Top-level (or Level " + currentLevel + ") Manager: " + userGR.getDisplayValue('name'));
+} else {
+    gs.print("User not found.");
+}

Server-Side Components/Business Rules/Captures the time it took to assign a task/README.md

@@ -0,0 +1,12 @@
+This script tracks the time it took to assign a task (like an Incident, Change, etc.) by calculating the difference
+between when the record was created and when it was assigned (assigned_to was set).
+It checks if the assigned_to field has changed and is not empty.
+If it's the first time the record is being assigned (u_assignment_time is empty), it captures the current time.
+It then calculates the time difference between when the record was created and when it was assigned.
+This time difference (in minutes) is stored in a custom field u_time_to_assign.
+The goal is to track how long it took for the record to be assigned after creation
+
+
+## While this is possible to do via Metrics in ServiceNow (https://www.servicenow.com/docs/bundle/xanadu-platform-administration/page/use/reporting/concept/c_SampleFieldValueDurationScript.html), 
+## the script is being provided to potentially solve some edge cases.
+

Server-Side Components/Business Rules/Captures the time it took to assign a task/script.js

@@ -0,0 +1,32 @@
+(function executeRule(current, previous /*null when async*/) {
+
+    // Only proceed if assigned_to changed AND is not empty/null
+    if (current.assigned_to.changes() && !gs.nil(current.assigned_to)) {
+        
+        gs.info("Assigned_to changed and assigned_to is: " + current.assigned_to);
+
+        // Only set u_assigned_time if empty
+        if (!current.u_assigned_time) {
+            
+            var assignedTime = new GlideDateTime();
+            current.u_assigned_time = assignedTime;
+
+            var createdTime = new GlideDateTime(current.sys_created_on);
+
+            var diffMillis = assignedTime.getNumericValue() - createdTime.getNumericValue();
+            var diffMinutes = diffMillis / (1000 * 60);
+
+            gs.info("Time difference in minutes: " + diffMinutes);
+
+            // Assuming u_time_to_assign is a string field
+            current.u_time_to_assign = diffMinutes.toFixed(2) + " minutes";
+            
+            gs.info("Set u_time_to_assign to: " + current.u_time_to_assign);
+        } else {
+            gs.info("u_assigned_time already set: " + current.u_assigned_time);
+        }
+    } else {
+        gs.info("Assigned_to not changed or is empty.");
+    }
+
+})(current, previous);

Server-Side Components/Business Rules/Round Robin for Incident Assignment/README.md

@@ -0,0 +1,8 @@
+UseCase - 
+
+
+
+When a new Incident is created, the system should automatically assign it to the next available member of the assignment group — in a Round Robin fashion (i.e., distributing incidents evenly among all group members).
+
+It will also work for New addition of new user. and distribute the incident equally to all the users.
+