Appearance
workflow-definition schema
A real multi-stage approval workflow (engine-workflow) — stagesJson/tasksJson/transitionsJson (each itself a JSON-encoded string) + a top-level approvalPermissions array.
Pull the full JSON Schema: erp schema pull workflow-definition · MCP: erp_get_schema {"name":"workflow-definition"}
Top-level properties
| Property | Type | Required | Notes |
|---|---|---|---|
name | string | yes | Unique per tenant; a domain module's REST layer starts instances by this exact name, e.g. "employee.transfer". |
description | string | ||
stagesJson | string | yes | |
tasksJson | string | yes | |
transitionsJson | string | yes | |
approversJson | string | ||
slasJson | string | ||
escalationsJson | string | ||
notificationsJson | string | ||
metadataJson | string | ||
approvalPermissions | array | Which role (by its stable role.code, never a mutable display name) may decide which named approvalObject task. |