Risk Condition or Business Rule script to calculate risk for manually added affected CIs using the business criticality field for manually added services..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2020 01:19 PM
One of the OOB risk conditions looks at the affected service business criticality to calculate risk on a change, but doesn't take into account manually added CIs. Can anyone help with a script to check all affected services, then using the business criticality field calculate risk using the highest value when CIs are manually added?
I'm looking for something similar to the below, accept I'd also like to take into account added CIs when calculating the risk.
OOB Risk Condition:
Thank you,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2020 01:05 AM
Hi MB,
The above OOB risk condition is checking the list of impacted services to see if any has the 'Business Criticality' attribute as '1 - Most Critical'. This attribute is on the business service table and not the base table so other CI classes will not have this field.
If you are wanting to check all CIs in the 'Affected CI list' what attribute are you wanting to check against in order to trigger the rule?
Essentially though you will need to get an array of the sys_ids of the CIs in the task_ci table. Then loop over the array and check each CI against the condition you want to check for to trigger the rule.
Hope this helps
Thanks
Sam
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-05-2020 04:06 PM
Hi Samogden,
Thanks for the reply! I'm not sure if I'm understanding the business service and CI relationships correctly. I believe if a CI is selected on the form, it will look at the relationship mapping to determine which business service is dependent on the selected CI. The business service table has a criticality field which would then be used for the risk calculation.
If a user opening a change manually adds additional CIs under the "affected ci" related list, I would want it to reference the parent business service's criticality field, then use that to calculate risk. The hope is that it would take the highest criticality value of all affected services to determine the risk (not just the primary service selected at the top of the form).
Ex. A change is opened, and the creator chooses the CI "exchange server." The parent business service "email" has a criticality of 2.
The user then adds an additional CI to the affected CIs related list "salesforce server," with the parent business service "sales ops" which has a criticality of 1. Can a risk condition compare and take the highest criticality value (which would be for the sales ops service in this case), then set risk to High based on that having a criticality value of 1?
Any help would be greatly appreciated.
Thank you,