Nuclos rule execution order: insert/update/delete/state change, final rules, subforms, object generation, user action, updateAfterExecution.

globe with meridians Language: Deutsch · English

open book Rule execution order

Which rule runs when? The order of API rules per action – create, edit, delete, clone, job, print.

On this page

Overview of the order in which the API rules assigned to a BO run, depending on the action.

Create

  1. StateChangeRule to the initial status (only with a status model)
  2. InsertRule (parent BO) → mandatory-field check
  3. InsertRule of subform BOs (only with own status model) → mandatory-field check
  4. StateChangeFinalRule (initial status)
  5. 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

ActionOrder
CloneGenerate → GenerateFinal → form → save → Insert → InsertFinal
User actionCustomRule → (UpdateRule → UpdateFinalRule)
Object generationGenerateRule → InsertRule → InsertFinalRule → GenerateFinalRule
PrintPrintRule → PrintFinalRule
JobJobRule
REST serviceCustomRestRule

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

open book Server-side rules

Rule kinds.

Open →

gear Server rule manager

Set the order.

Open →