Risk conditions not setting the Impact field correctly in Change Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-13-2023 03:55 AM
Hello folks - We're having some issues with our Risk Conditions in Change Mgt. More specifically, we can't seem to get them to set the Impact field as expected. We have 6 scripted Risk conditions in place, which traverse the Affected CI, Impacted Services, and Impacted Business Applications M2M tables to identify how many of these records are impacted, are any of the subject to compliance audits, etc. We're setting only the Impact field, not the Risk field (we're using assessments for Risk).
Our first rule checks to see if there are more than 5 Affected Business Services for the CHG Request. If so, it sets the Impact to Critical. If not, it should move to the next rule (more than 20 non-service CI's affected), and on down the line.
However, every time we run the 'Calculate Risk' option, the Impact is set to Critical, even though the conditions aren't being met, and we get the following message:
If I click on the 'View Details' link I get the following:
When I click on the information icon it reads 'Five or more Affected Services', which leads me to believe it ran the script in that Risk Condition, evaluated to false (because it was not set), and then stopped there and the Impact to Critical anyway. The expectation is that it would evaluate each Risk Condition until it found one where the script returned TRUE, and then set the Impact accordingly. It seems like it's stopping after the first rule for some reason. Anybody else ever seen this before? Thanks in advance!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-05-2023 06:51 AM
Sure that you must have figured the answer but I think since the risk field is a Boolean type field, the line answer = true or false can't be of the type 'String' meaning in it can't be set to values inside quotes like 'true' or 'false'.
Also, the first line when it says answer = false, it immediately jumps onto the next risk condition before evaluating the whole script, you might want to take that off.