The Custom Rules Engine in FieldEx lets planners control how Requisition and Consignment requests are approved based on item details, values, locations, and user roles. This article explains:
What the Custom Rules Engine does for approval workflows
Where to configure approval rules for consignment and requisition
How to create rules with conditions, approvers, and notifications
What Is the Custom Rules Engine for Approvals?
The Custom Rules Engine automates the routing of requisition and consignment requests to the right approvers in FieldEx. Rules can be based on request value, item category, bin/zone ownership, requester role, or operational context.
By defining conditions and mapping them to Level 1 and Level 2 approvers, planners can ensure that high-value or sensitive requests receive proper oversight, while low-risk items can be auto-approved with a full audit trail.
Sequential or any-order approvals
Auto-approval thresholds for low-risk cases
Escalation SLAs for overdue approvals
Bin/Zone-based approver assignment
Why this matters: The Rules Engine ensures custody control, prevents unauthorised movements, and saves time by automating straightforward approvals. |
Where to Configure Approval Rules
Use the Automation & Workflows section to create and manage approval rules.
Path: Setup > Automation & Workflows > Approval Rules
Configuration | Purpose |
User Groups | Define groups for requesters, Level 1 approvers, and Level 2 approvers. |
Zone Managing Groups | Assign managing groups to Zones—these members approve or reject requests for bins in that Zone. |
Approval Rules | Specify conditions, approver routing, order, auto-approval, and notifications. |
How to Create an Approval Rule
Follow these steps to set up a new rule:
Create Rule – Name it clearly, e.g., “High-Value Inter-Zone Transfer > £500”.
Select Scope – Choose Requisitions, Consignments, or Both.
Define Triggers – When the rule should run (e.g., On Submit).
Add Conditions – Item category, value, bin/zone, requester group, or urgency.
Set Approvers – Choose Level 1 and optional Level 2 groups (must be different).
Approval Order – Sequential (L1 then L2) or Any order.
Auto-Approval – Optional for low-risk, low-value requests.
Notifications – Select recipients for each stage of the process.
Escalation SLA – Notify higher groups if time limit exceeded.
Activate – Test with simulation before switching to Active.
Tip: Use simulation mode to preview how a request will route before activating a new rule. |
Example Conditions and Routing
Low-value consumables to van bins – Auto-approve if value ≤ £100 and category = Consumables.
High-value cross-zone transfers – Sequential L1 = From Zone Managing Group, L2 = Regional Mgmt.
Critical asset to remote site – Requires both L1 and L2 approvals regardless of value.
Urgent job requisitions – L1 only if under value threshold; escalate if not approved in 4 hours.
What Happens at Runtime
When a requisition or consignment is submitted, the system:
Matches the request against all active rules.
Routes it to the required approver(s) in the correct order.
Allows approvers to approve or reject with notes.
Enables the approver to initiate the transfer upon approval.
Notifies the destination managing group to accept or reject the transfer.
Note: Only users in the configured approval or managing groups can approve or accept transfers. |