Understanding Rules

A rule contains conditional logic that the Orchestrator uses to evaluate conditions, such as true or false conditions that determine how the orchestration processes the incoming data. You can define a rule with a list of conditions or you can define a more complex rule using a custom Java class. For more information about using a custom Java class for rules, see Creating Custom Java for Orchestrations.

An orchestration rule functions similar to an EnterpriseOne query in that each rule has:

• A "Match Any" or "Match All" setting.

• One or more conditions defined, each being a binary operation on two values.

After creating a rule, you must use the Action column in the Orchestration design panel to determine the course of action for any orchestration steps that are dependent on the rule. See Completing an Orchestration for more information.