Trigger Business Rule on change of state on AVIT or VIT in Servicenow Vulnerability Response odule n
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi,
I have created a onChange BR on AVIT (sn_vul_app_vulnerable_item)table whenever there is a change on if state changes from closed to trigger so that each AVIt will have only one rem task in open state
But lets say when ever the assignment group on the avit i schnaged manually and saved. then avit is closed and reopened which means state is chnaged from closed - in this case my BR itself is not triggering
but if there is no change on asignment group on avit and state is changed from closed then the BR is triggerring.
Here in case after the assignment group is chnaged we are saving the form and then closing and reopening BR is not triggering. Please help me on what I can do here
thanks,
Harika.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi, can you check manually in the list view and confirm whether you have records for this condition.
Also can you confirm that you don't have any other condition added in the advanced section (Above the script)
Palani
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Case 1 – Only State Change (No Assignment Group Update)
If I don’t update the assignment group and if the state change is made, then it’s working.
Case 2 – Assignment Group Updated
If assignment group on VIT updated and saved, then as well it is checking
Case 3 – Assignment Group Updated
If assignment group on VIT updated and saved
VIT Closed → Reopened → Not Triggering (state is changed and is recorded)
“Next step if the VIT is closed and re-opened, then the BR is not calling.”
That means:
When the state changes from Closed → Open (or In Progress),
The BR does not execute.
VIT Closed → Reopened again → Works
“Again next closed and reopened then BR is calling.”
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
in that case can you check if there is any workflow where you run current.setWorkflow(false). This may conflict and will stop other BRs from executing
Palani
