Updated CI - how can we automatically get the assignment rules for a VIT to update to reflect the change?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-02-2022 07:16 PM
Hello
First, I'd like confirmation that my assumption about VIT assignment rules is correct - by default they only execute when a VIT is first created?
Second, if that is true, is there a job/business we can configure to re-run the assigment rules based upon a CI's approval/assignment groups being modified?
Has anyone solved this problem?
- Labels:
-
Vulnerability Response

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-05-2022 07:05 AM
Hi,
I think that you need to run a Business Rule here:
- Detect if the CI groups have changed
- Determine if the CI has an open VI(s)
- Flag that VI(s)
I am pretty sure you would need a Business Rule to Detect the Change.
Maybe an on after or the newer async
https://community.servicenow.com/community?id=community_question&sys_id=ec0516e5db1ff89880073ca8f49619fb
I like to keep the Business Rule processing time down to a minimum.
Then a Scheduled Job to then Reassign the VI's
- Run a scheduled job on those flagged VI(s)
- Reassign
- Clear the flag
OR
Run a BR just to determine if the group changed and flag the CI (if your CMDB team will allow this)
- Detect if the CI groups have changed
- Flag the CI
Then run a Scheduled Job on the Flagged CIs
- Determine if the CI has an open VI(s)
- Reassign those open VI(s)
- Set the flag to false on the CI
It is a best practice to keep your BR to the shortest run time possible... especially on the CMDB.
VR tends to lean towards the larger record sets. So a CI may have 10 VIT associated. If you have 10 CI that Change you need to process 100 records. If you have 100 CI changes you need to process 1000 records. If you have 1000 CI Change you need to process 10000 records.