Business Rules
1. Feature Introduction
When creating or editing record data, business rules can be added to standardize form data entry according to different business needs. When conditions are met, actions such as hiding, making fields read-only, mandatory, and displaying error prompts can be executed.
2. Feature Example
For example: In the recruitment process, if the job seeker fills out the form and the position applied for is "Other," the "Other Position" field is mandatory.
3. Configuration Entry
Entry 1: Worksheet name > Set Worksheet > Business Rules > Add Rule
Entry 2: Edit Form > Form Settings > Business Rules > Add Rule
4. Composition of a Rule
A business rule consists of one or a set of conditions, and one or a set of actions.
4.1 Conditions
You can set one or multiple combined conditions. Each condition consists of a field + relationship (includes/does not include; is empty/is not empty, etc.) + condition value.
4.2 Actions
When conditions are met, configure the following actions:
- Hide certain field(s)
- Make certain field(s) read-only
- Make certain field(s) mandatory
- Display an error prompt
5. Business Rule Processing Logic
When a field is set with a business rule, the processing logic when the rule conditions are met and not met is as follows:
| Business Rule | Condition Met | Condition Not Met |
|---|---|---|
| Hide | Hide | Show |
| Read-Only | Read-Only | Take Original Field Attribute |
| Mandatory | Mandatory | Take Original Field Attribute |
| Read-Only + Mandatory | Read-Only | Take Original Field Attribute |
Example Explanation:
- If the field's business rule is set to hide, and the rule condition is not met, then the field is displayed, regardless of whether the field's original attribute is hidden or displayed. This is because showing and hiding are absolutely mutually exclusive.
- If the field's business rule is set to read-only or mandatory, and the rule condition is not met, it depends on the field's original attribute, because read-only or mandatory does not have a unique opposing attribute. Therefore, if not met, it will take the field's original attribute.
6. Error Prompt Action
Processing logic: When a numeric field > x, display an error: xxx Example: When the purchase quantity is < 10, display an error: The purchase quantity must be more than 10 each time. When the name is duplicated, display an error: xxxx Example: When the employee name entered is duplicated, display an error: The name already exists, please check if it has been entered twice!
7. Field Hiding Situations
- Hidden field properties configured in form design
- Fields hidden in the view
- Fields hidden by business rules
- Fields hidden in public forms
- Fields not added in the related records
- Fields hidden in custom action buttons
8. Routine Management of Rules
- View or edit rules
- Delete rules, copy rules
- Enable or disable rules