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

Author: ChaseMillers

Client-Side Components/UI Actions/Smart Assign to available member/README.md

@@ -0,0 +1,18 @@
+**Use-case:**
+The primary goal of this UI Action is load-balancing.
+It assigns tasks based on the fewest currently Active tasks assigned to a member in a group.
+
+**Example Scenario**:
+An assignment group has 10 members. Instead of assigning a new task to the whole group or any random member, the user/agent clicks on
+"Smart Assign" to find the member with the fewest currently Active tasks in the same group and assign the task to them.
+
+**UI Action Name:**
+Smart Assign
+
+**Condition**: !current.assignment_group.nil() && current.assigned_to.nil()
+
+**How it works:**
+1. The code queries the Group members table to find every single user associated with the currently selected assignment group.
+   If someone removes a previous assignement group and then clicks on Smart Assign button, they are shown an error message to choose an Assignment group.
+2. There is a loop on the task table. This loop uses GlideAggregate to count how many active records are assigned to a specific user.
+3. It tracks the user that has the lowest count of tasks assigned to them and assigns the current task to them.

Client-Side Components/UI Actions/Smart Assign to available member/smartAssigntoAvailablemember.js

@@ -0,0 +1,47 @@
+var assignedToId = '';
+var minOpenTasks = 77777;
+var targetGroup = current.assignment_group;
+
+if (!targetGroup) {
+    gs.addErrorMessage('Please select an Assignment Group first.');
+    action.setRedirectURL(current);
+}
+
+//Finding all active members in the target group
+var member = new GlideRecord('sys_user_grmember');
+member.addQuery('group', targetGroup);
+member.query();
+
+while (member.next()) {
+    var userId = member.user.toString();
+
+    //CountIng the number of active tasks currently assigned to the member
+    var taskCountGR = new GlideAggregate('task');
+    taskCountGR.addQuery('assigned_to', userId);
+    taskCountGR.addQuery('active', true);
+    taskCountGR.addAggregate('COUNT');
+    taskCountGR.query();
+
+    var openTasks = 0;
+    if (taskCountGR.next()) {
+        openTasks = taskCountGR.getAggregate('COUNT');
+    }
+
+    //Checking if this member has fewer tasks than the current minimum
+    if (openTasks < minOpenTasks) {
+        minOpenTasks = openTasks;
+        assignedToId = userId;
+    }
+}
+
+//Assigning the current record to the chosen user
+if (assignedToId) {
+    current.assigned_to = assignedToId;
+    current.work_notes = 'Assigned via Smart Assign to the user with the fewest active tasks (' + minOpenTasks + ' open tasks).';
+    current.update();
+    gs.addInfoMessage('Incident assigned to ' + current.assigned_to.getDisplayValue() + '.');
+} else {
+    gs.addErrorMessage('Could not find an active member in the group to assign the task.');
+}
+
+action.setRedirectURL(current);

Modern Development/Service Portal Widgets/Open in Platform/README.md

@@ -1,3 +1,6 @@
-Widget will create a button that will only be visable to users with the itil role that will take them to the same record in platform. will work with the form and standard ticket pages (or anywhere with the table and sysId in the url.
+**This is an enhancement to the current code**
+1. Added "open in SOW" Button to open the record in service operations workspace, since it is gaining popularity now.
+2. Enhanced the visibility condition so that the button is only visible on pages having sys_id and table in url.
+3. Enhanced css to improve visibility of button.
 
-see also [on Share](https://developer.servicenow.com/connect.do#!/share/contents/6592535_open_in_platform_widget?t=PRODUCT_DETAILS)
+Widget will create a button that will only be visable to users with the itil role that will take them to the same record in platform. will work with the form and standard ticket pages (or anywhere with the table and sysId in the url.

Modern Development/Service Portal Widgets/Open in Platform/body.html

@@ -1,5 +1,6 @@
 <div>
- <span ng-if="::data.role==true">
-   <a href="{{::data.url}}" target='_blank'class='btn btn-default'>{{::options.button_text}}</a>
- </span>
+  <span class="btn-cntr" ng-if="::data.role==true">
+    <a href="{{::data.platform_url}}" target='_blank'class='btn btn-default'>{{::options.open_in_platform}}</a><br> <!--Platform button configuration-->
+    <a href="{{::data.sow_url}}" target='_blank'class='btn btn-default'>{{::options.open_in_sow}}</a>  <!--SOW button configuration-->
+  </span>
 </div>

Modern Development/Service Portal Widgets/Open in Platform/css.js

@@ -0,0 +1,7 @@
+/*
+This styling will align buttons on 2 ends of the div.
+*/
+.btn-cntr{
+display: flex;
+justify-content: space-between;
+}

Modern Development/Service Portal Widgets/Open in Platform/option schema.js

@@ -0,0 +1,14 @@
+[
+{
+"name":"open_in_platform",
+"type":"string",
+"label":"Name for Plarform Button",
+"default_value":"Open in Platform"
+},
+{
+"name":"open_in_sow",
+"type":"string",
+"label":"Name for SOW Button",
+"default_value":"Open in SOW"
+}
+]

Modern Development/Service Portal Widgets/Open in Platform/server.js

@@ -1,11 +1,16 @@
 (function() {
-	data.table = input.table || $sp.getParameter("table");
-	data.sys_id = input.sys_id || $sp.getParameter("sys_id");
-	
-	data.url = "/nav_to.do?uri="+data.table+".do?sys_id="+data.sys_id;
-	
-	data.role = false;
-	if (gs.hasRole("itil")){
-		data.role = true;
-	}
+    /*
+    Code will get table and sys_id parameter from url and create url for platform and sow.
+    This widget can be used in any page having sys_id and table in url , eg: ticket page.
+    */
+    data.table = input.table || $sp.getParameter("table"); // get table from url
+    data.sys_id = input.sys_id || $sp.getParameter("sys_id"); // get sys_id from url
+
+    data.platform_url = "/nav_to.do?uri=" + data.table + ".do?sys_id=" + data.sys_id;
+    data.sow_url = "now/sow/record/" + data.table + "/" + data.sys_id;
+
+    data.role = false;
+    if (gs.hasRole("itil") && data.table && data.sys_id) { // only visible to users with itil role and if url has required parameters.
+        data.role = true;
+    }
 })();

Server-Side Components/Business Rules/Calculate Incident Duration and Validation/Duration.js

@@ -0,0 +1,36 @@
+(function executeRule(current, previous /*null when async*/ ) {
+
+    /*
+		Inputs
+		1. Opened(opened_at)
+		2. Resolved(resolved_at)
+
+		Checks & Validation
+		1. It will check the Date/Time validation whether it Resolved time should be greater than Open time 
+		2. And it will not calculate the empty values
+
+		Outputs
+		1. If everthing has a right value like the Opened < Resolve Date/Time then Duration will be calculated and populated in the respective field
+		2. Negative case if Opened > Resolved the duration will not calculate and it will Abort the action to save the record with Error message.
+	*/
+
+	// Getting both the date from the record
+    var opened = GlideDateTime(current.opened_at.getDisplayValue());
+    var resolved = GlideDateTime(current.resolved_at.getDisplayValue());
+
+    //If the opened and resolved times are present, calculate the duration
+    if (opened && resolved) {
+        var difference = GlideDateTime.subtract(opened, resolved);
+        if (difference.getYearUTC() >= 1970)
+            current.calendar_duration.setValue(difference);
+        else {
+            current.calendar_duration.setValue(null);
+            current.resolved_at.setValue(null);
+            current.setAbortAction(true);
+            gs.addErrorMessage("Incident Resolve date/time must be greater than incident Opened date/time");
+        }
+    }
+
+
+
+})(current, previous);

Server-Side Components/Business Rules/Calculate Incident Duration and Validation/Readme.md

@@ -0,0 +1,11 @@
+Calculate Incident Duration and Validation.
+
+Script Type : Business Rule Trigger: before update Table: incident Condition: Resolved Changes or Opened Changes
+
+Goal : To calculate the duration of a particular record and how much time has been spent on a particular ticket.
+
+Walk through of code :
+So when the Resolved Changes or Opened Changes in a particular record to calculate the duration will this Business rule will pull those values
+And then check whether the Opened Data/Time is lesser than the Resolved Date/Time the will calculate the duration 
+Else it will throw the Error Message and then Abort that action and won't save the record and will clear the values.
+

Server-Side Components/Server Side/Dynamic Catalog Task Creation/README.md

@@ -0,0 +1,10 @@
+**Dynamic Catalog Task Generator**
+
+This Script Include provides a flexible, maintainable way to create one or more Service Catalog Tasks (sc_task) on a Request Item (sc_req_item). Instead of relying on complex, branching logic within a single Workflow or Flow, this script determines which tasks to create based on the value selected by the user in a single variable on the catalog form.
+
+
+**Centralizes Task Logic**: Keeps all task definitions (short descriptions, assignment groups, order) in one easy-to-read script.
+
+**Improves Maintainability**: You only update this single script when task requirements change, not a sprawling visual flow.
+
+**Increases Flow Reusability**: The core Flow/Workflow remains simple, focused only on calling this generator.