Merge branch 'ServiceNowDevProgram:main' into Hactoberfest-2025-1st-pull-request

Author: Suri123789

Client-Side Components/Client Scripts/Date Range Validation (Within 30 Days)/README.md

@@ -0,0 +1,10 @@
+Date Range Validation (Within 30 Days) in Client Side
+
+This ServiceNow client script provides real-time date validation for form fields, ensuring users can only select dates within a specific 30-day window from today's date. The script runs automatically when a user changes a date field value, providing immediate feedback and preventing invalid date submissions.
+
+The script validates that any date entered in a form field meets these criteria:
+Minimum Date: Today's date (no past dates allowed)
+Maximum Date: 30 days from today's date
+Real-time Validation: Instant feedback as users type or select dates
+User-friendly Errors: Clear error messages explaining the valid date range
+Automatic Field Clearing: Invalid dates are automatically cleared to prevent submission

Client-Side Components/Client Scripts/Date Range Validation (Within 30 Days)/dateRangeValidation.js

@@ -0,0 +1,23 @@
+function onChange(control, oldValue, newValue, isLoading, isTemplate) {
+    if (isLoading || newValue === '') {
+        return;
+    }
+    
+    var todayDate = new Date();
+    var futureDate = new Date();
+    futureDate.setDate(futureDate.getDate() + 30);
+    
+    var todayDateStr = formatDate(todayDate, g_user_date_format);
+    var futureDateStr = formatDate(futureDate, g_user_date_format);
+    
+    var selectedDateNum = getDateFromFormat(newValue, g_user_date_format);
+    var todayDateNum = getDateFromFormat(todayDateStr, g_user_date_format);
+    var futureDateNum = getDateFromFormat(futureDateStr, g_user_date_format);
+    
+    if (selectedDateNum < todayDateNum || selectedDateNum > futureDateNum) {
+        g_form.showFieldMsg(control, 'Date must be between today and 30 days from today', 'error');
+        g_form.clearValue(control);
+    } else {
+        g_form.hideFieldMsg(control);
+    }
+}

Client-Side Components/Client Scripts/Field Validations/README.md

@@ -0,0 +1,12 @@
+An `onLoad` client script that validates required fields in specific ServiceNow form views.
+
+This ServiceNow client script provides automatic validation of required form fields when users access specific form views. The script runs immediately when a form loads and checks that critical fields are populated, displaying user-friendly error messages for any missing required information. This ensures data completeness and improves form submission success rates by catching validation issues early in the user workflow.
+
+What This Script Does:
+The onLoad client script performs comprehensive field validation with these key capabilities:
+View-Specific Validation: Only triggers validation when accessing a designated form view
+Multiple Field Support: Validates multiple required fields simultaneously in a single operation
+Smart Field Detection: Uses field labels (not technical names) in error messages for better user experience
+Consolidated Error Display: Shows all missing required fields in a single, clear error message
+Immediate Feedback: Provides instant validation results as soon as the form loads
+Non-Intrusive Design: Displays informational errors without blocking form interaction

Client-Side Components/Client Scripts/Field Validations/fieldValidation.js

@@ -0,0 +1,23 @@
+function onLoad(){
+  var targetViewName = 'your_target_view_name';
+    var requiredFields = ['field1', 'field2', 'field3'];
+    
+    var currentViewName = g_form.getViewName();
+    
+    if (currentViewName === targetViewName) {
+        var emptyFields = [];
+        
+        for (var i = 0; i < requiredFields.length; i++) {
+            var fieldValue = g_form.getValue(requiredFields[i]);
+            if (!fieldValue || fieldValue.trim() === '') {
+                emptyFields.push(g_form.getLabelOf(requiredFields[i]));
+            }
+        }
+        
+        if (emptyFields.length > 0) {
+            var errorMessage = "The following required fields cannot be empty: " + 
+                             emptyFields.join(', ');
+            g_form.addErrorMessage(errorMessage);
+        }
+    }
+}

Core ServiceNow APIs/GlideAggregate/Find Oldest Open Incidents per Group/README.md

@@ -0,0 +1,38 @@
+ServiceNow Script: Find Oldest Open Incidents per Group
+This script leverages GlideAggregate to efficiently find the oldest active incident for each assignment group. This is a powerful tool for monitoring and reporting on potential service level agreement (SLA) risks and improving incident management processes.
+Overview
+The script performs the following actions:
+Initializes GlideAggregate: Creates an aggregate query on the incident table.
+Filters Active Incidents: Uses addActiveQuery() to restrict the search to only open (active) incidents.
+Aggregates by Minimum Date: Finds the minimum (MIN) opened_at date, which represents the oldest record.
+Groups by Assignment Group: Groups the results by the assignment_group to get a separate result for each team.
+Iterates and Logs: Loops through the query results and logs the assignment group and the opening date of its oldest open incident.
+How to use
+This script is intended to be used in a server-side context within a ServiceNow instance. Common use cases include:
+Scheduled Job: Run this script on a regular schedule (e.g., daily) to generate a report on aging incidents.
+Script Include: Incorporate the logic into a reusable function within a Script Include, allowing other scripts to call it.
+
+Use code with caution.
+
+Installation
+As a Scheduled Job
+Navigate to System Definition > Scheduled Jobs.
+Click New and select Automatically run a script of your choosing.
+Name the job (e.g., Find Oldest Open Incidents).
+Set your desired frequency and time.
+Paste the script into the Run this script field.
+Save and activate the job.
+As a Script Include
+Navigate to System Definition > Script Includes.
+Click New.
+Name it (e.g., IncidentHelper).
+API Name: global.IncidentHelper
+
+
+Customization
+Change the output: Modify the gs.info() line to instead write to a custom log, send an email, or create a report.
+Refine the query: Add more addQuery() statements to filter incidents by other criteria, such as priority or category.
+Change the aggregate: Use MAX instead of MIN to find the newest incident in each group.
+Get incident details: To get the actual incident record (e.g., its number), you would need to perform a secondary GlideRecord query based on the aggregated data.
+Dependencies
+This script uses standard ServiceNow APIs (GlideAggregate, gs). No external libraries are required.

Core ServiceNow APIs/GlideAggregate/Find Oldest Open Incidents per Group/script.js

@@ -0,0 +1,11 @@
+var ga = new GlideAggregate('incident');
+    ga.addActiveQuery();
+    ga.addAggregate('MIN', 'opened_at');
+    ga.groupBy('assignment_group');
+    ga.query();
+
+    while (ga.next()) {
+        var group = ga.assignment_group.getDisplayValue();
+        var oldestIncidentDate = ga.getAggregate('MIN', 'opened_at');
+        gs.info("Oldest open incident for " + group + " was created on: " + oldestIncidentDate);
+    }

Integration/RESTMessageV2/External ML Model Integration/Call ML Prediction API/README.md

@@ -0,0 +1,44 @@
+# Integrate ServiceNow with External ML Model API
+
+## Overview
+Call an external ML API from ServiceNow to get AI predictions for incidents and auto-update records.
+
+## What It Does
+- Sends incident data to external ML API via REST call
+- Receives predictions (resolution time, category, priority, etc.)
+- Automatically updates incident record with predictions
+- Includes error handling and logging
+
+## Use Cases
+- Predict how long an incident will take to resolve
+- Auto-suggest the right category/priority
+- Recommend best assignment group
+- Get risk scores for changes
+
+## Files
+- `ml_prediction_script_include.js` - Script Include that calls ML API
+
+## How to Use
+1. Create Script Include in ServiceNow named `MLPredictionClient`
+2. Copy code from `ml_prediction_script_include.js`
+3. Update `ML_API_URL` and `API_KEY` with your ML service details
+4. Call it from a Business Rule or Client Script to get predictions
+5. Store results back in incident fields
+
+## Example Usage
+```javascript
+var mlClient = new MLPredictionClient();
+var prediction = mlClient.predictIncident({
+    description: incident.description,
+    category: incident.category,
+    priority: incident.priority
+});
+
+incident.estimated_resolution_time = prediction.predicted_resolution_time;
+incident.update();
+```
+
+## Requirements
+- ServiceNow instance
+- External ML API endpoint (REST)
+- API key or token

Integration/RESTMessageV2/External ML Model Integration/Call ML Prediction API/ml_prediction_script_include.js

@@ -0,0 +1,43 @@
+// Script Include: MLPredictionClient
+// Calls external ML API to get incident predictions
+
+var MLPredictionClient = Class.create();
+MLPredictionClient.prototype = {
+    initialize: function() {
+        this.ML_API_URL = 'https://your-ml-api.com/predict';
+        this.API_KEY = 'your-api-key-here';
+    },
+    
+    predictIncident: function(incidentData) {
+        try {
+            var request = new RESTMessageV2();
+            request.setEndpoint(this.ML_API_URL);
+            request.setHttpMethod('POST');
+            request.setRequestHeader('Authorization', 'Bearer ' + this.API_KEY);
+            request.setRequestHeader('Content-Type', 'application/json');
+            
+            // Send incident details to ML API
+            var payload = {
+                description: incidentData.description,
+                category: incidentData.category,
+                priority: incidentData.priority
+            };
+            request.setRequestBody(JSON.stringify(payload));
+            
+            // Get prediction from external ML service
+            var response = request.execute();
+            var result = JSON.parse(response.getBody());
+            
+            return {
+                estimated_hours: result.estimated_hours,
+                predicted_category: result.category,
+                confidence: result.confidence
+            };
+        } catch (error) {
+            gs.log('ML API Error: ' + error, 'MLPredictionClient');
+            return null;
+        }
+    },
+    
+    type: 'MLPredictionClient'
+};

Server-Side Components/Background Scripts/Capture Scheduled Job in an Update set/README.md

@@ -0,0 +1,5 @@
+Scheduled Job Update Set Capture Script
+
+This ServiceNow background script addresses a critical deployment challenge by programmatically capturing scheduled jobs in update sets. 
+By default, ServiceNow scheduled jobs are not automatically captured in update sets, making them difficult to migrate between environments. 
+This script uses the GlideUpdateManager2 API to force a scheduled job record into the current update set, enabling seamless deployment through standard update set processes.

Server-Side Components/Background Scripts/Capture Scheduled Job in an Update set/captureScheduledJob.js

@@ -0,0 +1,4 @@
+var gr = new GlideRecord('sysauto_script');
+gr.get('<sys_id of your scheduled job>');
+var gum = new GlideUpdateManager2();
+gum.saveRecord(gr);