Language: Deutsch · English
Rule execution order
Which rule runs when? The order of API rules per action – create, edit, delete, clone, job, print.
REFERENZ DEVELOPER UPDATED: JUL 2026 APPLIES TO NUCLOS 4.2026.X
On this page
Purpose
Overview of the order in which the API rules assigned to a BO run, depending on the action.
Create
- StateChangeRule to the initial status (only with a status model)
- InsertRule (parent BO) → mandatory-field check
- InsertRule of subform BOs (only with own status model) → mandatory-field check
- StateChangeFinalRule (initial status)
- InsertFinalRule of subform BOs, then of the parent BO
Edit
UpdateRule (main BO) → mandatory checks main/subform → UpdateFinalRule (main BO).
Delete
Subform records are deleted along with the parent (from Nuclos 4.38 only with delete cascade on the reference attribute); DeleteRules run for subform BOs only with their own status model.
Other actions
| Action | Order |
|---|---|
| Clone | Generate → GenerateFinal → form → save → Insert → InsertFinal |
| User action | CustomRule → (UpdateRule → UpdateFinalRule) |
| Object generation | GenerateRule → InsertRule → InsertFinalRule → GenerateFinalRule |
| PrintRule → PrintFinalRule | |
| Job | JobRule |
| REST service | CustomRestRule |
User action & save()
For user actions, context.setUpdateAfterExecution(...) controls whether a save follows. To perform status changes or save() calls from the CustomRule, the value must be false.
Related pages
Überblick
Inhalte