Merge branch 'ServiceNowDevProgram:main' into main

Author: raghavs046

Client-Side Components/Catalog Client Script/Autopopulate user information fields/ClientCallableScriptInclude.js

@@ -0,0 +1,25 @@
+/*
+* The following is a client callable script include. This can be used with the onChange Client script to be able to gather the data on the server side
+*/
+
+var ReferenceQualifierAjaxHelper = Class.create();
+ReferenceQualifierAjaxHelper.prototype = Object.extendsObject(AbstractAjaxProcessor, {
+  getUserInformation : function() {
+    var userID = this.getParameter('sysparm_user');
+    var userRec = new GlideRecord('sys_user');
+
+    if(userRec.get(userID)) {
+      var results = {
+        "email" : userRec.getValue('email'),
+        "department" : userRec.getValue('department'),
+        "title" : userRec.getValue('title'),
+        "phone" : userRec.getValue('phone')
+      };
+
+      return JSON.stringify(results)
+    }
+
+  },
+  
+  type: 'ReferenceQualifierAjaxHelper'
+});

Client-Side Components/Catalog Client Script/Autopopulate user information fields/README.md

@@ -0,0 +1,6 @@
+## Overview
+This onchange catalog client script and script inlcude work together autopopulate the user fields that might show up on a catalog item. In the 
+global scope you will have to create the client callable script include to be able to use the Ajax call that is in the on change client script.
+In this example we use the OOB Requested For field that already auto populates the user that is logged in then we go to the server to get that 
+users information. The fields that are brough back are the ones that are in the code but you can modify to bring back more or less fields if needed.
+

Client-Side Components/Catalog Client Script/Autopopulate user information fields/onChangeClientScript.js

@@ -0,0 +1,23 @@
+/*
+* In order for this to work make sure to have an onChange catalog client script on a variable that is type Requested For. This variable
+* already autopopulates the logged in user with its OOB functionality. In the updateUserFields function you can add any other user fields
+* that you might need. 
+*/
+
+function onChange(control, oldValue, newValue, isLoading) {
+  //This variable will store the sys_id of the user that populates in your requested for variable
+  var userID = newValue;
+
+  var ga = new GlideAjax(ReferenceQualifierAjaxHelper);
+  ga.addParam('sysparm_name', 'getUserInformation');
+  ga.addParam('sysparm_user', userID);
+  ga.getXMLAnswer(updateUserFields);
+
+  function updateUserFields(response) {
+    var returnedData = JSON.parse(response);
+    g_form.setValue("email", returnedData.email);
+    g_form.setValue("department", returnedData.department);
+    g_form.setValue("title", returnedData.title);
+    g_form.setValue("phone", returnedData.phone);
+  }
+}

Client-Side Components/Catalog Client Script/Catalog Approval/Readme.md

@@ -0,0 +1 @@
+This project adds a dynamic preview feature to Service Catalog items, allowing users to see the full approval chain before submitting a request. It improves transparency, reduces confusion, and helps users understand who will be involved in the approval process based on their selections.

Client-Side Components/Catalog Client Script/Catalog Approval/client script.js

@@ -0,0 +1,10 @@
+function onLoad() {
+  var ga = new GlideAjax('ApprovalChainHelper');
+  ga.addParam('sysparm_name', 'getApprovers');
+  ga.addParam('sysparm_item_id', g_form.getUniqueValue());
+  ga.getXMLAnswer(function(response) {
+    var approvers = JSON.parse(response);
+    var message = 'This request will be approved by: ' + approvers.join(', ');
+    g_form.showFieldMsg('requested_for', message, 'info');
+  });
+}

Client-Side Components/Catalog Client Script/Catalog Approval/script include.js

@@ -0,0 +1,20 @@
+var ApprovalChainHelper = Class.create();
+ApprovalChainHelper.prototype = Object.extendsObject(AbstractAjaxProcessor, {
+  getApprovers: function() {
+    var itemId = this.getParameter('sysparm_item_id');
+    var userId = gs.getUserID();
+
+    var approvers = [];
+
+    // Example logic: fetch approval rules based on item and user
+    var ruleGR = new GlideRecord('sysapproval_approver');
+    ruleGR.addQuery('document_id', 80f8920bc3e4b2105219daec050131e3);
+    ruleGR.query();
+
+    while (ruleGR.next()) {
+      approvers.push(ruleGR.approver.name.toString());
+    }
+
+    return JSON.stringify(approvers);
+  }
+});

Client-Side Components/Catalog Client Script/Document validation/Client script.JS

@@ -0,0 +1,12 @@
+function onSubmit() {
+  var ga = new GlideAjax('DocumentValidationHelper');
+  ga.addParam('sysparm_name', 'validateAttachments');
+  ga.addParam('sysparm_item_id', g_form.getUniqueValue());
+  ga.getXMLAnswer(function(response) {
+    if (response !== 'valid') {
+      alert('Document validation failed: ' + response);
+      return false;
+    }
+  });
+  return true;
+}

Client-Side Components/Catalog Client Script/Document validation/Readme.md

@@ -0,0 +1 @@
+This project enhances a Service Catalog item by allowing users to upload supporting documents (e.g., ID proof, approval letters) and validating them before the request is submitted. It ensures compliance, completeness, and proper documentation for sensitive or regulated requests.

Client-Side Components/Catalog Client Script/Document validation/Script include.js

@@ -0,0 +1,22 @@
+var DocumentValidationHelper = Class.create();
+DocumentValidationHelper.prototype = Object.extendsObject(AbstractAjaxProcessor, {
+  validateAttachments: function() {
+    var itemId = this.getParameter('sysparm_item_id');
+    var attachmentGR = new GlideRecord('sys_attachment');
+    attachmentGR.addQuery('table_name', 'sc_req_item');
+    attachmentGR.addQuery('table_sys_id', itemId);
+    attachmentGR.query();
+
+    while (attachmentGR.next()) {
+      var fileName = attachmentGR.file_name.toLowerCase();
+      if (!fileName.endsWith('.pdf') && !fileName.endsWith('.docx')) {
+        return 'Only PDF or DOCX files are allowed.';
+      }
+      if (attachmentGR.size_bytes > 5 * 1024 * 1024) {
+        return 'File size exceeds 5MB limit.';
+      }
+    }
+
+    return 'valid';
+  }
+});

Client-Side Components/Catalog Client Script/Multi-User Collaboration/Readme.md

@@ -0,0 +1 @@
+This project introduces a collaboration feature for Service Catalog requests, allowing multiple users to contribute to a single request. It’s ideal for scenarios like team onboarding, shared resource provisioning, or cross-functional workflows.