Skip to content

Adds a new instance check to notify about the possible risk associated with the usage of setWorkflow(false) method in business rule #119

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Oct 5, 2024

Conversation

aswamy93
Copy link
Contributor

@aswamy93 aswamy93 commented Oct 4, 2024

As setWorkflow(false) method will stop the execution of business rules on that particular GlideRecord object, this will result in unexpected behaviour where the execution of business rules skipped. Maintain caution while using this method and perform regression testing to avoid possible risk. It can have noticeable impact on Audit, Journal fields, notifications, SLA engine, workflow, flow engine etc.,

…d with the usage of setWorkflow(false) method in business rule
@niamccash niamccash self-assigned this Oct 4, 2024
@niamccash
Copy link
Contributor

hi @aswamy93 Thank you for your contribution. Looks good. Could you please update the readme file to include a description of your newly added check so that other people contributing know that it's there and don't duplicate?

@aswamy93
Copy link
Contributor Author

aswamy93 commented Oct 4, 2024

hi @aswamy93 Thank you for your contribution. Looks good. Could you please update the readme file to include a description of your newly added check so that other people contributing know that it's there and don't duplicate?

Hi @niamccash
Many thanks for the review,. I have update the readme file and created another pull request: #120. Please check it when you get a chance

@niamccash
Copy link
Contributor

hi @aswamy93
Can you please add the readme changes to this same PR? I think you should be able to go into your new_addition branch and update the readme file in that same branch to update this PR.

@aswamy93
Copy link
Contributor Author

aswamy93 commented Oct 4, 2024

hi @aswamy93 Can you please add the readme changes to this same PR? I think you should be able to go into your new_addition branch and update the readme file in that same branch to update this PR.

Hi @niamccash , There is no option to merge pull requests. Though I switched to new_addition brand updated readme but looks like I created another pull request. Sorry for the multiple pull requests for the same one.

@niamccash
Copy link
Contributor

How are you editing the readme file - in the browser or on your local computer? Can you try to go to https://github.com/aswamy93/example-instancescan-checks/tree/new_addition and edit the readme file there and commit?

It looks like you weren't working in the new_addition branch for your new PR. It was a new branch altogether.

Updated description of the instance scan definition
@aswamy93
Copy link
Contributor Author

aswamy93 commented Oct 5, 2024

How are you editing the readme file - in the browser or on your local computer? Can you try to go to https://github.com/aswamy93/example-instancescan-checks/tree/new_addition and edit the readme file there and commit?

It looks like you weren't working in the new_addition branch for your new PR. It was a new branch altogether.

Hi @niamccash , Sorry, my bad. I followed your steps and committed the changes without creating pull requests. Now, I can see that the readme file is captured in this pull requests. Thank you so much for your help

@SapphicFire
Copy link
Contributor

Addressed checksum conflict - will leave ownership of PR review and merge with Nia :)

@niamccash
Copy link
Contributor

Thanks for the help @SapphicFire!

@niamccash niamccash merged commit 68d9116 into ServiceNowDevProgram:master Oct 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants