Add or modify risk and impact conditions

You can define risk calculation rules on which the risk and impact of a change are calculated. Change Management - Change Risk Calculator is activated by default in the base system.

Before you begin

Role required: itil_admin or admin

About this task

Risk Conditions are run against the change request based on their Order field from lowest to highest. The first Risk Condition that matches the change request record is applied. All subsequent risk conditions are then ignored whether they match or not. A risk calculation rule is defined with two elements.

• Conditions that can evaluate to true or false. You can use a condition builder or write a script.

• Risk and Impact field value settings when the conditions evaluate to true.

Procedure

1. Navigate to All > Change > Administration > Risk Conditions.

2. Select New, or select the risk condition to modify.

   To stop a base-system condition such as Insufficient lead time from applying, open the condition and clear the Active check box instead of deleting it so that you can re-enable it later.

   You can also edit risk conditions from within the Change Request form by opening the form context menu and clicking Edit Risk Conditions.

3. Complete or update the form, as appropriate.

<table id=“table_xym_4zl_wy”><thead><tr><th>

Field

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Name

</td><td>

Enter a descriptive name for the rule

</td></tr><tr><td>

RiskImpact

</td><td>

Select a value for one of these fields. The selection determines which field to update based on this risk calculation.

</td></tr><tr><td>

Active

</td><td>

Select the check box to use the rule.

</td></tr><tr><td>

Order

</td><td>

Enter the order in which this risk calculation is evaluated. Rules with lower numbers are evaluated first. If there are two or more rules with differing orders, the rule with the lowest order is evaluated and the others are ignored.

</td></tr><tr><td>

Use advanced condition

</td><td>

Select the check box to enter a script instead of using the condition builder.

</td></tr><tr><td>

Use script values

</td><td>

Select the check box to hide the Risk and Impact fields. The script specifies the risk and impact values.

</td></tr><tr><td>

Description

</td><td>

Enter a description of how this risk calculation is applied.

</td></tr></tbody> </table> Important: If the Calculated risk value doesn’t update, check the following:

-   The rule's **Active** check box is selected.
-   No rule with a lower **Order** value matched the change request first. The first matching rule wins, and the system ignores later rules.
-   If **Use script values** is selected, the script assigns both the **Risk** and **Impact** values.

1. Specify the rule based on your selected rule method.

<table id=“choicetable_zdq_xvm_lz”><thead><tr><th align=“left” id=“d232670e266”>

Choice

</th><th align=“left” id=“d232670e269”>

Action

</th></tr></thead><tbody><tr><td id=“d232670e275”>

Condition

</td><td>

Use the condition builder to add conditions. Do not use the Keywords field as a filter condition. Risk and impact values are not calculated for keywords. To achieve equivalent filtering, use the Use advanced condition option and write a script that performs the text comparison explicitly.Note: The Condition section is hidden if you selected Use advanced condition.

</td></tr><tr><td id=“d232670e295”>

Use advanced conditions

</td><td>

Write the script in the Advanced condition field using standard business rule syntax. The condition must set the global variable answer to true or false.

</td></tr><tr><td id=“d232670e313”>

Use script values

</td><td>

Write the script in the Script values field. Specify the Risk and Impact values in the script.The conditions are set using either the condition builder or an advanced condition script.

</td></tr></tbody> </table> In the following example, the Advanced condition script first determines whether the CI is a business service. If so, the script identifies whether the Business criticality value is 1 - most critical or 2 - somewhat critical. If it does, it sets the global variable answer to true.

\[Omitted image "risk-condition-rule.png"\] Alt text: Critical business service risk condition

When the **Advanced condition** script returns *true*, the script in the **Script values** field sets the change request **Impact** and **Risk** values based on the **Business criticality** value.

To set risk based on lead time per change type, create two conditions.

The example above applies to change processes configured to use change models. If you're using legacy change types, set the condition using the **Type** field instead of the **Model** field.

-   Build a condition where **Model** is `Normal` and the planned start date is fewer than seven days from now, then set **Risk** to **High**.
-   Build a condition where **Model** is `Standard` and the planned start date is fewer than three days from now, then set **Risk** to **Moderate**.

    Set the **Order** values so these conditions evaluate before broader rules. The first matching condition is applied.

Parent Topic:Risk conditions and calculation

Related topics

{Risk Calculator property}[]