CR settings
The CR Settings guide how Turbonomic Actions creates a Change Request (CR).
To edit the settings, complete the following steps:
Click Settings in the Turbonomic Actions menu.
The Turbonomic Actions Settings view displays. This view includes the record that shows your current CR settings and other settings.
-
Click the field entry for Matching CR Type.
The settings record opens.
You can configure the following settings for Turbonomic Actions:
-
Matching CR Type: Specify the CR type to generate for Turbonomic Actions. The Change Management application includes three CR types, each with different behaviors. Use this field to choose which type you want to generate when you are using Turbonomic Actions.
Normal(Default)EmergencyStandard
For more information about CR types, see your ServiceNow documentation.
Note:You can edit your CRs in ServiceNow. In all cases, the CR that you use with Turbonomic Actions must include a
Scheduledstate. When Turbonomic Actions recognizes that the CR is in this state, it sends the action for Turbonomic to run. -
CR Close Code For Missed Approvals: Specify the
Close Codevalue to set when Change Requests forMISSEDaction approvals are closed.-
Successful -
Unsuccessful(default)
-
-
Populate CR Assignee: Enable this setting to define the CR users or groups to specify for each generated CR. Click the Lookup using list icon to search for valid user and group names.
-
Assigned CR User: Specify the user to assign the CR to.
-
Assigned CR Group: Specify the group to assign the CR to.
-
Use Custom Business Rules for CR Management: Select this option to use custom rules when Turbonomic Actions generates a CR. When you enable this setting, Turbonomic Actions does not create CRs. Your ServiceNow administrator must deploy a custom business rule that generates the CR.
The business rule is defined for the
x_turbo_turbonomic_turbonomic_action_approvaltable oninsert.Implement the rule to trigger for each
insertinto the approval table that Turbonomic Actions maintains. Disable theUpdateApprovalBasedOnRequestStateChangesbusiness rule and implement a similar rule to update the approval record when the CR is approved or rejected. - Allow Previously Rejected Actions and Allow Combined Actions : These settings do not affect CRs but determine whether previously rejected actions or combined actions are allowed in your Turbonomic Actions instance. For more information, see Allow Actions Settings.
-
Action Retention Time: For an action that is waiting to run, how long Turbonomic waits before it marks the action as
MISSED. This setting applies to an action in one of the following states:-
PENDING_APPROVAL -
APPROVED -
WAITING_FOR_CR_SCHEDULE -
WAITING_FOR_EXEC
The default setting is 86400 seconds (24 hours). By default, the action must be in one of the listed states for 24 hours before the Turbonomic Actions application marks it as
MISSED. -
-
CR State values
These settings are hidden by default but you can display them by adjusting the page layout. Set these fields if your ServiceNow administrator changes the default CR states for your environment. For more information about the default settings, see Custom business rules.
-
Approved CR State: This value corresponds to the
SCHEDULED CRstate. The default value is-2. If your environment uses a different value, specify it in this field. -
Canceled CR State: This value corresponds to the
CANCELED CRstate. The default value is4. If your environment uses a different value, specify it in this field. -
Implement CR State: This value corresponds to the
IMPLEMENT CRstate. The default value is-1. If your environment uses a different value, specify it in this field. -
Closed CR State: This value corresponds to the
CLOSED CRstate. The default value is3. If your environment uses a different value, specify it in this field.
-
-
Turbonomic Host Name: Specify the URL of the Turbonomic instance that discovered this ServiceNow target.
After you make your settings, click Update.