Merge branch 'ServiceNowDevProgram:main' into main

Author: raghavs046

.github/workflows/pr-auto-unassign-stale.yml

@@ -0,0 +1,23 @@
+name: Unassign stale PR assignees
+on:
+  schedule:
+    - cron: "*/15 * * * *"
+  workflow_dispatch:
+    inputs:
+      enabled:         { type: boolean, default: true }
+      max_age_minutes: { type: number,  default: 60 }
+      dry_run:         { type: boolean, default: false }
+
+permissions:
+  pull-requests: write
+  issues: write
+  contents: read
+
+jobs:
+  call:
+    uses: ServiceNowDevProgram/Hacktoberfest/.github/workflows/unassign-stale.yml@b8c3f56f94d96f263420e2c051d91b791c9494d8
+    with:
+      enabled:         ${{ inputs.enabled }}
+      max_age_minutes: ${{ inputs.max_age_minutes }}
+      dry_run:         ${{ inputs.dry_run }}
+    secrets: inherit

.github/workflows/unassign-stale.yml

@@ -0,0 +1,5 @@
+The script enhances a form field (specifically the description field) by:
+-Adding a live word counter below the field.
+-Visually warning the user if the word count exceeds 150 words.
+
+This client-side script, intended for use in a ServiceNow form (e.g., catalog item or incident form), dynamically appends a custom `<div>` element below the `description` field to display a real-time word count. It leverages the `g_form.getControl()` API to access the field's DOM element and attaches an `input` event listener to monitor user input. The script calculates the word count by splitting the input text using a regular expression (`\s+`) and updates the counter accordingly. It applies conditional styling to the counter (`green` if ≤150 words, `red` if >150), providing immediate visual feedback to the user to enforce input constraints.

Client-Side Components/Client Scripts/Display a Live Word Count for Description Field/README.md

@@ -0,0 +1,11 @@
+function onChange(control, oldValue, newValue, isLoading, isTemplate) {
+    if (isLoading || newValue === oldValue) {
+        return;
+    }
+
+    var wordCount = newValue.trim().split(/\s+/).length;
+    var message = 'Word Count: ' + (newValue ? wordCount : 0);
+    var messageType = (wordCount > 150) ? 'error' : 'info';
+
+    g_form.showFieldMsg('description', message, messageType);
+}

Client-Side Components/Client Scripts/Display a Live Word Count for Description Field/code.js

@@ -0,0 +1,33 @@
+# Smart Field Suggestions Based on Keywords
+
+## Category
+Client-Side Components / Client Scripts
+
+## Description
+This is an onChange Client Script designed for the Incident table that dynamically suggests and populates the Category, Subcategory, and Priority fields based on keywords detected in the Short Description field. By matching keywords, it prompts users to confirm applying suggestions aligned with backend choice values for seamless integration.
+
+## Use Case
+During incident creation or update, manually categorizing tickets correctly is critical for IT operations efficiency. This snippet automates early triage by analyzing user-entered short descriptions, providing actionable suggestions to improve categorization accuracy, accelerate routing, and enhance resolution speed.
+
+## How to Use
+- Add this script as an "onChange" client script on the Incident table's `short_description` field.
+- Ensure the Category, Subcategory, and Priority fields have choice lists aligned with backend values specified in the snippet.
+- Modify the keyword list to align with your organizational terminologies if needed.
+- The user will be prompted with suggestions and may confirm or dismiss them, allowing balanced automation and human control.
+
+## Why This Use Case is Unique and Valuable
+
+- Dynamically assists in categorizing incidents early, improving routing and resolution time.
+- Uses only platform APIs (`g_form`) without custom backend code or external integrations, making it lightweight and maintainable.
+- Uses real backend choice values ensuring seamless compatibility with existing configurations, reducing errors.
+- Provides prompt suggestions with user confirmation, balancing automation and user control.
+- Easily adaptable for other fields, keywords, or use cases beyond Incident management.
+- Designed without fragile DOM manipulations, following ServiceNow best practices, tailored for real environments.
+
+## Compatibility
+This client script is compatible with all standard ServiceNow instances without requiring ES2021 features.
+
+## Files
+- `Smart Field Suggestions Based on Keyword.js` — the client script implementing the logic.
+
+

Client-Side Components/Client Scripts/Smart-Field-Suggestions/README.md

@@ -0,0 +1,73 @@
+function onChange(control, oldValue, newValue, isLoading, isTemplate) {
+    if (isLoading || !newValue || newValue.length < 10) {
+        return;
+    }
+
+    var keywords = [
+        { 
+            pattern: /password|login|access/i, 
+            category: 'inquiry | Help ',             
+            subcategory: 'antivirus',        
+            priority: '3', 
+            suggestion: 'This appears to be a Inquiry issue.' 
+        },
+        { 
+            pattern: /slow|performance|hanging/i, 
+            category: 'software',          
+            subcategory: 'email',          
+            priority: '2', 
+            suggestion: 'This appears to be a Software issue.' 
+        },
+        { 
+            pattern: /printer|print|printing/i, 
+            category: 'hardware',            
+            subcategory: 'monitor',         
+            priority: '3', 
+            suggestion: 'This appears to be a Hardware issue.' 
+        },
+        { 
+            pattern: /database|data/i, 
+            category: 'database',          
+            subcategory: 'db2',             
+            priority: '3', 
+            suggestion: 'This appears to be an Database issue.' 
+        },
+        { 
+            pattern: /network|internet|wifi|connection/i, 
+            category: 'network',             
+            subcategory: 'vpn',               
+            priority: '2', 
+            suggestion: 'This appears to be a network issue.' 
+        }
+        
+    ];
+
+    var lowerDesc = newValue.toLowerCase();
+    var matched = null;
+
+    for (var i = 0; i < keywords.length; i++) {
+        if (keywords[i].pattern.test(lowerDesc)) {
+            matched = keywords[i];
+            break;
+        }
+    }
+
+    g_form.hideFieldMsg('short_description', true);
+    g_form.clearMessages();
+
+    if (matched) {
+        g_form.showFieldMsg('short_description', matched.suggestion, 'info', false);
+
+        if (confirm(matched.suggestion + "\n\nApply these suggestions?")) {
+            g_form.setValue('category', matched.category);
+            g_form.setValue('subcategory', matched.subcategory); // Make sure you use backend value for subcategory!
+            g_form.setValue('priority', matched.priority);
+            g_form.addInfoMessage('Suggestions applied automatically!');
+        } else {
+            g_form.addInfoMessage('Suggestions dismissed.');
+            g_form.hideFieldMsg('short_description', true);
+        }
+    } else {
+        g_form.addInfoMessage('No keywords matched in description.');
+    }
+}

Client-Side Components/Client Scripts/Smart-Field-Suggestions/Smart Field Suggestions Based on Keyword.js

@@ -1,3 +1,9 @@
 onSubmit Function: This client script validates the email format when the form is submitted.
-Regular Expression: It uses a regex pattern to check if the entered email matches a standard email format.
+Regular Expression: It uses a comprehensive email regex pattern to check if the entered email matches a standard email format.
+
+This pattern can handles:
+- Quoted local parts (`"john doe"@example.com`)
+- Dots within the local segment (`first.m.last@subdomain.org`)
+- IP-based domains (`user@[192.168.1.1]`)
+
 Error Message: If the email is invalid, an error message is displayed, and form submission is prevented.

Client-Side Components/Client Scripts/Validate Email Format/README.md

@@ -2,7 +2,8 @@
 
 function onSubmit() {
     var emailField = g_form.getValue('email');
-    var emailPattern = /^[^\s@]+@[^\s@]+\.[^\s@]+$/;
+    //Comprehensive email regex pattern
+    var emailPattern = /^(([^<>()\[\]\\.,;:\s@"]+(\.[^<>()\[\]\\.,;:\s@"]+)*)|(".+"))@((\[[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}])|(([a-zA-Z\-0-9]+\.)+[a-zA-Z]{2,}))$/;
 
     if (!emailPattern.test(emailField)) {
         g_form.addErrorMessage('Please enter a valid email address.');

Client-Side Components/Client Scripts/Validate Email Format/ValidateEmailFormat.js

@@ -0,0 +1,35 @@
+# Smart Field Validation and Dependent Field Derivation Using GlideElement.getError()
+
+This project demonstrates how to use `GlideElement.setError()` and `GlideElement.getError()` 
+to perform validation in one Business Rule and field derivation in another, without repeating logic.
+
+## 📘 Overview
+
+This snippet demonstrates how to share validation state and error messages between multiple Business Rules using `GlideElement.setError()` and `GlideElement.getError()` in ServiceNow.
+
+By propagating validation context across Business Rules, developers can:
+
+- Avoid repeated validation logic.  
+- Trigger dependent field updates only when a field passes validation.  
+- Maintain consistent and clean data flow between sequential rules.  
+
+This technique is especially useful when different validation or derivation rules are split by purpose or owned by different teams.
+
+---
+
+## 🧠 Concept
+
+When one Business Rule sets an error on a field using `setError()`, the error message persists in memory for that record during the same transaction.  
+A later Business Rule (executing at a higher order) can then retrieve that message using `getError()` and make data-driven decisions.
+
+### Flow:
+1. BR #1 (`Validate Short Description`) checks text length.
+2. BR #2 (`Derive Dependent Fields`) runs only if no validation error exists.
+3. Category, Subcategory, and Impact are derived dynamically.
+
+## 🚀 Benefits
+
+- ✅ Reduces redundant validation checks
+- ✅ Improves rule execution efficiency
+- ✅ Keeps logic modular and maintainable
+- ✅ Provides better visibility and control in field validations