The scope of a business rule can be either local or global.
- Global business rules are reusable and can have multiple functions, for example, in different workflows, during object approval, and in imports and bulk updates. Global business rules are available when you open a business rule selector.
- Local business rules are specific to one process such as when a specific workflow enters a specific state. Local business rules are not available from a business rule selector. Global business rules can be added to a workflow and then copied for local use. Local business rules are typically located below the workflow where they are used.
Icons are used to differentiate between conditions and actions. A hand indicates the business rule is global.
|
Condition |
Action |
|
|---|---|---|
|
Global |
|
|
|
Local |
|
|
Local and global business actions can be executed when entering a workflow state (On Entry), when exiting a workflow state (On Exit), when a deadline is met and the Escalation background process is run, and when the workflow transitions from one state to another (On Transition).
Local and global conditions can be tested on transitions. A transition cannot take place if the associated business action evaluates to false.
For more information about local business rules, see the Business Rules and Workflows topic in the Workflows documentation here.