Business rules are units of business logic that are stored as objects in System Setup. Business rules are used for many different purposes in STEP and come in three variants:
|
|
Input |
Output |
Side effects allowed |
|---|---|---|---|
|
Business actions |
Current object, current event batch, etc. provided by the context in which the action is executed. For more on business actions, refer to the Business Actions topic here. |
None |
Yes |
|
Business conditions |
Current object, current event, etc. provided by the context in which the condition is evaluated. For more on business conditions, refer to the Business Conditions topic here. |
Boolean result of evaluating the condition and a message for the user |
No |
|
Business functions |
Input parameters defined by the function and provided by the functionality evaluating the function. For more on business functions, refer to the Business Functions topic here. |
Result of evaluating the function |
No |
A fourth type of business rule, business library, allows users to define JavaScript library functions that can be called from other JavaScript-based business rules. For more information on business libraries, refer to Business Libraries topic documentation here.
For more information on differentiating between scenarios where one business rule is more useful than another, refer to the Business Rule Use Cases topic in the Business Rules documentation here.