Adds Feature: Ignore Update Sets Action#133
Adds Feature: Ignore Update Sets Action#133JorgeGRC wants to merge 3 commits intoServiceNowDevProgram:mainfrom
Conversation
|
✅ Valid PR for ActionPack Thank you for your contribution. This PR complies with the CONTRIBUTING.md. |
|
Thanks for your submission. It appears that this pull request contains more files than described in the title. Please review and update the pull request to either remove the extra/unintended files or to update the description to be more comprehensive. Ensure your contributions are meaningful and adhere to the project’s standards. [If applicable: You can create a new branch on your forked repository to avoid accidental inclusions of new commits in the future.]. Closing this for now. Once you make additional changes, feel free to re-open this Pull Request or create a new one. In your case, i see 2 flow designer action files. One file isn't required for this pull request. |
|
Weird - it appears to be mixed with another PR I had open. I'll fix it and resubmit. Thanks for taking the time to look into it! |
|
Submitted it (hopefully) clean now on #136 |
New feature to automate part of admins / devs offboarding. The Action will set to 'ignored' any 'in progress' Update Sets that a specific user still has in the instance.
sys_update_setrecords. This should be done manually by whoever tries to use this Action, because adding sensitive Cross Scope privileges in people's instances is not considered safe.The idea is to be able to better automate offboarding tasks via Flow Designer. The Action receives a sys_user reference and searches for 'in progress' Update Sets that the person might still have on the instance. It will mark them as 'Ignored' to clean-up.