Edit a record: inline editing, status rules and save conflicts
Edit a cell right in the table, or open the record and edit its fields. Corteksa applies the status transition rules, and protects you from overwriting a teammate’s edit made before yours.
Before you start · for managers and agentsThe edit permission on the unit and on this record
- You need: The edit permission on the unit and on this record
Steps
Status transition rules
A unit’s owner can set which stages a record can move to from each stage. The rule applies on the record page, when you drag a Kanban card, and in bulk edits.
If a move is refused, you see a message that names the allowed next stages.
A stage with no rule is open in every direction.
Save conflicts
If a teammate edited the same record after you opened it, Corteksa may refuse your save with the message “The record has changed since it was read”. Nothing is written, and the current values show. Reload and make your edit again.
Changing the assignee while editing
If you change the assignee and don’t have the assign permission, the other fields are saved and a notice says the assignee didn’t change.
If something goes wrong
A real example
Some employees moved contracts from “Quote” straight to “Completed” without a signature.
- The owner set the status rules: “Quote” can only move to “Signed” or “Rejected”.
- “Completed” became available only after “Signed”.
Nobody can skip the signing stage anymore, not on the record page and not by dragging the card.