A Business Rule is a predefined set of logical conditions and actions that determines how an application behaves in response to specific events or data inputs. It automates decision-making, ensuring consistency and eliminating manual effort in repetitive processes.
Example: If a user selects “Urgent” in a request form → Automatically assign the request to a senior approver.
A rule is built using two main components:
Condition: Defines the scenario that triggers the rule.
Example: “When a task’s status changes to ‘Completed’.”
Action: Specifies what should happen when the condition is met.
Example: “Send a notification to the manager.”
Use Case: Automate the school admission process — only students scoring 70% or above in their previous academic record can proceed.
Business Rules operate on logical conditions that tell the system what to check and what action to perform when that check passes or fails.
The IF, ELSE IF, and ELSE statements form the logical structure that defines how these checks are evaluated.
The IF statement sets the primary condition that the system evaluates first.
Example:
IF Leave Type = "Privileged Leave"
→ Action: Send to Manager 1 for approval.
Meaning: When the employee selects “Privileged Leave,” the rule triggers Manager 1’s approval flow.
The ELSE IF statement defines an alternative condition to check when the original IF condition is not true.
Example:
IF Leave Type = "Privileged Leave"
→ Send to Manager 1.
ELSE IF Leave Type = "Complimentary Leave"
→ Send to Manager 2.
Meaning: If the first condition fails (not Privileged Leave), the system checks the second one.
The ELSE statement acts as the default fallback condition — it executes only when none of the prior conditions are met.
Example:
IF Leave Type = "Privileged Leave"
→ Send to Manager 1.
ELSE IF Leave Type = "Complimentary Leave"
→ Send to Manager 2.
ELSE
→ Send to HR Department.
Meaning: If the leave type doesn’t match either condition, the system defaults to routing the request to HR.
Note
- IF defines the first condition.
- ELSE IF checks additional, alternative conditions.
- ELSE ensures a defined outcome even when no prior conditions are met.
This structure ensures no request goes unprocessed, maintaining logical flow and decision coverage in every workflow.
| Level | Description |
|---|---|
| Section Level | Applies actions to entire form sections. |
| Element Level | Targets individual form elements. |
| Grid Level | Controls grid-based data fields. |
| Level | Supported Actions |
|---|---|
| Section | Show Section, Hide Section |
| Element | Show, Hide, Enable, Disable, Set Value, Set Field Value, Set Operational Value |
| Grid | Show, Hide, Enable, Disable, Set Value, Set Field Value, Set Operational Value |
Natural Language Processing (NLP) lets users define rule conditions using everyday language instead of technical expressions.
For example: “If student score is greater than 70, show Particulars section.”
The platform interprets and converts this statement into a valid logical condition.
Note
- If the NLP-generated condition doesn’t reflect your intent, you can manually adjust it in the condition editor.
- Using business rules, you can now define values dynamically for Link fields, allowing real-time hyperlinks that replace static URLs.