Business rule is a server-side script running at the moment of inserting, updating, or deleting a record. Business rules are used for such tasks as conditionally automatic value change in the form fields or event creation for email notifications and script actions.
Business rules can use scenarios to perform actions with records in the database. Even so, there are several other options of the script actions available, such as client-side scripts and UI-actions.
The scheme below illustrates when Before and After rules run. Both execute after an action record start (insert, update, or delete).
Before rules run condition:
- Before the system performs the server updates.
After rules run condition:
- After the system performs the server updates.
For more information about execution order for before and after business rules, please refer to the Execution order article.
Role required: admin.
Abort business rules
It is possible to perform business rules that terminate the follow-up actions and processes.
The abort business rules terminate the following processes: Business rules, Notifications, Approval Rules, etc.
See Approval Management to learn more about approval rule rejection.
To make your business rule abort the follow-up processes, complete the steps below:
- Open a business rule desired.
- On the form, select the Abort Action checkbox.
- Click Save or Save and Exit.
Business rules creation
You can create business rule that will be running when inserting, updating or deleting a record.
To create it, please perform the following steps:
- Navigate to System Definitions → Business Rules.
- Click New and fill in the fields.
- Click Save or Save and Exit to apply changes.
Business rules form fields
| Field | Mandatory | Description | ||||
|---|---|---|---|---|---|---|
| Name | Y | Name a business rule. | ||||
| Table | Y | A table on which a business rule will be performing. | ||||
| Description | N | A brief action description. | ||||
| Set Value | N | Select a column of the table chosen in the Table field and define the needed value. | ||||
| Abort Action | N | Select this checkbox to interrupt the transaction (update, insert, or delete) when all conditions are met. | ||||
| Active | N | Select this checkbox to make the business rule active. | ||||
| Inheritance | N | Select this checkbox to apply this business rule to all child tables of the table defined in the Table field. | ||||
| Advanced | N | Select this checkbox to display the Script field. | ||||
| When to Run tab | ||||||
| When | N | Defines the moment of a business rule execution:
This field is available when the Advanced is selected. | ||||
| Order | N | Defines the order of the business rule execution. If there are several business rules, they will perform in the ascending order. This field is available when the Advanced is selected. | ||||
| Priority | N | Defines the importance of the business rule. This field is available when the Advanced is selected. | ||||
| Action Insert | N | Select this checkbox to execute the business rule when inserting a new record. | ||||
| Action Update | N | Select this checkbox tp execute the business rule when updating a record. | ||||
| Action Delete | N | Select this checkbox to execute the business rule when deleting a record. This field is available when the Advanced is selected. | ||||
| Filter Conditions | N | A condition builder that allows using static and dynamic filters. After specifying a table in the Table field, all fields of this table will be available in the constructor. Use dynamic filter conditions like is (dynamic) or is not (dynamic) when composing conditional expressions to make your business rules more versatile. | ||||
| Action tab | ||||||
| Add Message | N | Select this checkbox to display the Message text field if you want to show a message to a user when a business rule is performed. | ||||
| Message | N | Enter the message text you want to show to a user when a business rule is performed. | ||||
| Advanced tab | ||||||
| Script | N | The action sequence that will be executed when a business rule is launched, previous and current variables are available:
You can call REM attributes in your business rule of before type, In this case, while your business-rule is processed, you will get the current attribute values, before the transaction occurs. | ||||
