Save complete records and resolve conflicts
Employee edits send the full set of editable request fields with the current record version. Optional blank values and explicit No values matter. A stale version is refused rather than merged automatically.
Editing workflow
- Open the exact record; Edit / close fetches current server values.
- Review every populated field, not only the one being changed.
- Preserve intended optional values and explicit Yes/No/None selections.
- Save once and wait for the result.
- Reopen/reload to verify the saved state.
Conflict example
Farah and Nadia open the same assignment. Farah saves a corrected cost centre first. Nadia's later save with the old version is refused. Her dialog keeps the unsaved form but does not fetch a new version and resubmit it automatically.
Nadia should privately note the intended change, cancel, reopen the latest assignment, compare Farah's saved correction and reapply only the approved remaining change. Do not manually increment a version or treat repeated Save clicks as reconciliation.
Blank and boolean values
| Value | Meaning |
|---|---|
| Blank optional text/date | Submitted as null and can clear the old value |
| No | Explicit false; valid for required boolean fields |
| None | Null for optional choices; distinct from No |
| Omitted/full form misunderstood as a patch | Risk of losing intended values; use complete current form |
Employment selection must finish loading before saving dependent forms. If lookup loading fails, resolve it; do not choose another employment just to enable Save.
Lost responses and multi-record changes
The Employee UI does not implement Charity's stored original-intent replay. After an uncertain create response, inspect the existing records before repeating. A new master can be especially difficult to find until first employment establishes scope; arrange support resolution rather than creating another.
Transfers, pay changes and departures involve separate requests. Earlier saves can succeed even if a later one fails. Reload each affected record and complete the approved remaining work. An editor error is not evidence that all previous changes rolled back.