onStart Transform script to validate if the incoming file is empty or not

[sivamuruganandam-coder]

PR Description:

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.

Pull Request Checklist

Overview

• Put an x inside of the square brackets to check each item.
• I have read and understood the CONTRIBUTING.md guidelines
• My pull request has a descriptive title that accurately reflects the changes and the description has been filled in above.
• I've included only files relevant to the changes described in the PR title and description
• I've created a new branch in my forked repository for this contribution

Code Quality

• My code is relevant to ServiceNow developers
• My code snippets expand meaningfully on official ServiceNow documentation (if applicable)
• I've disclosed use of ES2021 features (if applicable)
• I've tested my code snippets in a ServiceNow environment (where possible)

Repository Structure Compliance

• I've placed my code snippet(s) in one of the required top-level categories:
  • Core ServiceNow APIs/
  • Server-Side Components/
  • Client-Side Components/
  • Modern Development/
  • Integration/
  • Specialized Areas/
• I've used appropriate sub-categories within the top-level categories
• Each code snippet has its own folder with a descriptive name

Documentation

• I've included a README.md file for each code snippet
• The README.md includes:
  • Description of the code snippet functionality
  • Usage instructions or examples
  • Any prerequisites or dependencies
  • (Optional) Screenshots or diagrams if helpful

Restrictions

• My PR does not include XML exports of ServiceNow records
• My PR does not contain sensitive information (passwords, API keys, tokens)
• My PR does not include changes that fall outside the described scope

[WillemZeiler]

Thank you for your contribution. Simple, jet useful script! However, the description of the PR does not match the script and readme fully. In the description you mention this solution (after detecting an empty import set) creates a ticket to be picked up. It would be great if you can add (an example) task creation in the code. Alternatively, adjust the description and clearly state that this is not included. In the code you can still add comment as placeholder where you think others should add it. This will help in better understanding and reviewing your contribution effectively. Closing this for now. Once you make additional changes, feel free to re-open this Pull Request or create a new one.