Default Risk conditions not working/How it works?

[Vivek13]

Hi Experts,

There are four default risk conditions:

1. Insufficient lead time

2. Critical service changed

3. Critical service affected

4. Default

When I tried to use the risk calculator, Insufficient lead time and Default conditions works perfectly for me but the Critical service changed and Critical service affected is not working for me.

The business service I have selected is 1- most critical but still while I click on calculate risk it takes the Default risk condition, while it should take the Critical service affected condition.

Also not sure when the Critical service changed condition applies.

Please help me with this.

Thanks.

[Maik Skoddow · Accepted solution]

Hi Vivek,

Since you did not provide a screenshot of your change request, I can only assume that you selected the mentioned service in the "Service" field. In that case the OOTB risk conditions won't work.

Risk Conditions (2) and (3) will only work if you reference the service in the "Configuration Item" field:

And as a second condition that your selected service has to be of class cmdb_ci_service and not one of the derived classes:

To my mind this is really crazy and I'm wondering why ServiceNow has not fixed that so far.

[Maik Skoddow]

Hi

Did my reply answer your question?

If so, please mark appropriate response as correct so that the question will appear as resolved for other users who may have a similar question in the future.

If not, please tell me what is still missing.

Kind regards
Maik

[Vivek13]

Hi,

Yes, Thanks for the help. I checked it and works as you said. Risk Conditions (2) and (3) is working only if we reference the service in the "Configuration Item" field.

Thanks