Update related tasks when parent changes

[DhruvBhatheja]

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

[ravichandra1998g]

Hello @DhruvBhatheja
Thank you for submitting!

as a reminder, Please adhere to contributing guidelines. CONTRIBUTING.md
Expanded Snippets: Code snippets reused from the ServiceNow Documentation or API References are acceptable only if they are expanded in a meaningful way (e.g., with additional context, documentation, or variations).
Quality Over Quantity: Low-effort pull requests will be marked accordingly.
Remember: “QUANTITY IS FUN, QUALITY IS KEY.”

[DhruvBhatheja]

Hi @ravichandra1998g is this PR is acceptable?

[DhruvBhatheja]

Hi @ravichandra1998g as I am new in this so what I explored and used in my projects these types of usecases only I have known if you have any idea what are usecases you were expected kindly tell so accordingly I will do.

[ravichandra1998g]

For Hacktoberfest, we’re aiming for high-quality contributions providing real-world use developer cases.

You can check some of the recently merged code snippets for reference. They are good examples of what we're aiming for.

As this is your first, we are merging it.
For upcoming one's, please continue to focus on the quality enhancements