Correlatives and auto-fill
Advanced numbering sequences and relative date defaults in Form Builder fields.
Audience: Admin
Correlatives assign sequential document numbers (work orders, ticket IDs). Auto-fill pre-populates fields with formulas, relative dates, or context from the visit—reducing typing on mobile.
Correlative numbering
Correlatives generate monotonic identifiers per form or per scope (team, place, global).
| Concept | Description |
|---|---|
| Prefix | Static text (WO-, INSP-2026-) |
| Counter | Incrementing integer, often zero-padded (000142) |
| Scope | Reset yearly, per team, or never reset |
| Read-only | Field user cannot edit; value assigned on first save |
Typical uses: maintenance work orders, inspection serials, delivery receipts.
Best practices
- Decide reset policy before go-live (calendar year vs. never).
- Do not reuse a correlative field for a different document type mid-stream.
- Export sample numbers to finance if they must align with ERP sequences—ERP may remain system of record while Chekku generates field-facing IDs.
Relative date auto-fill
Date fields can default relative to visit start, submission time, or fixed offset:
| Pattern | Example |
|---|---|
| Today | Service date = visit day |
| Today + N days | Follow-up due in 7 days |
| Start of month | Billing period anchor |
Auto-fill runs when the form opens or on first save—exact timing depends on field configuration. Users can override unless the field is read-only.
Context auto-fill from visit
Some fields pull from visit context without user input:
- Place name or external place code
- Assigned user display name
- Visit type label
- GPS coordinates (read-only snapshot)
Reduces mismatches between visit header and form answers.
Formulas linking fields
Formula fields combine other answers (quantity * unit_price). Correlative and auto-fill fields can feed formulas if keys are stable—see Field keys and API.
Order matters: source fields should appear above dependent fields in the form layout.
Interaction with Workflows
Correlative values are available in form_submitted payloads—use them as task titles or external reference numbers. Prefer Workflows over copying numbers manually in notifications (Automations on form submit).
Tips
- Pilot correlatives with one team to validate padding and reset before global rollout.
- Document whether mobile users may edit auto-filled dates—audits often require read-only service dates.
- Test offline: correlative assignment should not duplicate when two devices sync late (Chekku resolves server-side; still verify on pilot).
- For ERP-owned numbering, store ERP ID in a separate text field populated by integration, not the correlative field.