Merge branch 'ServiceNowDevProgram:main' into improve-ci-classes-readme

Author: ChaseMillers

Client-Side Components/Catalog Client Script/Set and Lock Variable by Group/README.md

@@ -0,0 +1,5 @@
+**Set and Lock Variable by Group**
+
+This solution provides a secure and dynamic way to control data entry on a Service Catalog form based on the user's group membership. It is typically used to pre-fill and lock certain justification or approval bypass fields for authorized users (like managers or executive staff), improving their efficiency while maintaining an accurate audit trail.
+
+This functionality requires a combined Client-side (Catalog Client Script) and Server-side (Script Include) approach to ensure the group check is done securely.

Client-Side Components/Catalog Client Script/Set and Lock Variable by Group/set_lock_variable_by_grp.js

@@ -0,0 +1,33 @@
+// onload Catalog Client Script with Catalog Name 
+function onLoad() {
+    var variableName = 'bypass_approval_reason';
+    var targetGroupName = 'ServiceNow Support'; // The group authorized to skip this step
+    var ga = new GlideAjax('UserUtils');
+    ga.addParam('sysparm_name', 'isMemberOf');
+    ga.addParam('sysparm_group_name', targetGroupName);
+    ga.getXMLAnswer(checkAndLockVariable);
+    function checkAndLockVariable(response) {
+        var isMember = response;
+        if (isMember == 'true') {
+            var message = 'Value set and locked due to your ' + targetGroupName + ' membership.';
+            var setValue = 'Bypassed by authorized ' + targetGroupName + ' member.';
+            g_form.setValue(variableName, setValue);
+            g_form.setReadOnly(variableName, true);
+            g_form.showFieldMsg(variableName, message, 'info');
+        } else {
+            g_form.setReadOnly(variableName, false);
+        }
+    }
+}
+
+//Script Include
+var UserUtils = Class.create();
+UserUtils.prototype = Object.extendsObject(AbstractAjaxProcessor, {
+    isMemberOf: function() {
+        var groupName = this.getParameter('sysparm_group_name');
+        var isMember = gs.getUser().isMemberOf(groupName);
+        return isMember.toString();
+    },
+
+    type: 'UserUtils'
+});

Client-Side Components/Client Scripts/Dynamic Reference Qualifier with Filtering/README.md

@@ -0,0 +1,6 @@
+**Dynamic Reference Qualifier with Filtering**
+This Client Script provides a solution for dynamically updating the available options in a Reference Field based on the value selected in another field on the same form.
+
+This technique is essential for ensuring data quality and improving the user experience (UX). 
+
+A typical use case is filtering the Assignment Group field to show only groups relevant to the selected Service, Category, or Location.

Client-Side Components/Client Scripts/Dynamic Reference Qualifier with Filtering/reference_qual_dynamic.js

@@ -0,0 +1,14 @@
+ function onChange(control, oldValue, newValue, isLoading, isTemplate) {
+    if (isLoading || newValue === '') {
+        return;
+    }
+    var controlledField = 'assignment_group'; 
+    var controllingField = 'u_service';     
+    var serviceSysId = g_form.getValue(controllingField);
+    var encodedQuery = 'typeLIKEITIL^u_related_service=' + serviceSysId;
+    g_form.setQuery(controlledField, encodedQuery);
+    var currentGroupSysId = g_form.getValue(controlledField);
+    if (currentGroupSysId && oldValue !== '' && currentGroupSysId !== '') {
+        g_form.setValue(controlledField, '');
+    }
+}

Server-Side Components/Business Rules/Auto-Generate Knowledge Article for Resolved Incidents/README.md

@@ -0,0 +1,9 @@
+## Overview
+This ServiceNow Business Rule automatically creates a Knowledge Article when an Incident is resolved and includes detailed resolution notes.  
+It helps promote knowledge sharing, reduce repeated issues, and improve ITSM efficiency.
+
+
+## Features
+- Automatically creates a Knowledge Article in the **Draft** state.
+- Extracts content from the Incident's **Resolution Notes**.
+- Prevents duplicate Knowledge Articles by checking for similar issue titles.

Server-Side Components/Business Rules/Auto-Generate Knowledge Article for Resolved Incidents/script.js

@@ -0,0 +1,39 @@
+(function executeRule(current, previous) {
+
+    // Only run when the incident moves to Resolved
+    if (current.state == previous.state || current.state != 6) {
+        return;
+    }
+
+    // Make sure we have resolution notes to use for the KB article
+    if (!current.close_notes) {
+        gs.info('Skipping KB creation: No resolution notes found for ' + current.number);
+        return;
+    }
+
+    // Get a clean version of the short description for comparison
+    var issueTitle = current.short_description ? current.short_description.toLowerCase().trim() : '';
+
+    // Check if a similar KB article already exists
+    var kbCheck = new GlideRecord('kb_knowledge');
+    kbCheck.addQuery('short_description', 'CONTAINS', issueTitle);
+    kbCheck.query();
+
+    if (kbCheck.next()) {
+        gs.info('KB already exists for issue: ' + current.number + '. Skipping new KB creation.');
+        return;
+    }
+
+    // Create a new Knowledge Article
+    var kb = new GlideRecord('kb_knowledge');
+    kb.initialize();
+    kb.short_description = current.short_description;
+    kb.text = current.close_notes;
+    kb.workflow_state = 'draft';
+    kb.kb_category = ''; // You can set a default category if needed
+    kb.u_source_incident = current.number; // Optional: track which incident created it
+    kb.insert();
+
+    gs.info('New KB article created from Incident: ' + current.number);
+
+})(current, previous);