Add a Run Action rule

This rule automatically runs actions (defined by rule sets and/or backend transitions) on records that have a specified relationship to the record that triggers the rule. For example, you can use this rule to change the workflow phase of related records under specific conditions.

To add a Run Action rule, follow these steps:

1. In the System Navigator, click Tailoring > Process Designer > Rule Sets.

2. Click Search to open the Rule Set form, and then select the rule set to which you want to add the rule.

   Note You can edit user-defined rule sets only. Out-of-box rule sets are labeled as Micro Focus Proprietary and cannot be modified.

3. Click Add Rule to open the Select Rule Type page, and then click Run Action.
4. Type a description in the Rule Description field.

5. Click Edit to add conditions to the rule.

   Note If you do not specify a condition, the value defaults to Always.

6. Select the type of record on which you want to run the action.

   • Select Related Records to change the workflow status of records related to the record that triggers the rule.

   • Select Other Records to change the workflow status of records that have a relationship with the current record that is built by a manually-defined query string.

   • Select Current Record to change the workflow status of the record that triggers the rule.

     Note This option enables you to run a backend transition directly on the current record.

7. Configure the relationship between the records on which you want to run the action and the record that triggers the rule.

   • If you selected the Related Records option, select a relationship type from the Relation Type drop-down list.

   • If you selected the Other Records option, select a table from the Table Name drop-down list.

   • If you selected the Current Record option, there is no need to define a relationship.

8. Click Edit Query if you want to define a subset of the related records on which the actions will be run.

   Note  

   • If you select the Other records option but do not specify a query, no records are queried. This prevents the rule from running the action on every record in the defined table.
   • This step does not apply if you selected to run the actions on the current record only.
   • The Query Editor widget functions similarly to the Condition Editor. However, note the following differences:
     • In the left-hand side (LHS) of the query, you can only select a field in the record on which you want to run the action. Cross table fields are not supported.
     • Only the following data types are supported on the right-hand side of the query:
       • Blank/Nul
       • Value
       • Variable
       • Current Record
       • Saved Record
9. In the Run Rule Set field, select the rule set that is applied to the target records when this rule is triggered.
10. In the Action after Rule Set field, select the action that is performed on the target records after the rule set is applied. You can select to do nothing, save the record, or apply a backend transition. The list of available backend transitions is retrieved from the workflows of the target record's table name (depending on the Relation Type that you selected).

11. Click OK to add the new rule to the rule set.

Related topics

Process Designer
Process Designer security model
Adding a rule
Create a rule set