Develop > Process Designer Tailoring Best Practices > Best practices for configuring rule sets > Perform automatic operations with Run Action rules > Configure Run Action rules on the current record

Configure Run Action rules on the current record

You can configure the Run Action rules to enable Service Manager to perform automatic operations on the current record. Usually this rule type can be used to easily expose a back end transition call as an action. To expose a back end transition configured in a workflow, you can use JavaScript or RAD calls as well. However, that approach is not quite user-friendly. By using the Run Action rules, you can easily expose the back end transitions. For details about calling back end transitions, see the Workflow back end transitions section in Configure a workflow.

For example, in the out-of-box incident workflow, there is a back end transition “close.any.time” that can move the incident to the Closure phase whatever current phase is. The back end transition is shown as follows:

To be able to invoke the transition, you need to first add a rule set that contains the Run Action rule, and then mark this rule set as Available as action, as shown below:

In addition, you also need to configure the Run Action rules in rule set as follows:

  • Select Current Record for the "Run Action on" field
  • Keep the "Run Rule Set" field empty
  • Select Backend Transition:close.any.time for the "Action after Rule Set" field. The save action is executed against the current incident record.
Note: You can select Do nothing, Save, or one of the back end transitions.
  • The back end transition list is retrieved from all the workflows of the selected record file. Similar to Configure Run Action rules on related records, at run time, if some of the other records do not have your selected back end transition, the corresponding transition is not run.
  • You are suggested to use the same back end transition name in different workflows if these back end transitions follow the same business logic.
  • While a back end transition is selected from the list, the interface is updated to indicate to which workflows the transition applies and to which it does not apply.

The form on which you can perform these tasks is shown below:

Upon completing all the above configurations, you can expose the rule set as an action by adding it to the workflow level actions:

 

Note: Only expose such actions to specific persons or operations. For example, you can expose it to the person who has the Expert permission on the Incident area by setting the security level with the Action Condition. If you want to make it available only to a Web Service call, set your Action Condition accordingly.