Merge branch 'ServiceNowDevProgram:main' into record-as-link

Author: Its-Nmk

Client-Side Components/UI Actions/Cancel Flow Executions/README.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/UI Actions/Cancel Flow Executions/cancelFlow.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);
+  }
+}
+
+

Server-Side Components/Inbound Actions/Duplicate Incident Detection and Creation/README.md

@@ -0,0 +1,23 @@
+**Duplicate Incident Detection and Creation**
+
+**Description**
+This inbound email action detects duplicate incidents from incoming emails and either updates existing incidents or creates a new one.
+
+- Duplicate Found: Updates the existing incident's work notes with the new email content and aborts new incident creation.
+- No Duplicate Found: Creates a new incident with the email subject as short description and the email body as description.
+
+**Use Case**
+When multiple users report the same issue via email, this automation prevents duplicate incidents, keeping the incident queue cleaner and improving triage efficiency.
+
+**Inbound Action Configuration**
+- Target Table: incident 
+- Action Type: Record Action
+- Type: New
+
+**How It Works**
+1. The inbound email action scans the email subject for matches against active incidents whose short description contains the subject excluding Closed or Cancelled incidents.   
+2. If a matching incident is found:
+   - Updates the incident's work notes with the email content.
+   - Aborts creation of a new incident.  
+3. If no match is found:
+   - Creates a new incident using the email subject as the short description and the email body as the description.

Server-Side Components/Inbound Actions/Duplicate Incident Detection and Creation/script.js

@@ -0,0 +1,25 @@
+(function runAction(current, event, email, logger, classifier) {
+    var subject = email.subject.trim();
+
+    //Look for duplicate incident
+    var gr = new GlideRecord('incident');
+    gr.addActiveQuery();
+    gr.addQuery('short_description', 'CONTAINS', subject);
+    gr.addQuery('state', 'NOT IN', '3,4'); //Ignore resolved or closed incidents
+    gr.query();
+
+    if(gr.next()){
+        //Update existing incident with duplicate email
+        gr.work_notes = 'Duplicate email received for this incident:\n' + email.body_text;
+        gr.update();
+
+        //Abort creating new incident
+        action.setAbortAction(true);
+        return;
+    }
+
+	//Create new incident if no duplicate incident found
+    current.short_description = email.subject;
+    current.description = email.body_text;
+	current.update();
+})(current, event, email, logger, classifier);

Specialized Areas/CMDB/UnsyncCI from Asset/readme.md

@@ -0,0 +1 @@
+Fix script to unsync a Asset from a CI . OOB the field is read only, this allows admin to unsync when required.

Specialized Areas/CMDB/UnsyncCI from Asset/script.js

@@ -0,0 +1,22 @@
+unsyncCI();
+
+function unsyncCI() {
+
+    var grAsset = new GlideRecord("alm_hardware");
+    grAsset.addEncodedQuery('sys_id='); //replace query with rrequired list
+    grAsset.query();
+    if (grAsset.next()) {
+        var grCI = new GlideRecord("cmdb_ci");
+        grCI.addQuery("sys_id", grAsset.ci);
+        grCI.setLimit(1);
+        grCI.query();
+        if (grCI.next()) {
+            grCI.asset = '';
+            grCI.setWorkFlow(false);
+            grCI.update();
+        }
+        grAsset.ci = '';
+        grAsset.setWorkFlow(false);
+        grAsset.update();
+    }
+}

Specialized Areas/Regular Expressions/IP Address Validation/README.md

@@ -1,25 +1,24 @@
-The regex in the file getIP4OrIPV6address.js files validates for both ip address(ipv4) or ipv6 based on the input.
+This snippet extracts IPv4 and IPv6 addresses from free text. For single-value validation, see `validateIPInput.js` and `Validate IPv6 Address/script.js`.
 
-This regex cover the folloing IPv6 examples: 
-Full IPv6 addresses (e.g., 2001:0db8:85a3:0000:0000:8a2e:0370:7334).
-Shorthand versions (e.g., fe80::1, where :: represents omitted zeros).
-IPv6 with embedded IPv4 addresses (e.g., ::ffff:192.168.1.1).
-And also includes following IPv4 addresses.
-Following are the valid IP address examples:
+The regex in `getIP4OrIPV6address.js` finds both IPv4 and IPv6 addresses within arbitrary text content.
 
-192.168.1.1
+IPv6 coverage includes:
+- Full addresses like `2001:0db8:85a3:0000:0000:8a2e:0370:7334`
+- Compressed forms like `fe80::1` (`::` for omitted zeros)
+- IPv4-embedded forms like `::ffff:192.168.1.1`
 
-127.0.0.1
+IPv4 validation now strictly enforces each octet to be in the range 0–255.
 
-0.0.0.0
+Valid IPv4 examples:
 
-255.255.255.255
+- 192.168.1.1
+- 127.0.0.1
+- 0.0.0.0
+- 255.255.255.255
+- 1.2.3.4
 
-256.256.256.256
-
-999.999.999.999
-
-1.2.3
-
-1.2.3.4
+Invalid IPv4 examples (correctly rejected by the regex):
 
+- 256.256.256.256
+- 999.999.999.999
+- 1.2.3

Specialized Areas/Regular Expressions/IP Address Validation/getIP4OrIPV6address.js

@@ -1,5 +1,26 @@
+// Extracts IPv4 and IPv6 addresses from arbitrary text content
+// For single-value validation, use validateIPInput.js or Validate IPv6 Address/script.js
 extractIPAddresses: function(text) {
-        var ipRegex = /\b((\d{1,3}\.){3}\d{1,3})\b|\b([a-fA-F0-9:]+:+[a-fA-F0-9:]+)\b/g;
-		var matches = text.match(ipRegex);
+        var ipv4 = "(?:25[0-5]|2[0-4]\\d|1?\\d?\\d)(?:\\.(?:25[0-5]|2[0-4]\\d|1?\\d?\\d)){3}";
+        var ipv6 = "("+
+            "(?:[A-Fa-f0-9]{1,4}:){7}[A-Fa-f0-9]{1,4}|"+
+            "(?:[A-Fa-f0-9]{1,4}:){1,7}:|"+
+            "(?:[A-Fa-f0-9]{1,4}:){1,6}:[A-Fa-f0-9]{1,4}|"+
+            "(?:[A-Fa-f0-9]{1,4}:){1,5}(?::[A-Fa-f0-9]{1,4}){1,2}|"+
+            "(?:[A-Fa-f0-9]{1,4}:){1,4}(?::[A-Fa-f0-9]{1,4}){1,3}|"+
+            "(?:[A-Fa-f0-9]{1,4}:){1,3}(?::[A-Fa-f0-9]{1,4}){1,4}|"+
+            "(?:[A-Fa-f0-9]{1,4}:){1,2}(?::[A-Fa-f0-9]{1,4}){1,5}|"+
+            "[A-Fa-f0-9]{1,4}:(?:(?::[A-Fa-f0-9]{1,4}){1,6})|"+
+            ":(?:(?::[A-Fa-f0-9]{1,4}){1,7}|:)|"+
+            "fe80:(?::[A-Fa-f0-9]{0,4}){0,4}%[0-9A-Za-z]{1,}|"+
+            "::(?:ffff(?::0{1,4}){0,1}:){0,1}(?:"+
+                "(?:25[0-5]|2[0-4]\\d|1?\\d?\\d)(?:\\.(?:25[0-5]|2[0-4]\\d|1?\\d?\\d)){3}"+
+            ")|"+
+            "(?:[A-Fa-f0-9]{1,4}:){1,4}:(?:"+
+                "(?:25[0-5]|2[0-4]\\d|1?\\d?\\d)(?:\\.(?:25[0-5]|2[0-4]\\d|1?\\d?\\d)){3}"+
+            ")"+
+        ")";
+        var ipRegex = new RegExp("\\b(?:" + ipv4 + "|" + ipv6 + ")\\b","g");
+        var matches = text.match(ipRegex);
         return matches;
     },