Documentation Index
Fetch the complete documentation index at: https://docs.firstwork.com/llms.txt
Use this file to discover all available pages before exploring further.
Decision rules are the conditional logic attached to form pages. When a candidate submits a page, the platform evaluates rules and determines what happens next.
Building a Rule
A rule is a condition tree that evaluates to true or false. Admins build rules using a visual editor to express logic like “age is greater than 18 AND state is one of [CA, NY, TX].”
Condition Structure
Field conditions are the leaves of the tree. Each compares a data value against a target:
- Left side — a field from the current record (e.g., applicant’s age, document upload status, contract start date)
- Operator — how to compare (equals, not equals, greater than, less than, contains, is present, is absent, before/after for dates, regex match, and more)
- Right side — a static value (“18”, “CA”), another field for field-to-field comparisons, or a dynamic data path
Logical Operators
| Operator | Behavior |
|---|
| AND | All child conditions must be true |
| OR | At least one child condition must be true |
| NOT | Inverts the result of its child |
AI-Powered Evaluation
Rules optionally support AI-powered evaluation where the system uses an AI model to assess candidate data against the rule criteria.
Rule Categories
| Category | What It Does |
|---|
| Recollection | Flags specific documents or fields for re-submission if they don’t meet requirements |
| Assignment | Assigns tags, enrolls in courses, sends to manual review, fills form fields, or resets funnels |
| Navigation | Controls which page the candidate sees next — including approval, rejection, waiting list, or advancing to a specific stage |
Navigation Outcomes
| Outcome | Description |
|---|
| Next Page | Candidate proceeds normally to the next page |
| Manual Approval | Application is held for admin review |
| Waiting List | Candidate is placed on a waiting list |
| Rejection | Application is rejected |
| Create Offer | An offer or contract is generated |
| Move to Stage | Candidate is moved to a specific stage in the pipeline |
Rule Branching
Rules can have child rules on TRUE and FALSE branches, each with their own actions. This creates if/else decision trees:
- If score > 80, approve
- Else if score > 60, send for review
- Else reject
Logging
Every rule evaluation creates an execution record showing which conditions were checked, what values were compared, and whether each node passed or failed. Admins use these logs to debug why an applicant was routed to a particular page or why a field appeared or disappeared.
