Page tree
Skip to end of metadata
Go to start of metadata

Use the Branch Editor tool to specify conditions that must be met for the rule set to continue. Each condition consists of a property (such as Job Status), an operator (such as Is), and a value (such as Completed).

Check Any/All ... conditions are true

If you use more than one condition:

    • Select Any if you want a Yes result when one or more conditions are true.
    • Select All if you want a Yes result when every condition is true.

Create one or more conditions. Each condition consists of two or three parts:

    • The event property that you want to evaluate. For example, Job > Status.
    • The operator, such as Is or Is not.
    • The value that you want to evaluate, such as Completed status.
      Note: Some event properties do not need a value.

For example, when you create the condition Job > Status Is Completed, the condition is met if the Job Status attribute of the job is set to Completed.
If the property is a group of things, such as input files, the Any/All list appears for you to indicate whether every item in the group must meet the condition or just a single item in the group.


Add and delete rows—one row per condition.

Advanced: Convert to Code

Click this button to use the Microsoft Visual Basic programming language to assign parameters in Parameter Code Editor.
If you click Save in Parameter Code Editor, the next time that you edit the parameters for the event-action pair, Parameter Code Editor appears instead of Rule Parameters Editor. If you want to stop using code and use Rule Parameters Editor again, right-click the line between the event and action, and select Reset to Default.

See also

About writing custom code for RBA

  • No labels