Business Rules

A business rule is an action run on the server-side when a record is inserted, updated or deleted. Business rules are executed in a database transaction, irrespective of the interface used to initiate the transaction (user submitting a form, execution of a server-side script, REST request, execution of a Workflow Activity block). The action of a rule can be executed both on the current record and on other records.

Business rules are used for:

• changing values in the fields of a record that caused the rule to run when certain conditions are met;
• executing a server-side script of the rule;
• displaying a message to the client side;
• creating system events for sending e-mail notifications or running other server-side scripts;
• aborting transactions with the database.

To view all business rules navigate to System Definition → Business Rules.

To view the business rules related to a table, complete the steps below:

1. Navigate to the list or form view of the table;
2. Select Configure → Business Rules from the burger menu.

Business rules types

Depending on the business task to be completed, you can use one of the following types of business rules:

• before;
• after;
• async after.

Each type of business rules has its own run conditions.

Before rules run conditions:

• After record action start (insert, update, or delete).
• Before the system performs server updates (before the database transaction is completed).

After rules run conditions:

• After the system performs server updates (after the database transaction is completed).

Async after rules run conditions:

• After all business rules of other types (after all after business rules).

The scheme below illustrates when before, after  and async after  rules run. All rules execute after a record action start (insert, update, or delete).

Process starts with a form action: if it is the update action, data source is the database, and therefore the record has the previous block. The p revious block represents the form state before an action (form submission – insert, update or delete), and the current blocks represent the form state after the action is completed. Form submission can be performed by a user, script or REST API request.

Business rules creation

To create a new business rule, perform the steps below:

1. Navigate to System Definition → Business Rules.
2. Click New and fill in the fields.
3. Click Save or Save and Exit to apply changes.

Business rules form fields

Abort business rules 

It is possible to perform business rules that terminate the follow-up actions and processes.

To make your business rule abort the follow-up processes, complete the steps below:

1. Open a business rule record you need.
2. In the When to Run tab, define the abort conditions.
3. In the Action tab, select the Abort Action checkbox.

4. In the When to Run tab, check that the When field is set to before.

5. Click Save or Save and Exit to apply the changes.

Out-of-the-box business rules override 

If necessary, some "out-of-the-box" business rules can be overridden.

• For applications other than Simple it is enough to copy an "out-of-the-box" rule using the Make a copy action and deactivate the original rule. You can define the required logic in the copy of the rule.
• For the Simple application, most rules are delivered with Protection Policy = Protected, so you can not deactivate them. However, the rules of the When=before type can be overridden by rules of a higher order with the same start conditions. For example, an "out-of-the-box" rule with the before type generates a value in a field. The order of the rule is 999. To change the value generation logic, it is enough to make a copy of the rule using the Make a copy action, define a specific logic and set Order = 1000. If the value in the field should remain unchanged, use the rule triggered by an Action Update event with the following script:

(function executeRule(current, previous = null /*not null only when action is update*/) {
  if (previous) {
    current.getValue('field_name') = previous.getValue('field_name');
  }
})(current, previous);