Merge branch 'ServiceNowDevProgram:main' into Check-Attchment

Author: Nisha-admin

Client-Side Components/Client Scripts/Abort action when description is empty/Code.js

@@ -0,0 +1,12 @@
+function onSubmit() {
+    //Type appropriate comment here, and begin script below
+    var description = g_form.getValue('description');
+	var state = g_form.getValue('state');
+
+    if ((!description) && (state == 'completed')) {
+        g_form.addErrorMessage('Please provide Description Value, Description Cannot be empty');
+
+        return false;
+    }
+
+}

Client-Side Components/Client Scripts/Abort action when description is empty/ReadMe.md

@@ -0,0 +1,2 @@
+When an Incident record is being closed, the system should validate that the Description field is not empty and state is completed.
+If the Description field is blank and state is completed, the record submission (update) should be aborted, and the user should be prompted to provide a description before closing the incident.

Client-Side Components/Client Scripts/Form Dirty State Prevention/README.md

@@ -0,0 +1,109 @@
+# Form Dirty State Prevention
+
+## Overview
+Detects form changes and warns users before navigating away or closing the form, preventing accidental data loss.
+
+## What It Does
+- Tracks form field changes (dirty state)
+- Warns user before leaving unsaved form
+- Allows user to cancel navigation
+- Works with all form fields
+- Prevents accidental data loss
+- Clean, reusable pattern
+
+## Use Cases
+- Complex multi-field forms
+- Long data entry forms
+- Forms with expensive operations
+- Critical data entry (financial, medical)
+- Any form where accidental exit would cause issues
+
+## Files
+- `form_dirty_state_manager.js` - Client Script to manage form state
+
+## How to Use
+
+### Step 1: Create Client Script
+1. Go to **System Definition > Scripts** (any table)
+2. Create new Client Script
+3. Set **Type** to "onChange"
+4. Copy code from `form_dirty_state_manager.js`
+5. Set to run on any field
+
+### Step 2: Add Navigation Handler
+1. Add to form's onLoad script:
+```javascript
+// Initialize dirty state tracking
+var formStateManager = new FormDirtyStateManager();
+```
+
+### Step 3: Test
+1. Open form and make changes
+2. Try to navigate away without saving
+3. User sees warning dialog
+4. User can choose to stay or leave
+
+## Example Usage
+```javascript
+// Automatically tracks all field changes
+// When user tries to close/navigate:
+// "You have unsaved changes. Do you want to leave?"
+// - Leave (discard changes)
+// - Stay (return to form)
+```
+
+## Key Features
+- ✅ Detects any field change
+- ✅ Persistent across form interactions
+- ✅ Works with new records and updates
+- ✅ Ignores read-only fields
+- ✅ Resets after save
+- ✅ No performance impact
+
+## Output Examples
+```
+User opens form and changes a field
+→ Form marked as "dirty"
+
+User clicks close/back button
+→ Warning dialog appears: "You have unsaved changes"
+
+User clicks Leave
+→ Form closes, changes discarded
+
+User clicks Save then navigates
+→ No warning (form is clean)
+```
+
+## Customization
+```javascript
+// Customize warning message
+var warningMessage = "Warning: You have unsaved changes!";
+
+// Add specific field tracking
+g_form.addOnFieldChange('priority', myCustomHandler);
+
+// Reset dirty flag after save
+g_form.save(); // Automatically triggers cleanup
+```
+
+## Requirements
+- ServiceNow instance
+- Client Script access
+- Any table form
+
+## Browser Support
+- Chrome, Firefox, Safari, Edge (all modern browsers)
+- Works with ServiceNow classic and modern UI
+
+## Related APIs
+- [g_form API](https://docs.servicenow.com/bundle/sandiego-application-development/page/app-store/dev_apps/concept/c_FormAPI.html)
+- [Client Script Events](https://docs.servicenow.com/bundle/sandiego-application-development/page/app-store/dev_apps/concept/c_ClientScriptEvents.html)
+- [Form Field Changes](https://docs.servicenow.com/bundle/sandiego-application-development/page/app-store/dev_apps/concept/c_FieldChanges.html)
+
+## Best Practices
+- Apply to important data entry forms
+- Test with real users
+- Consider accessibility for screen readers
+- Use with save shortcuts (Ctrl+S)
+- Combine with auto-save patterns

Client-Side Components/Client Scripts/Form Dirty State Prevention/form_dirty_state_manager.js

@@ -0,0 +1,60 @@
+// Client Script: Form Dirty State Manager
+// Purpose: Track form changes and warn user before leaving with unsaved changes
+
+var FormDirtyStateManager = Class.create();
+FormDirtyStateManager.prototype = {
+    initialize: function() {
+        this.isDirty = false;
+        this.setupFieldChangeListeners();
+        this.setupNavigationWarning();
+    },
+    
+    // Mark form as changed when any field is modified
+    setupFieldChangeListeners: function() {
+        var self = this;
+        g_form.addOnFieldChange('*', function(control, oldValue, newValue, isLoading) {
+            // Ignore system updates and form loads
+            if (isLoading || oldValue === newValue) {
+                return;
+            }
+            self.setDirty(true);
+        });
+    },
+    
+    // Warn user before navigating away with unsaved changes
+    setupNavigationWarning: function() {
+        var self = this;
+        
+        // Warn on form close attempt
+        window.addEventListener('beforeunload', function(e) {
+            if (self.isDirty && !g_form.isNewRecord()) {
+                e.preventDefault();
+                e.returnValue = 'You have unsaved changes. Do you want to leave?';
+                return e.returnValue;
+            }
+        });
+        
+        // Warn on GlideForm navigation
+        g_form.addOnSave(function() {
+            // Reset dirty flag after successful save
+            self.setDirty(false);
+            return true;
+        });
+    },
+    
+    setDirty: function(isDirty) {
+        this.isDirty = isDirty;
+        if (isDirty) {
+            // Optional: Show visual indicator
+            document.title = '* ' + document.title.replace(/^\* /, '');
+            gs.info('[Form State] Unsaved changes detected');
+        }
+    },
+    
+    isDirtyState: function() {
+        return this.isDirty;
+    }
+};
+
+// Initialize on form load
+var formDirtyState = new FormDirtyStateManager();

Client-Side Components/UI Actions/Add Loggedin user as Incident assigned to/ReadMe.md

@@ -0,0 +1,2 @@
+>**UI Action**
+When a new Incident record is created, user can come to incident ticket and assigned to themself. Once they click on UI Action.

Client-Side Components/UI Actions/Add Loggedin user as Incident assigned to/code.js

@@ -0,0 +1,12 @@
+var currentUser = gs.getUserID(); //Getting loggedIn User Id
+
+//Checing wheather user is available or not in Assignee field
+if(current.assigned_to == ""){ //checking assigned to is there or not
+	current.assigned_to = currentUser; //Setting the current loggedIn user
+	current.update(); //updating the record.
+	gs.addInfoMessage("Incident has been assigned to You.");
+	action.setRedirectURL(current);
+} else {
+	gs.addErrorMessage("Incident is already assigned");
+	action.setRedirectURL(current);
+}

Client-Side Components/UI Actions/Generate QR for Assets/ReadMe.md

@@ -0,0 +1,50 @@
+# 🧩 ServiceNow Asset QR Code Generator (UI Action)
+
+This repository contains a **ServiceNow UI Action** script that generates and displays a QR Code for an Asset record from list view.  
+When the user selects a record and clicks the UI Action, a modal window pops up showing a dynamically generated QR Code that links to asset details.
+
+
+A supporting **Script Include** (server-side) is required in your ServiceNow instance but **is not included** in this repository.
+At the bottom of file , a sample Script Include Code is given , check for the reference.
+
+---
+
+## 🚀 Features
+
+- Generates a QR Code for the selected Asset record.
+- Displays the QR Code inside a ServiceNow modal (`GlideModal`).
+- Uses **QrIckit API** for quick and free QR code generation.
+- Clean, modular client-side code that integrates seamlessly with UI Actions.
+- Includes a `qr-code-image` file showing example QR Code generated.
+
+---
+
+## 🧠 How It Works
+
+1. The `onClickQR()` function is triggered when the user clicks a UI Action button.
+2. It calls `generateQRCodeForAsset(sys_id)` and passes the record’s `sys_id`.
+3. A `GlideAjax` request fetches asset data from a **Script Include** on the server.
+4. That data is encoded and sent to the **QrIckit** API to generate a QR Code image.
+5. A ServiceNow modal (`GlideModal`) displays the generated QR Code to the user.
+
+---
+
+
+**Note :**
+1) As the UI action calls a Script Include , in this folder no script include is present
+2) You can modify script include part as required(i.e Which fields are to be shown when QR is scanned)
+3) A sample Client Callable Script-Include is given here.
+
+``` Script Include Code
+     var GenerateAssetQR = Class.create();
+GenerateAssetQR.prototype = Object.extendsObject(AbstractAjaxProcessor, {
+    getAssetQRData: function() {
+        var sys_id = this.getParameter('sysparm_sys_id');
+        var asset = new GlideRecord('alm_asset');
+        if (asset.get(sys_id)) {
+            return 'Asset: ' + asset.name + ', Serial: ' + asset.serial_number;
+        }
+        return 'Invalid asset record.';
+    }
+});
+```

Client-Side Components/UI Actions/Generate QR for Assets/qr-code-image.png

@@ -0,0 +1,26 @@
+function onClickQR() {
+    generateQRCodeForAsset(g_sysId);//get the sysid of selected record
+}
+
+function generateQRCodeForAsset(sys_id) {
+    var ga = new GlideAjax('GenerateAssetQR');//Script Include which stores data to be presented when QR-Code is Scanned
+    ga.addParam('sysparm_name', 'getAssetQRData');
+    ga.addParam('sysparm_sys_id', sys_id);
+
+    ga.getXMLAnswer(function(response) {
+        var qrData = response;
+        var qrURL = 'https://qrickit.com/api/qr.php?d=' + encodeURIComponent(qrData) + '&addtext=Get Asset Data';
+         //QrIckit is a tool using which Customized QR-Codes can be generated
+        var modalHTML = `
+            <div style="text-align:center">
+                <img id="qrCodeImage" src="${qrURL}" alt="QR Code" style="margin-bottom:10px;" />
+                <p>Scan to view asset details</p>
+            </div>
+        `;
+
+        var gModal = new GlideModal("QR Code");
+        gModal.setTitle('Asset QR Code');
+        gModal.setWidth(500);
+        gModal.renderWithContent(modalHTML);
+    });
+}

Client-Side Components/UI Actions/Generate QR for Assets/ui-action-script.js

@@ -0,0 +1,47 @@
+**Calculate the due date based on the Priority**
+
+Script Type: UI Action, Table: incident, Form button: True, Show update: True, Condition: (current.due_date == '' && current.priority != '5'), OnClick: functionName()
+
+Script Type: Script Include, Glide AJAX enabled: False
+
+Schedule- Name: Holidays, Time Zone: GMT
+
+Schedule Entry - Name:  New Year's Day, Type: Exclude, Show as: Busy, When: 31-12-2024, To: 01-01-2025
+Schedule Entry - Name:  Christmas Day, Type: Exclude, Show as: Busy, When: 24-12-2025, To: 25-12-2025
+Schedule Entry - Name:  Thanksgiving Day, Type: Exclude, Show as: Busy, When: 26-11-2025, To: 27-11-2025
+Schedule Entry - Name:  Diwali, Type: Exclude, Show as: Busy, When: 19-10-2025, To: 20-10-2025
+
+**Goal:** To Calculate Due-Date based on Priority with some conditions.
+
+**Walk through of code:** So in this use case the UI Action is been used and then Script Include for server calculate is used.So the main to calculate the due-date by the user trigger.
+
+UI Action- So this button will check the priority and check the due date field is empty or not if not then will fetch the value of "Priority" and "Created date" and pass the data to the Script Include for calculation once it gets the response will populate the value to the due_date field in the incident table and then update it.
+
+Script Include- The role of this is to get the "Priority" and "Created date" based on prioriy this will calculate the time and date by using th GlidDateTime API and the will do some additional changes based on each priorit which is mentioned below and then return the response back to the UI Action,
+
+Schedule & Schedule Entry- It is used for the P3 and P4 Priority which is mentioned below for the use case.To exclude the Holidays.
+
+These are the use case which the above functionality works,
+
+**1-> P1** - add 4hrs to the Created date
+**2-> P2 **- add 4hrs to the Created date but if it's exceed the working hrs of of 5 PM the add to the next day or if the is before the working hours of 8 AM set 5 PM to the same Created date.
+**3-> P3 or P4** - Kind of low priority so add the due date to the next day but it should exclude the holidays and the weekend's and the populate the next business working day.
+**4-> P5 **- User manually will populate the due date based on the process.
+
+The UI Action on the Incident Form
+<img width="815" height="382" alt="Button" src="https://github.com/user-attachments/assets/68876b10-e6e0-43b9-9ecf-f6eb95b7ef87" />
+
+UI Action which will call the Script Include
+<img width="556" height="425" alt="UI Action" src="https://github.com/user-attachments/assets/2715232a-000b-4520-8b1a-f5bf72afdaa9" />
+
+Script Include
+<img width="817" height="416" alt="SI" src="https://github.com/user-attachments/assets/5ddb332c-d23f-4746-b014-1a71acb59186" />
+
+Schedules and Schedule Entry
+<img width="839" height="431" alt="Schedules" src="https://github.com/user-attachments/assets/f96ea4dc-e2d4-4d8f-87b7-67df66a2d8af" />
+<img width="917" height="370" alt="Schedule Entry" src="https://github.com/user-attachments/assets/c4fec5ce-8ee4-46cc-8673-2d22a27290f1" />
+
+Output
+<img width="828" height="356" alt="Priority 1" src="https://github.com/user-attachments/assets/7f4049b6-294e-4064-bab1-e2d1ab938bfd" />
+<img width="817" height="416" alt="Priority 2" src="https://github.com/user-attachments/assets/37f0cffd-f05c-4f4d-bf35-36090f02ee3b" />
+<img width="815" height="334" alt="Priority 4" src="https://github.com/user-attachments/assets/0ab4ab27-4726-4ea7-b99e-7e35f9b0f4c7" />