Merge branch 'ServiceNowDevProgram:main' into First-Contribution

Author: harishbaislaawc2022-sketch

Client-Side Components/Catalog Client Script/previous Request/Readme.MD

@@ -0,0 +1,3 @@
+Show previous request ON requested for selection
+
+This feature enhances the Service Catalog experience by displaying previous requests for the selected Requested For user. When a user selects the Requested For variable in a catalog item form, a confirmation message appears showing the last few requests created for that user.

Client-Side Components/Catalog Client Script/previous Request/previous request client script.js

@@ -0,0 +1,24 @@
+function onChange(control, oldValue, newValue, isLoading) {
+    if (isLoading || newValue == '') return;
+
+    var ga = new GlideAjax('PreviousRequestsUtils');
+    ga.addParam('sysparm_name', 'getPreviousRequests');
+    ga.addParam('sysparm_requested_for', newValue);
+    ga.getXMLAnswer(function(response) {
+        var requests = JSON.parse(response);
+        if (requests.length === 0) {
+            alert('No previous requests found for this user.');
+        } else {
+            var message = 'Previous Requests:\n\n';
+            requests.forEach(function(req) {
+                message += 'Number: ' + req.number + ' | Item: ' + req.item + ' | Date: ' + req.date + '\n';
+            });
+            if (confirm(message + '\nDo you want to continue?')) {
+                // User clicked OK
+            } else {
+                // User clicked Cancel
+                g_form.setValue('requested_for', oldValue);
+            }
+        }
+    });
+}

Client-Side Components/Catalog Client Script/previous Request/previous request script include.js

@@ -0,0 +1,20 @@
+var PreviousRequestsUtils = Class.create();
+PreviousRequestsUtils.prototype = Object.extendsObject(AbstractAjaxProcessor, {
+    getPreviousRequests: function() {
+        var requestedFor = this.getParameter('sysparm_requested_for');
+        var result = [];
+        var gr = new GlideRecord('sc_req_item');
+        gr.addQuery('requested_for', requestedFor);
+        gr.orderByDesc('sys_created_on');
+        gr.setLimit(5); // Show last 5 requests
+        gr.query();
+        while (gr.next()) {
+            result.push({
+                number: gr.number.toString(),
+                item: gr.cat_item.getDisplayValue(),
+                date: gr.sys_created_on.getDisplayValue()
+            });
+        }
+        return JSON.stringify(result);
+    }
+});

Client-Side Components/Client Scripts/Validate Interaction record for FCR(First Call Resolution)/readme.md

@@ -0,0 +1,71 @@
+README — Client Script: Validate Interaction Resolution
+📌 Purpose
+This Client Script ensures proper validation when resolving an Interaction record in ServiceNow.
+It prevents a user from marking an Interaction as Closed Complete without proper justification.
+
+🎯 What It Does
+
+When a user attempts to submit the form:
+✔ Allows submission only if:
+Interaction Type is "walkup"
+And Related Task Boolean is true
+
+OR
+
+✔ If work notes are provided for First Contact Resolution (FCR)
+❌ Prevents submission if:
+State = Closed Complete
+Work Notes are empty
+And no related task condition is met
+
+🧠 Validations Performed
+Field	Condition	Action
+state	closed_complete	Trigger validation
+type	walkup AND u_boolean_no_related_task = true	Submission allowed ✅
+work_notes	Must not be empty	Show error & stop submission ❌
+🔔 User Feedback
+
+If work notes are missing:
+Displays inline field message
+
+Shows popup alert:
+"Provide Worknotes for FCR Interaction"
+
+📍 Script Location
+
+Client Script → Type: onSubmit()
+Applicable to Interaction table (interaction)
+
+📌 Script Code
+//Client Script to validate an Interaction record is resolved with out any related record created.
+function onSubmit() {
+    var relatedTask = g_form.getValue('u_boolean_no_related_task');
+    var state = g_form.getValue('state');
+    var type = g_form.getValue('type');
+    var workNotes = g_form.getValue('work_notes'); // Get the value of work notes
+
+    // Clear previous field messages
+    g_form.clearMessages();
+
+    // Check if state is changing to 'Closed Complete'
+    if (state == 'closed_complete') {
+        // Check additional conditions
+        if (type == 'walkup' && relatedTask == 'true') {
+            return true; // Allow form submission
+        } else if (!workNotes) { // Check if work notes is empty
+            g_form.showFieldMsg('work_notes', 'Provide Worknotes for FCR Interaction', 'error');
+            alert('Provide Worknotes for FCR Interaction');
+            return false; // Prevent form submission
+        }
+    }
+    return true; // Allow form submission for other states
+}
+
+✅ Benefits
+
+Maintains consistent resolution standards
+Ensures justification/documentation for FCR interactions
+Reduces incorrect closure of requests without related actions
+
+
+

Client-Side Components/Client Scripts/Validate Interaction record for FCR(First Call Resolution)/script.js

@@ -0,0 +1,23 @@
+//Client Script to validate an Interaction record is resolved with out any related record created.
+function onSubmit() {
+    var relatedTask = g_form.getValue('u_boolean_no_related_task');
+    var state = g_form.getValue('state');
+    var type = g_form.getValue('type');
+    var workNotes = g_form.getValue('work_notes'); // Get the value of work notes
+
+    // Clear previous field messages
+    g_form.clearMessages();
+
+    // Check if state is changing to 'Closed Complete'
+    if (state == 'closed_complete') {
+        // Check additional conditions
+        if (type == 'walkup' && relatedTask == 'true') {
+            return true; // Allow form submission
+        } else if (!workNotes) { // Check if work notes is empty
+            g_form.showFieldMsg('work_notes', 'Provide Worknotes for FCR Interaction', 'error');
+			alert('Provide Worknotes for FCR Interaction');
+            return false; // Prevent form submission
+        }
+    }
+    return true; // Allow form submission for other states
+}

Client-Side Components/UI Macros/Show Open Incident of Caller/Readme.md

@@ -0,0 +1,21 @@
+Show Open Incident of caller
+
+Script Type: UI Macro
+
+Goal: In Form view caller can see what are the open incident of that particular caller.
+
+Walk through of code: So for this use case a new macro will be added to the caller field,  when it is triggered it will open a new popup window where it will show the list of particular caller which are all open incident.So for this a new UImacro have been used in that a new list icon have been rendered from the db_image table and inside that a showopentckts() function this will get the current caller and then add the query to filter out the list of open incident and then open a popup to show the list of that particular caller which are all open(other than Closed and Cancelled).
+
+Note: To inherite the UI Macro in that particular field (Caller) we need to add the attribute in the Dictionary Entry = ref_contributions=caller_inc_lists [ref_contributions="name of the macro"]
+
+UI Macro
+<img width="853" height="292" alt="UIMacro" src="https://github.com/user-attachments/assets/f5b353a2-ffb6-4e44-a740-9905b33cb484" />
+
+Dictonary Entry in Attribute section
+<img width="848" height="386" alt="UIMacroDictionary" src="https://github.com/user-attachments/assets/b21d2077-3df5-4408-9bb3-c0672fd1398b" />
+
+UI Macro in Incident Form near the Caller Field
+<img width="860" height="310" alt="From UIMacro" src="https://github.com/user-attachments/assets/c3867abf-f9cd-4947-a7e9-41c83189681d" />
+
+Result:
+<img width="865" height="409" alt="UIMacro Result" src="https://github.com/user-attachments/assets/5412b29b-e96b-4455-a3e0-5552c9680600" />

Client-Side Components/UI Macros/Show Open Incident of Caller/macro.js

@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="utf-8" ?>
+<j:jelly trim="false" xmlns:j="jelly:core" xmlns:g="glide" xmlns:j2="null" xmlns:g2="null">
+
+<img src='sn_tile_icon/now-checklist.svg' stype='width=5%,height:5%' onclick="showopentckts()" title="Show Open Incident of me"></img>
+
+<script language="javascript">
+function showopentckts(){
+var name=g_form.getValue("caller_id");
+var tableName='incident';
+var url=tableName+'_list.do?sysparm_query=caller_id='+name+'^stateNOT IN7,8';
+window.open(url,'OpenIncident',"popup");
+}
+
+</script>
+
+</j:jelly>

Server-Side Components/Background Scripts/Identify Inactive users with tickets/README.md

@@ -0,0 +1,4 @@
+# ServiceNow Background Script – Identify Inactive Users with Open Incidents
+
+This background script helps admin to identify **inactive users** who still have **open incidents** assigned to them.  
+It’s particularly useful during **user cleanup, offboarding audits, or reassignment activities** to ensure no tickets remain unaddressed.

Server-Side Components/Background Scripts/Identify Inactive users with tickets/identify_inactive_users_with_open_tickets.js

@@ -0,0 +1,12 @@
+var user = new GlideRecord('sys_user');
+user.addQuery('active', false);
+user.query();
+while (user.next()) {
+    var inc = new GlideRecord('incident');
+    inc.addQuery('assigned_to', user.sys_id);
+    inc.addQuery('state', '!=', 7); // not Closed
+    inc.query();
+    while (inc.next()) {
+        gs.info('Inactive user with open ticket: ' + user.name + ' → ' + inc.number);
+    }
+}

Server-Side Components/Background Scripts/Safe Bulk Update with Logging/README.md

@@ -0,0 +1,37 @@
+# Safe Bulk Record Update with Logging
+
+## Overview
+Efficiently update multiple records in batch with error handling, progress tracking, and logging to prevent timeouts and data loss.
+
+## What It Does
+- Updates records in configurable batch sizes
+- Logs progress for monitoring
+- Handles individual record errors without stopping batch
+- Prevents script timeout with batch processing
+- Tracks success/failure counts
+- Logs detailed error information
+
+## Use Cases
+- Bulk data migrations
+- Mass field updates after deployment
+- Scheduled bulk corrections
+- Data cleanup operations
+- Batch status updates across records
+
+## Files
+- `bulk_update_with_progress.js` - Background Script for safe bulk updates
+
+## How to Use
+
+### Option 1: Run as Background Script
+1. Go to **System Diagnostics > Script Background**
+2. Copy code from `bulk_update_with_progress.js`
+3. Modify the table name and query filter
+4. Execute and monitor logs
+
+### Option 2: Create as Scheduled Job
+1. Go to **System Scheduler > Scheduled Jobs**
+2. Create new job with the script code
+3. Schedule for off-peak hours
+4. Logs will be available in System Logs
+