Fixscripts/workflow nudger

[lauri457]

PR Description:

replace this with your description

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

[ravichandra1998g]

Hello @lauri457

Thank you for your contribution.

There are many community threads on advancing a hung workflow. Below is one of the examples.

https://www.servicenow.com/community/servicenow-ai-platform-forum/workflow-issue-a-workflow-is-struck-in-an-activity-and-doesnot/td-p/1093522/page/2

• At Hactoberfest, we are aiming for unique code snippet contributions that will be helpful for the open source.

• Since this use case is already available in various ServiceNow community threads, this PR will not be merged.
  You can expand the code snippet with additional use cases/examples.

Closing this for now. Once you make additional changes, feel free to re-open this Pull Request or create a new one.

[lauri457]

Hey @ravichandra1998g thanks, that's a valid point but wouldn't the presence of a similar snippet in the repo make more sense to be cause for rejection. Seeing as there is a recent merged PR that shows how to use glideajax this rule seems arbitrary