Cancel running flow executions

[Its-Nmk]

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

[Its-Nmk]

Removed the duplication of the script from README file

[ravichandra1998g]

Hello @Its-Nmk

What happens if there are no flows associated with the record at all?

Can you please modify the script to handle that scenario and add a message indicating user there are no flow contexts associated with the record

[Its-Nmk]

Hello @Its-Nmk

What happens if there are no flows associated with the record at all?

Can you please modify the script to handle that scenario and add a message indicating user there are no flow contexts associated with the record

As it is checking for the execution, we wont be encountering to any issues even when there is no on going execution. GlideRecord while loop will return false and no flow API methods will be invoked.

We can restrict the visibility of the UI action, but I feel that will be out of scope for this, as developers may need to have different conditions according to their use case.

@ravichandra1998g

[ravichandra1998g]

Yes, having UI action visibility based on flow executions is better approach. even though that's outside the scope of this, Can you update the readme file about the same so that it'll be helpful to understand the functionality if anyone wants to explore the use case..

[Its-Nmk]

Agreed. I mentioned the same with one section as Visibility in the readme file. Its good point as it can be referenced from here and get more idea about other use cases as well.

Thanks for the suggestion. @ravichandra1998g

[ravichandra1998g]

looks good now