Merge branch 'ServiceNowDevProgram:main' into main

Author: raghavs046

Client-Side Components/Client Scripts/Display Incident Count of Assigned-To User When Field Changes/Incident_Count_message_1.png

@@ -0,0 +1,17 @@
+## Display Info Message of Incident Count of Assigned-To User When Field Assigned-To Changes
+
+Displays a message showing the count of **open incidents** assigned to a user whenever the **Assigned To** field changes on the Incident form.  
+
+- Helps assess the assignee’s **current workload** by fetching and displaying active incident counts (excluding *Resolved*, *Closed*, and *Canceled* states)
+- Shows an **info message** with the count of the assignee's assigned incidents
+- Uses an **onChange Client Script** on the **Assigned To** field and a **GlideAjax Script Include** called from the client script to fetch the count dynamically
+
+---
+
+### Info Message Example 1  
+![Incident_Count_message_1](Incident_Count_message_1.png)
+
+### Info Message Example 2  
+![Incident_Count_message_2](Incident_Count_message_2.png)
+
+---

Client-Side Components/Client Scripts/Display Incident Count of Assigned-To User When Field Changes/Incident_Count_message_2.png

@@ -0,0 +1,31 @@
+function onChange(control, oldValue, newValue, isLoading, isTemplate) {
+    if (isLoading || newValue === '') return;
+
+    // Clear any previous messages
+    g_form.clearMessages();
+
+    // Create GlideAjax object to call the Script Include
+    var ga = new GlideAjax('IncidentAssignmentCheck');
+    ga.addParam('sysparm_name', 'getIncidentCount');
+    ga.addParam('sysparm_user', newValue);
+
+    
+    ga.getXMLAnswer(function(response) {
+        var count = parseInt(response, 10);
+
+        
+        if (isNaN(count)) {
+            g_form.addErrorMessage("Could not retrieve open incident count.");
+            return;
+        }
+
+        var userName = g_form.getDisplayValue('assigned_to');
+        var msg = userName + " currently has " + count + " incidents assigned ";
+
+        if (count >= 5) {
+            g_form.addInfoMessage(msg + " Please review workload before assigning more incidents");
+        } else {
+            g_form.addInfoMessage(msg);
+        }
+    });
+}

Client-Side Components/Client Scripts/Display Incident Count of Assigned-To User When Field Changes/README.md

@@ -0,0 +1,23 @@
+var IncidentAssignmentCheck = Class.create();
+IncidentAssignmentCheck.prototype = Object.extendsObject(AbstractAjaxProcessor, {
+
+    getIncidentCount: function() {
+        var user = this.getParameter('sysparm_user');
+        var count = 0;
+
+        if (user) {
+            var gr = new GlideAggregate('incident');
+            gr.addQuery('assigned_to', user);
+            gr.addQuery('state', 'NOT IN', '6,7,8');
+            gr.addAggregate('COUNT');a
+            gr.query();
+
+            if (gr.next()) {
+                count = gr.getAggregate('COUNT');
+            }
+        }
+        return count;
+    },
+
+    type: 'IncidentAssignmentCheck'
+});

Client-Side Components/Client Scripts/Display Incident Count of Assigned-To User When Field Changes/clientScript.js

@@ -0,0 +1,5 @@
+Dynamic script to make fields read only
+
+It runs when the field value changes.On change client script
+If the new value equals '7', it retrieves all editable fields using g_form.getEditableFields().
+Then it loops through each field and sets it to read-only using g_form.setReadOnly().

Client-Side Components/Client Scripts/Display Incident Count of Assigned-To User When Field Changes/glideAjaxIncidentCount.js

@@ -0,0 +1,20 @@
+/*
+It runs when the field value changes.
+If the new value equals '7', it retrieves all editable fields using g_form.getEditableFields().
+Then it loops through each field and sets it to read-only using g_form.setReadOnly().
+
+*/
+
+
+function onChange(control, oldValue, newValue, isLoading, isTemplate) {
+    if (isLoading || newValue === '') {
+        return;
+    }
+
+
+    if (newValue == '7') { // update condition as required
+        var fields = g_form.getEditableFields();
+        for (var i = 0; i < fields.length; i++) {
+            g_form.setReadOnly(fields[i].getName(), true);
+        }
+  

Client-Side Components/Client Scripts/Dynamic script to make fields read only/reame.md

@@ -0,0 +1,49 @@
+# CancelFlow UI Action
+
+A ServiceNow utility that dynamically cancels flows associated with the current record, ensuring seamless process management.
+
+## Challenge
+
+Managing running flows in ServiceNow can be challenging, particularly when multiple flows are tied to a single record. This utility streamlines the process by offering a dynamic solution to identify and cancel running flows, minimizing manual intervention and ensuring seamless operations.
+
+This tool is especially useful in scenarios where you need to halt the current execution and initiate a new flow or process. Additionally, it can be leveraged to forcefully terminate the automation lifecycle when necessary, providing greater control over flow management.
+
+## Description
+
+This UI Action is designed to identify and cancel all running flows associated with the current record in a ServiceNow instance. It provides a user-friendly interface for administrators and developers to manage flow cancellations efficiently. This utility is particularly useful in scenarios where flows need to be terminated to prevent conflicts or errors during record updates.
+
+## Functionality
+
+The CancelFlow UI Action provides the following capabilities:
+- Dynamically identifies running flows for the current record.
+- Cancels the identified flows programmatically.
+- Displays success or error messages to the user for better visibility.
+- Ensures smooth handling of flow cancellations without manual intervention.
+
+## Usage Instructions
+
+### UI Action Script
+
+Add the given script to your UI Action:
+
+
+### Example Usage
+
+1. Open the record where you want to cancel the associated flows.
+2. Click on the **Cancel Flow** UI Action button.
+3. The system will identify and cancel all running flows for the current record.
+4. The same can be used in Business rules as well based on trigger conditions
+
+
+### Visibility for  UI Action
+
+In certain scenarios, it may be necessary to restrict the visibility of this operation to specific user groups. For example, only HR administrators or members of a designated group (e.g., "X Group") should have access to this functionality. These requirements can be addressed by configuring the **Condition** field in the UI Action. You can tailor the conditions to align with your specific use case, ensuring that only authorized users can execute this operation. One edge case about not having an active flow execution can also be handled in the condition which will restrict the visibility if no active flow execution is present.
+
+
+## Dependencies
+
+- `sn_fd.FlowAPI`
+
+## Category
+
+Client-Side Components / UI Actions 

Client-Side Components/Client Scripts/Dynamic script to make fields read only/script.js

@@ -0,0 +1,16 @@
+function cancelRunningFlows() {
+
+  try {
+    var grFlowExecution = new GlideRecord("sys_flow_context");
+    grFlowExecution.addQuery("source_record", current.sys_id);
+    grFlowExecution.query();
+
+    while (grFlowExecution.next()) {
+      sn_fd.FlowAPI.cancel(grFlowExecution.getUniqueValue(), "Canceling Flows");
+    }
+  } catch (error) {
+    gs.error("Error cancelling flows: " + error.message);
+  }
+}
+
+

Client-Side Components/UI Actions/Cancel Flow Executions/README.md

@@ -0,0 +1,17 @@
+# Loaders UI Page  
+
+This UI Page showcases a collection of loaders and spinners designed to visually represent ongoing processes in web applications. These components enhance user experience by providing clear feedback during data loading or processing.  
+
+## Features  
+- A diverse set of loader and spinner designs.  
+- Fully responsive and easily customizable.  
+- Lightweight and seamlessly integrable into glideModal or other UI components.  
+
+
+## Usage  
+1. Select the desired loader's HTML and CSS code from the examples.  
+2. Go to the Application Navigator and search for UI Pages under **System UI > UI Pages**.
+3. Click on New and create new record by adding given HTML in the HTML section.
+4. Adjust the styles as needed to align with your design requirements.  
+
+