Merge branch 'main' of https://github.com/ChaseMillers/code-snippets

Author: ChaseMillers

Integration/Mail Scripts/Redact PII from outbound email body/README.md

@@ -0,0 +1,22 @@
+# Redact PII from outbound email body
+
+## What this solves
+Notifications sometimes leak personal data into emails. This mail script replaces common identifiers in the email body with redacted tokens before send.
+
+## Where to use
+Notification or Email Script record, Advanced view, "Mail script" field. Invoke the function to get a safe body string and print it.
+
+## How it works
+- Applies regex patterns to the email text for emails, phone numbers, IP addresses, NI number style patterns, and 16-digit card-like numbers
+- Replaces matches with descriptive placeholders
+- Leaves HTML tags intact by operating on the plain text portion you pass in
+
+## Configure
+- Extend or tighten patterns for your organisation
+- Toggle specific scrubs on or off in the config block
+
+## References
+- Email Scripts  
+  https://www.servicenow.com/docs/bundle/zurich-platform-administration/page/administer/notification/reference/email-scripts.html
+- Notifications  
+  https://www.servicenow.com/docs/bundle/zurich-platform-administration/page/administer/notification/concept/c_EmailNotifications.html

Integration/Mail Scripts/Redact PII from outbound email body/mail_redact_pii.js

@@ -0,0 +1,54 @@
+// Mail Script: Redact PII from outbound email body
+// Usage inside a Notification (Advanced view):
+//   var safe = redactPii(current.short_description + '\n\n' + current.description);
+//   template.print(safe);
+
+(function() {
+  function redactPii(text) {
+    if (!text) return '';
+
+    // Config: toggle specific redactions
+    var cfg = {
+      email: true,
+      phone: true,
+      ip: true,
+      niNumber: true,
+      card16: true
+    };
+
+    var out = String(text);
+
+    // Email addresses
+    if (cfg.email) {
+      out = out.replace(/\b[A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,}\b/gi, '[redacted email]');
+    }
+
+    // Phone numbers (UK leaning, permissive, 7+ digits ignoring separators)
+    if (cfg.phone) {
+      out = out.replace(/\b(?:\+?\d{1,3}[\s-]?)?(?:\(?\d{3,5}\)?[\s-]?)?\d{3,4}[\s-]?\d{3,4}\b/g, '[redacted phone]');
+    }
+
+    // IPv4 addresses
+    if (cfg.ip) {
+      out = out.replace(/\b(?:(?:25[0-5]|2[0-4]\d|1?\d?\d)\.){3}(?:25[0-5]|2[0-4]\d|1?\d?\d)\b/g, '[redacted ip]');
+    }
+
+    // National Insurance number style (AA 00 00 00 A) simplified - UK Specific
+    if (cfg.niNumber) {
+      out = out.replace(/\b([A-CEGHJ-PR-TW-Z]{2}\s*\d{2}\s*\d{2}\s*\d{2}\s*[A-D])\b/gi, '[redacted ni]');
+    }
+
+    // 16 consecutive digits that look like a card (permit separators)
+    if (cfg.card16) {
+      out = out.replace(/\b(?:\d[ -]?){13,19}\b/g, function(match) {
+        var digits = match.replace(/[ -]/g, '');
+        return digits.length >= 13 && digits.length <= 19 ? '[redacted card]' : match;
+      });
+    }
+
+    return out;
+  }
+
+  // Expose function to the mail template scope
+  this.redactPii = redactPii;
+}).call(this);

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

@@ -1,6 +1,19 @@
 **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.
+1. Added "open in Workspace" Button to open the record in workspace(defined in option schema), 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.
+4. This button wll look for the table to workspace mapping (in option schema) and create the URL to open record in respective workspace. If now mapping is found, the record is opened in SOW workspace(default).
+5. The button name has been changed to generic title "Open In Workspace"
 
-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.
+**Sample**
+{
+"name":"define_workspace",
+"type":"json",
+"label":"Define Table Workspace JSON Mapping",
+"value":{
+  "sn_grc_issue":"risk/privacy", // will open issue records in RISK workspace
+  "sn_si_incident":"sir" // will open security incidents in SIR workspace.
+}
+}
+
+Widget will create a button that will only be visible 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,6 +1,6 @@
 <div>
   <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-->
+    <a href="{{::data.workspace_url}}" target='_blank'class='btn btn-default'>{{::options.open_in_workspace}}</a>  <!--Workspace button-->
   </span>
 </div>

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

@@ -6,9 +6,18 @@
 "default_value":"Open in Platform"
 },
 {
-"name":"open_in_sow",
+"name":"open_in_workspace",
 "type":"string",
-"label":"Name for SOW Button",
-"default_value":"Open in SOW"
+"label":"Name for Workspace Button",
+"default_value":"Open In workspace"
+},
+{
+"name":"define_workspace",
+"type":"json",
+"label":"Define Table Workspace JSON Mapping",
+"value":{
+  "sn_grc_issue":"risk/privacy",
+  "sn_si_incident":"sir"
+}
 }
 ]

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

@@ -1,13 +1,19 @@
 (function() {
     /*
-    Code will get table and sys_id parameter from url and create url for platform and sow.
+    Code will get table and sys_id parameter from url and create url for platform and workspace(defined in option schema).
     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.table = $sp.getParameter("table"); // get table from url
+    data.sys_id = $sp.getParameter("sys_id"); // get sys_id from url
 
+    var tableWorkspaceMapping = JSON.parse(options.define_workspace); // get the table to workspace mapping from instance options.
+    Object.keys(tableWorkspaceMapping).forEach(function(key) {
+        if (key == data.table)
+            data.workspace_url = "now/" + tableWorkspaceMapping[key] + "/record/" + data.table + "/" + data.sys_id; // if table to workspce mapping is found, the create workspace URL.
+        else
+            data.workspace_url = "now/sow/record/" + data.table + "/" + data.sys_id; // open in SOW
+    });
     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.

Specialized Areas/Data Quality/Similarity Calculator/README.md

@@ -0,0 +1,32 @@
+# Similarity Calculator for ServiceNow Incidents
+
+## Overview
+This utility provides manual similarity scoring between ServiceNow incident records using text analysis, without requiring machine learning. It helps developers and admins find similar incidents by comparing descriptions and calculating similarity scores programmatically.
+
+## How It Works
+1. Extracts keywords from incident descriptions
+2. Compares keyword overlap between incidents
+3. Calculates a similarity score (0-100%)
+4. Finds and ranks similar incidents based on score
+
+## Features
+- Compare incident descriptions using keyword matching
+- Calculate similarity scores between incidents
+- Find and rank similar incidents programmatically
+- No ML or Predictive Intelligence required
+
+## Use Cases
+- Manual clustering of incidents
+- Identifying duplicate or related tickets
+- Data quality analysis before ML model training
+- Root cause analysis and incident triage
+
+## Setup Requirements
+- ServiceNow instance with access to the `incident` table
+- Script execution permissions (Background Script or Script Include)
+- No external dependencies
+
+## Customization
+- Adjust keyword extraction logic for your environment
+- Change scoring algorithm to use TF-IDF, cosine similarity, etc.
+- Filter by assignment group, category, or other fields

Specialized Areas/Data Quality/Similarity Calculator/similarity_calculator.js

@@ -0,0 +1,97 @@
+// ========================================
+// Similarity Calculator for ServiceNow Incidents
+// ========================================
+// Purpose: Manually score similarity between incidents using text analysis
+// No ML required
+// ========================================
+
+(function similarityCalculator() {
+    // --- CONFIG ---
+    var config = {
+        table: 'incident',
+        baseIncidentSysId: '89b325155370f610de0038e0a0490ec5', // Set to the sys_id of the incident to compare
+        fields: ['short_description', 'description'],
+        maxResults: 50,
+        minSimilarity: 0 // Minimum similarity % to report
+    };
+
+    // --- Helper: Extract keywords from text ---
+    function extractKeywords(text) {
+        if (!text) return [];
+        // Simple keyword extraction: split, lowercase, remove stopwords
+        var stopwords = ['the','and','a','an','to','of','in','for','on','with','at','by','from','is','it','this','that','as','are','was','were','be','has','have','had','but','or','not','can','will','do','does','did','if','so','then','than','too','very','just','also','into','out','up','down','over','under','again','more','less','most','least','such','no','yes','you','your','our','their','my','me','i'];
+        var words = text.toLowerCase().replace(/[^a-z0-9 ]/g, ' ').split(/\s+/);
+        var keywords = [];
+        for (var i = 0; i < words.length; i++) {
+            var word = words[i];
+            if (word && stopwords.indexOf(word) === -1 && word.length > 2) {
+                keywords.push(word);
+            }
+        }
+        return keywords;
+    }
+
+    // --- Helper: Calculate similarity score ---
+    function calcSimilarity(keywordsA, keywordsB) {
+        if (!keywordsA.length || !keywordsB.length) return 0;
+        var mapA = {};
+        var mapB = {};
+        for (var i = 0; i < keywordsA.length; i++) {
+            mapA[keywordsA[i]] = true;
+        }
+        for (var j = 0; j < keywordsB.length; j++) {
+            mapB[keywordsB[j]] = true;
+        }
+        var intersection = 0;
+        var unionMap = {};
+        for (var k in mapA) {
+            unionMap[k] = true;
+            if (mapB[k]) intersection++;
+        }
+        for (var l in mapB) {
+            unionMap[l] = true;
+        }
+        var union = Object.keys(unionMap).length;
+        return union ? (intersection / union * 100) : 0;
+    }
+
+    // --- Get base incident ---
+    var baseGr = new GlideRecord(config.table);
+    if (!baseGr.get(config.baseIncidentSysId)) {
+        gs.error('Base incident not found: ' + config.baseIncidentSysId);
+        return;
+    }
+    var baseText = config.fields.map(function(f) { return baseGr.getValue(f); }).join(' ');
+    var baseKeywords = extractKeywords(baseText);
+
+    // --- Find candidate incidents ---
+    var gr = new GlideRecord(config.table);
+    gr.addQuery('active', true);
+    gr.addQuery('sys_id', '!=', config.baseIncidentSysId);
+    gr.setLimit(config.maxResults);
+    gr.query();
+
+    var results = [];
+    while (gr.next()) {
+        var compareText = config.fields.map(function(f) { return gr.getValue(f); }).join(' ');
+        var compareKeywords = extractKeywords(compareText);
+        var score = calcSimilarity(baseKeywords, compareKeywords);
+        results.push({
+            sys_id: gr.getUniqueValue(),
+            number: gr.getValue('number'),
+            short_description: gr.getValue('short_description'),
+            similarity: score
+        });
+    }
+
+    // --- Sort and print results ---
+    results.sort(function(a, b) { return b.similarity - a.similarity; });
+    gs.info('=== Similarity Results ===');
+    for (var i = 0; i < results.length; i++) {
+        var r = results[i];
+        gs.info((i+1) + '. ' + r.number + ' (' + r.similarity.toFixed(1) + '%) - ' + r.short_description);
+    }
+    if (results.length === 0) {
+        gs.info('No similar incidents found above threshold.');
+    }
+})();

Specialized Areas/Predictive Intelligence/Training Data Preparer/README.md

@@ -0,0 +1,42 @@
+# Training Data Quality Analyzer for ServiceNow Predictive Intelligence
+
+## Overview
+This script analyzes the quality of incident data in ServiceNow to determine readiness for Predictive Intelligence (PI) model training. It provides detailed statistics and quality metrics to help ServiceNow developers and admins identify and address data issues before starting ML training jobs.
+
+## Purpose
+- Assess completeness and quality of key fields in incident records
+- Identify common data issues that could impact PI model performance
+- Provide actionable insights for improving training data
+
+## Features
+- Checks completeness of important fields (e.g., short_description, description, category, subcategory, close_notes, assignment_group)
+- Analyzes text quality for description and close notes
+- Evaluates category diversity and resolution times
+- Calculates an overall data quality score
+- Outputs results to the ServiceNow system logs
+
+## Setup Requirements
+1. **ServiceNow Instance** with Predictive Intelligence plugin enabled
+2. **Script Execution Permissions**: Run as a background script or Script Include with access to the `incident` table
+3. **No external dependencies**: Uses only standard ServiceNow APIs (GlideRecord, GlideAggregate, GlideDateTime)
+4. **Sufficient Data Volume**: At least 50 resolved/closed incidents recommended for meaningful analysis
+
+## How It Works
+1. **Field Existence Check**: Dynamically verifies that each key field exists on the incident table or its parent tables
+2. **Statistics Gathering**: Collects counts for total, resolved, and recent incidents
+3. **Completeness Analysis**: Calculates the percentage of records with each key field filled
+4. **Text Quality Analysis**: Measures average length and quality of description and close notes
+5. **Category Distribution**: Reports on the spread and diversity of incident categories
+6. **Resolution Time Analysis**: Evaluates how quickly incidents are resolved
+7. **Quality Scoring**: Combines all metrics into a single overall score
+8. **Log Output**: Prints all results and warnings to the ServiceNow logs for review
+
+## Customization
+- Adjust the `keyFields` array in the config section to match your organization's data requirements
+- Modify thresholds for text length, resolution time, and completeness as needed
+- Increase `sampleSize` for more detailed analysis if you have a large dataset
+
+## Security & Best Practices
+- Do not run in production without review
+- Ensure no sensitive data is exposed in logs
+- Validate script results in a sub-production environment before using for model training