Merge branch 'main' into feature/Identify-inactive-assignment-groups

anjimuvva · web-flow · commit 9385271da73f · 2025-10-30T16:14:58.000+08:00
diff --git a/Client-Side Components/Catalog Client Script/Catalog Approval/Readme.md b/Client-Side Components/Catalog Client Script/Catalog Approval/Readme.md
@@ -0,0 +1 @@
+This project adds a dynamic preview feature to Service Catalog items, allowing users to see the full approval chain before submitting a request. It improves transparency, reduces confusion, and helps users understand who will be involved in the approval process based on their selections.
diff --git a/Client-Side Components/Catalog Client Script/Catalog Approval/client script.js b/Client-Side Components/Catalog Client Script/Catalog Approval/client script.js
@@ -0,0 +1,10 @@
+function onLoad() {
+  var ga = new GlideAjax('ApprovalChainHelper');
+  ga.addParam('sysparm_name', 'getApprovers');
+  ga.addParam('sysparm_item_id', g_form.getUniqueValue());
+  ga.getXMLAnswer(function(response) {
+    var approvers = JSON.parse(response);
+    var message = 'This request will be approved by: ' + approvers.join(', ');
+    g_form.showFieldMsg('requested_for', message, 'info');
+  });
+}
diff --git a/Client-Side Components/Catalog Client Script/Catalog Approval/script include.js b/Client-Side Components/Catalog Client Script/Catalog Approval/script include.js
@@ -0,0 +1,20 @@
+var ApprovalChainHelper = Class.create();
+ApprovalChainHelper.prototype = Object.extendsObject(AbstractAjaxProcessor, {
+  getApprovers: function() {
+    var itemId = this.getParameter('sysparm_item_id');
+    var userId = gs.getUserID();
+
+    var approvers = [];
+
+    // Example logic: fetch approval rules based on item and user
+    var ruleGR = new GlideRecord('sysapproval_approver');
+    ruleGR.addQuery('document_id', 80f8920bc3e4b2105219daec050131e3);
+    ruleGR.query();
+
+    while (ruleGR.next()) {
+      approvers.push(ruleGR.approver.name.toString());
+    }
+
+    return JSON.stringify(approvers);
+  }
+});
diff --git a/Client-Side Components/Catalog Client Script/Document validation/Client script.JS b/Client-Side Components/Catalog Client Script/Document validation/Client script.JS
@@ -0,0 +1,12 @@
+function onSubmit() {
+  var ga = new GlideAjax('DocumentValidationHelper');
+  ga.addParam('sysparm_name', 'validateAttachments');
+  ga.addParam('sysparm_item_id', g_form.getUniqueValue());
+  ga.getXMLAnswer(function(response) {
+    if (response !== 'valid') {
+      alert('Document validation failed: ' + response);
+      return false;
+    }
+  });
+  return true;
+}
diff --git a/Client-Side Components/Catalog Client Script/Document validation/Readme.md b/Client-Side Components/Catalog Client Script/Document validation/Readme.md
@@ -0,0 +1 @@
+This project enhances a Service Catalog item by allowing users to upload supporting documents (e.g., ID proof, approval letters) and validating them before the request is submitted. It ensures compliance, completeness, and proper documentation for sensitive or regulated requests.
diff --git a/Client-Side Components/Catalog Client Script/Document validation/Script include.js b/Client-Side Components/Catalog Client Script/Document validation/Script include.js
@@ -0,0 +1,22 @@
+var DocumentValidationHelper = Class.create();
+DocumentValidationHelper.prototype = Object.extendsObject(AbstractAjaxProcessor, {
+  validateAttachments: function() {
+    var itemId = this.getParameter('sysparm_item_id');
+    var attachmentGR = new GlideRecord('sys_attachment');
+    attachmentGR.addQuery('table_name', 'sc_req_item');
+    attachmentGR.addQuery('table_sys_id', itemId);
+    attachmentGR.query();
+
+    while (attachmentGR.next()) {
+      var fileName = attachmentGR.file_name.toLowerCase();
+      if (!fileName.endsWith('.pdf') && !fileName.endsWith('.docx')) {
+        return 'Only PDF or DOCX files are allowed.';
+      }
+      if (attachmentGR.size_bytes > 5 * 1024 * 1024) {
+        return 'File size exceeds 5MB limit.';
+      }
+    }
+
+    return 'valid';
+  }
+});
diff --git a/Client-Side Components/Catalog Client Script/Schedule Request/Readme.JS b/Client-Side Components/Catalog Client Script/Schedule Request/Readme.JS
@@ -0,0 +1 @@
+This project allows users to schedule a Service Catalog request for a future date and time. Instead of submitting immediately, the request is stored and automatically submitted later using a Scheduled Job
diff --git a/Client-Side Components/Catalog Client Script/Schedule Request/scheduled client script.js b/Client-Side Components/Catalog Client Script/Schedule Request/scheduled client script.js
@@ -0,0 +1,17 @@
+function onSubmit() {
+  var scheduledTime = g_form.getValue('scheduled_time');
+  var currentTime = new Date().toISOString();
+
+  if (scheduledTime > currentTime) {
+    var ga = new GlideAjax('ScheduledRequestHelper');
+    ga.addParam('sysparm_name', 'storeScheduledRequest');
+    ga.addParam('sysparm_item', g_form.getUniqueValue());
+    ga.addParam('sysparm_time', scheduledTime);
+    ga.getXMLAnswer(function(response) {
+      alert('Your request has been scheduled for: ' + scheduledTime);
+    });
+    return false; // Prevent immediate submission
+  }
+
+  return true; // Submit immediately if time is now or past
+}
diff --git a/Client-Side Components/Catalog Client Script/Schedule Request/scheduled scriptinclude.JS b/Client-Side Components/Catalog Client Script/Schedule Request/scheduled scriptinclude.JS
@@ -0,0 +1,15 @@
+var ScheduledRequestHelper = Class.create();
+ScheduledRequestHelper.prototype = Object.extendsObject(AbstractAjaxProcessor, {
+  storeScheduledRequest: function() {
+    var itemID = this.getParameter('sysparm_item');
+    var scheduledTime = this.getParameter('sysparm_time');
+
+    var record = new GlideRecord('x_snc_scheduled_requests'); // Custom table
+    record.initialize();
+    record.catalog_item = itemID;
+    record.scheduled_time = scheduledTime;
+    record.insert();
+
+    return 'Scheduled successfully';
+  }
+});
diff --git a/Client-Side Components/Catalog Client Script/Schedule Request/scheduled_job.JS b/Client-Side Components/Catalog Client Script/Schedule Request/scheduled_job.JS
@@ -0,0 +1,14 @@
+var now = new GlideDateTime();
+var gr = new GlideRecord('x_snc_scheduled_requests');
+gr.addQuery('scheduled_time', '<=', now);
+gr.query();
+
+while (gr.next()) {
+  var request = new GlideRecord('sc_request');
+  request.initialize();
+  request.requested_for = gr.requested_for;
+  request.cat_item = gr.catalog_item;
+  request.insert();
+
+  gr.deleteRecord(); // Remove after submission
+}
diff --git a/Client-Side Components/Client Scripts/Abort direct incident closure without Resolve State/readme.md b/Client-Side Components/Client Scripts/Abort direct incident closure without Resolve State/readme.md
@@ -0,0 +1,31 @@
+📘 README — Incident State Validation (Client Script)
+Overview
+
+This Client Script enforces the correct ITIL incident lifecycle by preventing users from directly closing an incident without first transitioning it through the Resolved state.
+If a user attempts to move the state directly to Closed Complete, the system reverts the change and displays a notification.
+
+What This Code Does
+Monitors changes to the state field on Incident form
+Checks if new selection is trying to skip the Resolved step
+Reverts state to its previous value when the rule is violated
+Alerts the user with a clear and guided message
+Refreshes the form to maintain data consistency
+Usage Instructions
+
+Create a Client Script on the Incident table
+Type: onChange
+Field Name: state
+Paste the script under the script section
+Test by trying to directly move an Incident to Closed Complete
+S
+cript Requirements
+State values must be configured as:
+6 → Resolved
+7 → Closed Complete
+
+Script runs only on Incident records
+Must be active in applicable ITIL views
+Notes for Developers
+This code supports clean transition handling for ITSM workflows
+Helps enforce process compliance without server-side overhead
+Recommended for environments requiring strict closure governance
diff --git a/Client-Side Components/Client Scripts/Abort direct incident closure without Resolve State/script.js b/Client-Side Components/Client Scripts/Abort direct incident closure without Resolve State/script.js
@@ -0,0 +1,30 @@
+function onChange(control, oldValue, newValue, isLoading, isTemplate) {
+    // Prevent execution during form load or when value is empty
+    if (isLoading || newValue === '') {
+        return;
+    }
+
+    // Dummy values for state comparison
+    // Assuming:
+    // 6 = Resolved
+    // 7 = Closed Complete
+    var RESOLVED = 6;
+    var CLOSED = 7;
+
+    // Prevent direct move to Closed without passing through Resolved
+    if (newValue == CLOSED && oldValue != RESOLVED) {
+        
+        // Reset to previous state
+        g_form.setValue('state', oldValue);
+
+        // Show validation warning
+        g_form.addErrorMessage(
+            'Direct closure is not allowed. Please first move the incident to Resolved state.'
+        );
+
+        // Reload page after showing error
+        setTimeout(function() {
+            location.reload();
+        }, 3000);
+    }
+}
diff --git a/Core ServiceNow APIs/GlideAggregate/Count Inactive Users with Active incidents/README.md b/Core ServiceNow APIs/GlideAggregate/Count Inactive Users with Active incidents/README.md
@@ -0,0 +1,38 @@
+Count Active Incidents Assigned to Inactive Users 
+
+This script uses GlideAggregate to efficiently count the number of active incidents assigned to inactive users. 
+
+This is a crucial task for maintaining data hygiene and preventing incidents from being stalled due to inactive assignees. 
+
+Overview The script performs the following actions: Initializes GlideAggregate: Creates an aggregate query on the incident table. 
+
+Filters Records: Uses addQuery() to restrict the search to incidents that are both active (true) and assigned to a user whose active status is false.
+
+This filter uses a "dot-walk" on the assigned_to field to check the user's active status directly within the query.
+
+Aggregates by Count: Uses addAggregate() to count the number of incidents, grouping the results by assigned_to user.
+
+Executes and Logs: Runs the query, then loops through the results. 
+
+For each inactive user found, it logs their name and the number of active incidents assigned to them. Use case This script is essential for regular cleanup and maintenance. 
+
+It can be used in: Scheduled Job: Automatically run the script daily or weekly to monitor for and report on incidents assigned to inactive users. 
+
+Installation As a Scheduled Job Navigate to System Definition > Scheduled Jobs.
+
+
+Click New and select Automatically run a script of your choosing. Name the job (e.g., Find Incidents Assigned to Inactive Users).
+
+
+Set your desired frequency and time. Paste the script into the Run this script field. Save and activate the job. As a Fix Script Navigate to System Definition > Fix Scripts.
+
+Click New. Name it (e.g., Find Active Incidents with Inactive Assignee).
+
+
+Paste the script into the Script field. Run the script to see the results in the System Log. 
+
+
+Customization Targeted tables: Change the table name from incident to task or any other table with an assigned_to field to check for active records assigned to inactive users.
+
+
+Automated reassignment: Extend the script to automatically reassign the incidents to a group or another user. This is a common practice to ensure that tickets do not get stuck in the queue. Email notification: Instead of logging the information, modify the script to send an email notification to the group manager or another stakeholder with the list of incidents needing attention.
diff --git a/Core ServiceNow APIs/GlideAggregate/Count Inactive Users with Active incidents/script.js b/Core ServiceNow APIs/GlideAggregate/Count Inactive Users with Active incidents/script.js
@@ -0,0 +1,32 @@
+/* 
+This script uses GlideAggregate to find the number of active incidents
+that are assigned to users who are currently marked as inactive.
+GlideAggregate is used instead of a standard GlideRecord query
+because it is more efficient for performing calculations like COUNT 
+directly in the database.
+*/
+var ga = new GlideAggregate('incident');
+
+// Query for active incidents.
+ga.addQuery('active', true);
+
+// Use dot-walking to query for incidents assigned to inactive users.
+ga.addQuery('assigned_to.active', false);
+
+// Add an aggregate function to count the incidents, grouped by the assigned user.
+ga.addAggregate('COUNT', 'assigned_to');
+
+// Execute the query.
+ga.query();
+
+// Process the results of the aggregate query.
+while (ga.next()) {
+    // Get the display name of the inactive user from the current record.
+    var inactiveUser = ga.assigned_to.getDisplayValue();
+    
+    // Get the count of active incidents for this specific user.
+    var incidentCount = ga.getAggregate('COUNT', 'assigned_to');
+    
+    // Log the result to the system logs.
+    gs.info("Inactive user " + inactiveUser + " has " + incidentCount + " active incidents.");
+}
diff --git a/Core ServiceNow APIs/GlideAggregate/Count open Incidents per Priority and State using GlideAggregate/README.md b/Core ServiceNow APIs/GlideAggregate/Count open Incidents per Priority and State using GlideAggregate/README.md
@@ -0,0 +1,29 @@
+# Count open Incidents per Priority and State using GlideAggregate
+
+## Overview
+This script will dynamically calculate the **number of open incidents** for each priority level and also give you a total for what 
+current state the Incident is in using **server-side scripting**
+Priority levels typically include:  
++ 1 – Critical  
++ 2 – High  
++ 3 – Moderate  
++ 4 – Low
+
+Incident State typically include:
++ New
++ In Progress
++ On Hold
++ Resolved
++ Closed
++ Canceled
+
+The scripting solution leverages **GlideAggregate** to efficiently count records grouped by priority and state. This scripts approach
+is useful for:
++ Dashboards
++ Business Rules
++ SLA monitoring and reporting
+ 
+--
+## Table and Fields
++ **Table:** Task
++ **Fields:** Priority, State
diff --git a/Core ServiceNow APIs/GlideAggregate/Count open Incidents per Priority and State using GlideAggregate/script.js b/Core ServiceNow APIs/GlideAggregate/Count open Incidents per Priority and State using GlideAggregate/script.js
@@ -0,0 +1,45 @@
+/*
+*Going to define the Incident Closed and Canceled state since we dont want those records as part of our query. 
+*Also going to leverage the IncidentStateSNC script from ServiceNow
+*/
+
+/*
+*Going to define the Incident Closed and Canceled state since we dont want those records as part of our query. 
+*/
+var incident_close = IncidentStateSNC.CLOSED;
+var incident_canceled = IncidentStateSNC.CANCELED;
+var incident_state_query = incident_close + "," + incident_canceled;
+
+/*
+*Creating the Incident State value object that will house the correct incident state since we are working from the Task table.
+*Leveraging the IncidentStateSNC script from ServiceNow to get the values that they should be
+*/
+var incident_states = {
+  '1':'New',
+  '2':'In Progress',
+  '3':'On Hold',
+  '6':'Resolved',
+  '7':'Closed',
+  '8':'Canceled'
+};
+
+//Going to create the GlideAggregate object
+var ga = new GlideAggregate('task');
+ga.addQuery('state', 'NOT IN', incident_state_query); //Going to exclude the canceled and closed incidents
+ga.addQuery('sys_class_name', 'incident'); //Since working on the Task table need to grab only Incident records with task type
+ga.groupBy('state');
+ga.groubBy('count');
+ga.addAggregate('COUNT');
+ga.query()
+
+gs.info('The following is a list of Open Incident records');
+
+while (ga.next()) {
+
+  var priorityValue = ga.getDisplayValue('priority');
+  var state = ga.getValue('state');
+  var count = ga.getValue('COUNT');
+
+  gs.info("There are a total of: " + count + " Incidents with a priority of " + priorityValue + " and in a state of " + incident_states[state]);
+  
+}
diff --git a/Server-Side Components/Business Rules/When Group is making inactive/Code.js b/Server-Side Components/Business Rules/When Group is making inactive/Code.js
@@ -0,0 +1,30 @@
+(function executeRule(current, previous /*null when async*/) {
+
+    // Run only when group is being inactivated
+    if (current.active.changes() && current.active == false) {
+
+        var openTicketCount = 0;
+
+        // List of task tables to check
+        var taskTables = ['incident', 'problem', 'change_request'];
+
+        for (var i = 0; i < taskTables.length; i++) {
+            var gr = new GlideRecord(taskTables[i]);
+            gr.addQuery('assignment_group', current.sys_id);
+            gr.addQuery('active', true);
+            gr.query();
+            if (gr.hasNext()) {
+                openTicketCount++;
+                break; // We found at least one open ticket, no need to continue
+            }
+        }
+
+        // If open tickets exist, stop the update
+        if (openTicketCount > 0) {
+            gs.addErrorMessage('Cannot deactivate "' + current.name + 
+                '" group, because there are open tickets assigned to it.');
+            current.setAbortAction(true);
+        }
+    }
+
+})(current, previous);
diff --git a/Server-Side Components/Business Rules/When Group is making inactive/ReadMe.md b/Server-Side Components/Business Rules/When Group is making inactive/ReadMe.md
@@ -0,0 +1 @@
+When marking a group as inactive, verify that there are no open tickets assigned to it from 'incident', 'problem', 'change_request' tables. If any open tickets are found, abort the deactivation process.
diff --git a/Specialized Areas/Fix scripts/Copy favourite to other users/README.md b/Specialized Areas/Fix scripts/Copy favourite to other users/README.md
@@ -1,3 +1,7 @@
+**Enhancement**
+1. This code will create the sp favorites of the selected users along with the sys_ui_bookmarks.
+2. The entry will be made in "sp_favorite" through new **createPortalFav** function.
+
 You can use this script to take an existing favaourite from the sys_ui_bookmark table and create a copy of it for any number of users.
 Can be useful when onboarding new staff, doing testing, etc.
 
diff --git a/Specialized Areas/Fix scripts/Copy favourite to other users/favCopy.js b/Specialized Areas/Fix scripts/Copy favourite to other users/favCopy.js

Original file line number	Diff line number	Diff line change
`@@ -0,0 +1 @@`
	`1`	`+This project adds a dynamic preview feature to Service Catalog items, allowing users to see the full approval chain before submitting a request. It improves transparency, reduces confusion, and helps users understand who will be involved in the approval process based on their selections.`
Original file line number	Diff line number	Diff line change
`@@ -0,0 +1 @@`
	`1`	`+This project enhances a Service Catalog item by allowing users to upload supporting documents (e.g., ID proof, approval letters) and validating them before the request is submitted. It ensures compliance, completeness, and proper documentation for sensitive or regulated requests.`
Original file line number	Diff line number	Diff line change
`@@ -0,0 +1 @@`
	`1`	`+This project allows users to schedule a Service Catalog request for a future date and time. Instead of submitting immediately, the request is stored and automatically submitted later using a Scheduled Job`