Merge branch 'ServiceNowDevProgram:main' into main

Author: nvprav

Client-Side Components/Catalog Client Script/Multi-User Collaboration/Readme.md

@@ -0,0 +1 @@
+This project introduces a collaboration feature for Service Catalog requests, allowing multiple users to contribute to a single request. It’s ideal for scenarios like team onboarding, shared resource provisioning, or cross-functional workflows.

Client-Side Components/Catalog Client Script/Multi-User Collaboration/Script include.JS

@@ -0,0 +1,18 @@
+var CollaboratorHandler = Class.create();
+CollaboratorHandler.prototype = Object.extendsObject(AbstractAjaxProcessor, {
+  addCollaborators: function() {
+    var requestId = this.getParameter('sysparm_request_id');
+    var users = this.getParameter('sysparm_users').split(',');
+
+    users.forEach(function(userId) {
+      var gr = new GlideRecord('x_your_scope_collaborators');
+      gr.initialize();
+      gr.request = requestId;
+      gr.collaborator = userId;
+      gr.status = 'Pending';
+      gr.insert();
+    });
+
+    return 'Collaborators added successfully';
+  }
+});

Client-Side Components/Catalog Client Script/Multi-User Collaboration/client script.JS

@@ -0,0 +1,13 @@
+function onSubmit() {
+  var collaborators = g_form.getValue('collaborators'); // Multi-user reference field
+  if (collaborators) {
+    var ga = new GlideAjax('CollaboratorHandler');
+    ga.addParam('sysparm_name', 'addCollaborators');
+    ga.addParam('sysparm_request_id', g_form.getUniqueValue());
+    ga.addParam('sysparm_users', collaborators);
+    ga.getXMLAnswer(function(response) {
+      alert('Collaborators added: ' + response);
+    });
+  }
+  return true;
+}

Client-Side Components/Catalog Client Script/Multi-User Collaboration/widget client controller.JS

@@ -0,0 +1,19 @@
+function($scope, $http) {
+  $scope.approve = function(sysId) {
+    $http.post('/api/x_your_scope/collab_action', {
+      action: 'approve',
+      sys_id: sysId
+    }).then(function(response) {
+      $scope.server.update();
+    });
+  };
+
+  $scope.reject = function(sysId) {
+    $http.post('/api/x_your_scope/collab_action', {
+      action: 'reject',
+      sys_id: sysId
+    }).then(function(response) {
+      $scope.server.update();
+    });
+  };
+}

Client-Side Components/Catalog Client Script/Multi-User Collaboration/widget server script.JS

@@ -0,0 +1,15 @@
+(function() {
+  var collabs = [];
+  var gr = new GlideRecord('x_your_scope_collaborators');
+  gr.addQuery('request', $sp.getParameter('request_id'));
+  gr.query();
+  while (gr.next()) {
+    collabs.push({
+      sys_id: gr.getUniqueValue(),
+      name: gr.collaborator.name.toString(),
+      status: gr.status.toString(),
+      comments: gr.comments.toString()
+    });
+  }
+  data.collaborators = collabs;
+})();

Client-Side Components/Catalog Client Script/Percentage Symbol/readme.md

@@ -0,0 +1,7 @@
+Sets the field value to the formatted percentage string (e.g., 45 becomes 45.00%).
+
+Retrieves the current value of the field.
+Removes any existing % symbol to avoid duplication.
+Validates the input to ensure it's a number.
+Converts the value to a float.
+Formats it to two decimal places and appends a % symbol. 

Client-Side Components/Catalog Client Script/Percentage Symbol/script.js

@@ -0,0 +1,28 @@
+/*Sets the field value to the formatted percentage string (e.g., 45 becomes 45.00%).
+
+Retrieves the current value of the field.
+Removes any existing % symbol to avoid duplication.
+Validates the input to ensure it's a number.
+Converts the value to a float.
+Formats it to two decimal places and appends a % symbol. */
+
+
+function onChange(control, oldValue, newValue, isLoading) {
+   if (isLoading || newValue == '') {
+      return;
+   }
+
+   function formatPercent(value) {
+    if (value === null || value === undefined || value === '' || isNaN(value)) {
+        return "";
+    }
+    var num = parseFloat(value);
+    if (isNaN(num)) 
+	return "";
+    return num.toFixed(2) + "%";
+}
+var des_amount = g_form.getValue("<variable_name>").replace("%","");
+
+g_form.setValue("<variable_name>", formatPercent(des_amount));
+   
+}

Client-Side Components/Client Scripts/Auto Update Priority based on Impact and Urgency/readme.md

@@ -0,0 +1,81 @@
+🧩 Readme : Client Script: Auto Priority Update Based on Impact and Urgency
+📘 Overview
+
+This client script automatically updates the Priority field on the Incident form whenever the Impact or Urgency value changes.
+It follows the ITIL standard mapping to ensure the correct priority is always set automatically, improving data accuracy and efficiency for service desk agents.
+
+⚙️ Script Details
+Field	Value
+Name	Auto Priority Update based on Impact and Urgency
+Type	onChange
+Applies to Table	Incident
+Applies on Fields	impact, urgency
+UI Type	All (Classic, Mobile, Workspace)
+Active	✅ Yes
+Condition	Leave blank
+💻 Script Code
+// ==========================================================================
+// Script Name: Auto Priority Update based on Impact and Urgency
+// Table: Incident
+// Type: onChange | Fields: impact, urgency
+// UI Type: All
+// Version: 2025 Production Ready
+// ==========================================================================
+
+function onChange(control, oldValue, newValue, isLoading, isTemplate) {
+    // Skip execution if form is loading or field is empty
+    if (isLoading || newValue == '') {
+        return;
+    }
+
+    // Get Impact and Urgency values
+    var impact = g_form.getValue('impact');
+    var urgency = g_form.getValue('urgency');
+
+    // Define Priority Matrix (ITIL standard)
+    var priorityMatrix = {
+        '1': { '1': '1', '2': '2', '3': '3' },
+        '2': { '1': '2', '2': '3', '3': '4' },
+        '3': { '1': '3', '2': '4', '3': '5' }
+    };
+
+    // Find the new Priority
+    var newPriority = priorityMatrix[impact]?.[urgency];
+
+    // Update the Priority field if valid
+    if (newPriority) {
+        if (g_form.getValue('priority') != newPriority) {
+            g_form.setValue('priority', newPriority);
+            g_form.showFieldMsg('priority', 'Priority auto-updated based on Impact and Urgency', 'info');
+        }
+    } else {
+        // Optional: Clear Priority if invalid combination is selected
+        g_form.clearValue('priority');
+        g_form.showFieldMsg('priority', 'Invalid Impact/Urgency combination — priority cleared', 'error');
+    }
+}
+
+🧠 How It Works
+
+The script runs automatically when Impact or Urgency changes.
+It checks the ITIL-based matrix to determine the correct Priority.
+If a valid combination is found, the Priority field updates automatically.
+A small info message appears to confirm the update.
+
+🔢 ITIL Mapping Table
+Impact	Urgency	Resulting Priority
+1 (High)	1 (High)	1 (Critical)
+1	2	2
+1	3	3
+2	1	2
+2	2	3
+2	3	4
+3	1	3
+3	2	4
+3	3	5
+✅ Benefits
+
+Automatically enforces ITIL priority standards
+Reduces manual effort and user errors
+Ensures consistency in priority calculation
+Compatible with Classic UI, Next Experience, and Agent Workspace

Client-Side Components/Client Scripts/Auto Update Priority based on Impact and Urgency/script.js

@@ -0,0 +1,58 @@
+//Auto Priority Update based on Impact and Urgency
+
+// ==========================================================================
+// Script Name: Auto Priority Update based on Impact and Urgency
+// Table: Incident (or any Task-based table)
+// Type: onChange | Fields: impact, urgency
+// UI Type: All
+// ==========================================================================
+
+function onChange(control, oldValue, newValue, isLoading, isTemplate) {
+    // Prevent the script from running when the form loads or when the field is empty
+    if (isLoading || newValue == '') {
+        return;
+    }
+
+    // ----------------------------------------------------------------------
+    // Step 1: Fetch field values from the form
+    // ----------------------------------------------------------------------
+    var impact = g_form.getValue('impact');   // e.g., 1 - High, 2 - Medium, 3 - Low
+    var urgency = g_form.getValue('urgency'); // e.g., 1 - High, 2 - Medium, 3 - Low
+
+    // ----------------------------------------------------------------------
+    // Step 2: Define the ITIL-based Priority Matrix
+    // ----------------------------------------------------------------------
+    // Each row represents "Impact", and each column represents "Urgency"
+    // The resulting value sets the "Priority"
+    var priorityMatrix = {
+        '1': { '1': '1', '2': '2', '3': '3' }, // Impact = High
+        '2': { '1': '2', '2': '3', '3': '4' }, // Impact = Medium
+        '3': { '1': '3', '2': '4', '3': '5' }  // Impact = Low
+    };
+
+    // ----------------------------------------------------------------------
+    // Step 3: Determine the new priority based on selected Impact/Urgency
+    // ----------------------------------------------------------------------
+    var newPriority = priorityMatrix[impact]?.[urgency]; // optional chaining prevents errors
+
+    // ----------------------------------------------------------------------
+    // Step 4: Update the Priority field and inform the user
+    // ----------------------------------------------------------------------
+    if (newPriority) {
+        // Only update if priority is different from current value
+        if (g_form.getValue('priority') != newPriority) {
+            g_form.setValue('priority', newPriority);
+
+            // Show message (works in both Classic UI and Next Experience)
+            g_form.showFieldMsg('priority', 'Priority auto-updated based on Impact and Urgency', 'info');
+        }
+    } else {
+        // Optional: clear priority if invalid combination is selected
+        g_form.clearValue('priority');
+        g_form.showFieldMsg('priority', 'Invalid Impact/Urgency combination — priority cleared', 'error');
+    }
+
+    // ----------------------------------------------------------------------
+    // End of Script
+    // ----------------------------------------------------------------------
+}

Client-Side Components/Client Scripts/Prevent Rejection Without Comments/readme.md

@@ -0,0 +1,72 @@
+🧩 Readme: Prevent Rejection Without Comments – Client Script
+📘 Overview
+
+This Client Script enforces that approvers must enter comments before rejecting a record in the Approval [sysapproval_approver] table.
+It ensures accountability, audit readiness, and clear justification for rejection decisions.
+
+🧠 Use Case
+Field	Details
+Table	sysapproval_approver
+Type	Client Script – onSubmit
+Purpose	Prevent users from rejecting approvals without comments
+Business Value	Ensures transparency and proper audit trail in approval workflows
+⚙️ Configuration Steps
+
+Navigate to System Definition → Client Scripts.
+
+Click New.
+
+Fill the form as follows:
+
+Field	Value
+Name	Prevent Rejection Without Comments
+Table	sysapproval_approver
+UI Type	All
+Type	onSubmit
+Active	✅
+Applies on	Update
+
+Paste the following script in the Script field.
+
+💻 Script
+function onSubmit() {
+    // Get the current state value of the approval record
+    var state = g_form.getValue('state');
+
+    // Get the comments entered by the approver
+    var comments = g_form.getValue('comments');
+
+    // Check if the approver is trying to REJECT the record
+    // The out-of-box (OOB) value for rejection in sysapproval_approver is "rejected"
+    // If state is 'rejected' and comments are empty, stop the submission
+    if (state == 'rejected' && !comments) {
+
+        // Display an error message to the user
+        g_form.addErrorMessage('Please provide comments before rejecting the approval.');
+
+        // Prevent the form from being submitted (block save/update)
+        return false;
+    }
+
+    // Allow the form submission if validation passes
+    return true;
+}
+
+🧪 Example Scenario
+Field	Value
+Approver	John Doe
+State	Rejected
+Comments	(empty)
+
+User Action: Clicks Update
+System Response: Shows error message —
+
+“Please provide comments before rejecting the approval.”
+Record submission is blocked until comments are provided.
+
+✅ Expected Outcome
+🚫 Prevents rejection without comments
+⚠️ Displays user-friendly validation message
+📝 Ensures that every rejection has a reason logged for compliance
+
+