Business Rule Examples

You can specify a read-only rule for the incident business object to not allow users to modify incident records after the status of the incident has been marked closed. In other words, you are setting up a final state for the incident, where users cannot update incidents after they have been marked closed.

The read-only business rule for incidents is not set up by default.

1.

From the Configuration Console, open a business object.

2.

Click the Business Rules tab on the toolbar. The Business Rules page appears.

3.

Under Read-only Rules, click Add Read-only Rule. The Add Read-only Rule window appears.

Add Read-only Rule Window

4.

From the Field Name drop-down list, select a field (for example, Status_Valid).

5.

Check This field is conditionally read only based on expression.

6.

In the Expression Editor, enter the following:

 

$(iif(((Status == "Closed"),

true,

false

Add Read-only Rule Window with Expression

7.

Click Save.

The read-only business rule does not apply to child objects, such as tasks.

A use case involving a business rule can involve linking an incident to a problem so that configuration items associated with the incident are also linked to the problem.

To facilitate this process, you must create a business rule in the problem object, triggered by the creation of a ProblemAssociatesIncident relationship with the incident object.

1.

From the Configuration Console, open the problem business object.

2.

Click the Business Rules tab on the toolbar. The Business Rules page appears.

3.

Under Triggered Actions, click Add Trigger. The Create Triggered Action window appears.

4.

Check On Creation of Specific Relationship.

5.

From the Relationship drop-down menu, select ProblemAssociatesIncident.

Create Triggered Action Window - ProblemAssociatesIncident

6.

Click Next.

7.

Enter a name and description for this triggered action.

8.

Check Configure new action and choose Search and Link from the New Action Type drop-down menu.

Create Triggered Action Window - New Action Type

9.

Click Next.

10.

Define the linking criteria.  From the Relationship drop-down menu, select CIAssociatesProblem.

11.

For the four where fields, enter CI in the first field, enter '[Incident#]RecID' in the second field, select Equal to from the drop-down menu in the third field, and in the fourth field enter ‘$([OtherObject]RecId)'. Because you are defining this rule for the problem object, to obtain the RecID of the incident, you must enter the [OtherObject] prefix.

Creating Business Rule Window - Linking Criteria

12.

Click Save.

As a result, upon the creation of the ProblemAssociatesIncident relationship, this quick action links configuration items to problem records using the CIAssociatesProblem relationship. The search condition of this quick action finds configuration items linked to an incident with a RecID equal to the RecID of the incident linked to this problem.