Dynamic CI grouping for change management and Outage creation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2024 03:53 AM - edited 11-26-2024 04:00 AM
In our set up, when an Outage record is created from change ticket and Dynamic CI is selected, it doesn't have effect on all related CI's that are part of Dynamic CI group.
Is this Dynamic CI group functionality working as expected? ideally, we would expect it to show all related CI's of the Dynamic CI group having the outage record tagged. Can ServiceNow suggest something here
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-20-2024 12:27 PM - edited 01-03-2025 11:28 AM
Interested in a solution for this as well. In theory the unpacking of constituent CIs on an Outage record could work the same way it does on Change Request, even though they are different types of records (Outage does not extend task like Change Request does) and use different tables to record the relationship between them and the CIs they affect (the Affected CIs related list):
change_request > task_ci
cmdb_ci_outage > cmdb_outage_ci_mtom
Interestingly enough, the Affected CI unpacking doesn't seem to work on Change Tasks (change_task), which also use the Affected CIs as related list.
The change_request table has a couple of Business Rules that utilize functions in a Script Include called ChangeCollisionHelper and its addCiToChangeAffectedCis() function:
Add CI to Affected CIs
Add CI to Affected CIs on change
Skimming the Script Include I don't see the Dynamic CI Group table (cmdb_ci_query_based_service) being referenced anywhere, so the unpacking may be happening via different route, though I haven't had a chance to review thoroughly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2025 11:27 AM
I found out that the unpacking of Dynamic CI Group members into the Affected CIs list on Change Requests (task_ci table) happens via a Business Rule called "Sync Affected CI Dynamic Group," which references the TaskUtils Script Include (extends TaskUtilsSNC). The Script Include uses the following functions to unpack the CIs in a Dynamic CI Group or delete them: