Prevent closure parent incident when child incident is open

[naveensnow]

PR Description:

Pull Request Checklist

Overview

• I have read and understood the CONTRIBUTING.md guidelines
• My pull request has a descriptive title that accurately reflects the changes
• 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. I have added some comments to your code.
Closing this for now. Once you make additional changes, feel free to re-open this Pull Request or create a new one.

[WillemZeiler]

Consider using a GlideAggregate, it is more efficient (getting the aggregate instead of full records) and getting the count of child incidents is enough to allow or prevent the closure of the parent.

[WillemZeiler]

Just my preference have them count up so 6, 7, 8, and add what 6, 7, 8 are (closed, resolved, canceled (like in line 6 of your code))