- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2024 12:53 AM - edited 12-08-2024 03:48 AM
When there are issues and needs troubleshooting, I can use 'Debug business rules' or 'Script tracer' feature and see which Business rule is causing the issue.
Had I used flows, I need to review all the active flows and makes it difficult to troubleshoot and takes more time.
So I prefer Business rules over Flows keeping easier troubleshooting in mind.
What is your opinion? Is there any easier way to troubleshoot Flows (like how we can use 'Debug business rules' or 'script tracer' ?)
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2024 01:00 AM
Why do you need to review all active flows? Something happens at x time, so you can just check on the flow executions of that time where the record that is having the issue is the source. The execution record tells you exactly what happened when (depending on the level of reporting the flow is on).
Also, picking one over the other because of troubleshooting may not be the best reason to prefer one.
Flows are easy to read and maintain by any one. You just see what is being done, while some people have more trouble in exactly understanding what a (scripted) BR is doing.
But also see your other question related to the same topic: https://www.servicenow.com/community/developer-forum/on-after-business-rule-vs-flows-which-is-prefer...
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-08-2024 03:49 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2024 01:00 AM
Why do you need to review all active flows? Something happens at x time, so you can just check on the flow executions of that time where the record that is having the issue is the source. The execution record tells you exactly what happened when (depending on the level of reporting the flow is on).
Also, picking one over the other because of troubleshooting may not be the best reason to prefer one.
Flows are easy to read and maintain by any one. You just see what is being done, while some people have more trouble in exactly understanding what a (scripted) BR is doing.
But also see your other question related to the same topic: https://www.servicenow.com/community/developer-forum/on-after-business-rule-vs-flows-which-is-prefer...
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-08-2024 03:49 AM
I was confused with something, its clear now. Thanks Mark 🙂