Custom business rules

By default, the Turbonomic Actions app creates a corresponding Change Request (CR) in ServiceNow for each action approval. You can create custom business rules when the CR states differ from what the application expects or if you need to support complex workflows for creating and managing CRs.

Points to consider:

  • IBM Support does not debug or maintain the custom business rules that you created.

  • If you use a custom business rule to create matching CRs for action approvals, the ServiceNow administrator must close those CRs. They can be closed as successful or unsuccessful, based on the state of the action approvals SUCCEEDED or FAILED).

This following table lists the default change request states that are used by the Turbonomic Actions application.

Change request state Value
New -5
Assess -4
Authorize -3
Scheduled -2
Implement -1
Review 0
Close 3
Cancelled 4

To enable your custom business rules to create matching CRs for Turbonomic action approvals, you must enable the Use Custom Business Rule for CR Creation application setting.

Enabling custom business rules

Your custom business rules must implement the following logic steps:

  • Create a CR for every newly added action approval record in the PENDING_APPROVAL state. It must also link the CR to the action approval.

  • For every change request, update the state of its corresponding action approval based on the approval or rejection of the request. When the CR is canceled, the action approval state must be set to REJECTED. When the CR is approved, the action approval state must be set to APPROVED.

  • If a CR is approved but a future schedule is attached to it (Planned Start Date is in the future), the state of its corresponding action approval must be set to WAITING_FOR_CR_SCHEDULE. Later on, when the CR schedule is on, the rule must change the approval state to APPROVED.

  • After the Turbonomic action completes its execution and the approval state is set to SUCCEEDED or FAILED, the rule must close the corresponding CR as successful or unsuccessful. Similarly, the rule must close the CR as unsuccessful when the action approval moves to the MISSED state.

Note:

If your business rules do not implement these logic steps, Turbonomic might not run the specified actions.