A value worked out from others
The customer asks: A field filled in from other fields when the record is saved
- Verdict: Ready, with limits (2)
- Door: Save rules · area: Documents and print › Numbering and checks on save
- Recipe: Save rules
- Sample: none yet
- Checked: carried 2026-10-16 · not re-run
What you build
A save rule of kind derived, held on every save.
Limits
- On a till sale and the till close a save rule only flags, never refuses.
- POS LANE X row X59, P-RULES4, adds days between two dates to the derived rule, and to the limit rule a value judged when it changes, a row rule that reads its header and a limit read from a settings record, when it merges.
Tell the customer
The field is worked out from the others each time the record is saved.
What next
- Tell the customer the 2 limits above, and write them into the proposal.
- Start from: Save rules.
- Build and test it on your sandbox (request one if you have none; what is on it).
- Run the checks: your own tests, the kit's checks and the money kit's release gate (testing and release).
- Release through the customer's own release gate (14. Testing and release); an app other shops install goes through the App library.
Related needs
- A code must follow our pattern — Ready, with limits (1)
- A field must be filled when another field holds a value — Ready, with limits (1)
- Fields cannot be changed once the document is approved — Ready, with limits (1)
- The same item or code may not appear twice in one document — Ready, with limits (1)
Start a project shortlist with this need · Put it in your blueprint · Every need