onStart Transform script to validate if the incoming file is empty or not (#1944)

* Create Code.js

* Create README.md

* Add Business rule: Add or remove tag to the ticket

* Rename code.js to code.js

* Rename README.md to README.md

* Adding new UI Action: Generate PDF

* Adding new UI Action: Generate PDF

* Adding new Background script: Bulk Update of Fulfillment Group References in Published KB Articles

* Adding new Background script: Bulk Update of Fulfillment Group References in Published KB Articles

* Delete Server-Side Components/Background Scripts/Bulk Update of Fulfillment Group References in Published KB Articles directory

* Update Script.js

* Update README.md

* Update README.md

* Delete Client-Side Components/UI Actions/Generate PDF directory

* Create script.js

* Create README.md

* Create script.js

* Create README.md

* Delete Server-Side Components/Script Includes/Calculate Due date using user defined schedules directory

* Create README.md

* Add files via upload

* Update script.js

* Update README.md

* Create README.md

* Update README.md

* Create ui_action_script.js

* Create ui_page.html

* Create ui_page_client_script.js

* Create ui_page_processing_script.js

* Update README.md

* Add files via upload

* Updated the table name ui_page_processing_script.js

* Create script.js

* Create README.md

* Update script.js

* Update README.md

* Update script.js

Author: sivamuruganandam-coder

Server-Side Components/Transform Map Scripts/Check if the Import file is valid/README.md

@@ -0,0 +1,18 @@
+**Example use Case:**
+
+Vendor data is periodically imported into ServiceNow via a scheduled data load (import set) sourced from an external application. These files contain only valid vendor records. After the import, any existing vendor records in ServiceNow that are not present in the latest file should be marked as inactive.
+
+**Risk:**
+
+If the incoming file is empty due to an issue in the source application, all existing vendor records in ServiceNow could be incorrectly marked as inactive, resulting in data loss or disruption.
+
+**Solution:**
+
+To prevent this, implement an "onStart" transform script that checks whether the import set contains any data before proceeding with the transformation. If it is found to be empty, the script should:
+
+1. Abort the transformation process.
+2. Automatically raise a ticket to the responsible team for investigation.(Optional)
+
+
+   
+This ensures that the existing vendor data in ServiceNow remains unchanged until the issue is resolved.

Server-Side Components/Transform Map Scripts/Check if the Import file is valid/script.js

@@ -0,0 +1,32 @@
+/*
+When : onStart
+Active : True
+*/
+
+(function runTransformScript(source, map, log, target /*undefined onStart*/ ) {
+
+    var table = import_set.table_name;
+    var run = new GlideAggregate(table);
+    run.addQuery("sys_import_set", import_set.sys_id);
+    run.addAggregate('COUNT');
+    run.query();
+    while (run.next()) {
+        var count = parseInt(run.getAggregate('COUNT'));
+        if (count < 1) { // Check the row count of the latest import job. If it's 0, then abort the transformation and raise a ticket (Optional)
+            ignore = true;
+            gs.error("File is empty. Hence aborting the transformation");
+
+			// Creating a ticket to the fulfillment team. This step is optional.
+            var incident = new GlideRecord('incident');
+            incident.initialize();
+            incident.short_description = "Import failed due to empty file";
+            incident.description = "The incoming file was empty. Please investigate.";
+            incident.assignment_group = gs.getProperty('Fallback queue'); // Store the resolver group sys id in the system property and use it here.
+            incident.impact = 3; // Modify as required
+            incident.urgency = 3; // Modify as required
+            incident.insert();
+
+        }
+    }
+
+})(source, map, log, target);