Stages
Stages track progress through a Service Catalog request fulfillment process.
Definition
Section titled “Definition”stages: - label: Waiting for Approval value: waiting_for_approval steps: - approve_request always_show: true - label: Fulfillment value: fulfillment steps: - provision_access - notify_user - label: Completed value: completed steps: - close_taskFields
Section titled “Fields”| Field | Type | Required | Notes |
|---|---|---|---|
label | string | Yes | Display name in the Service Catalog portal. |
value | string | Yes | Internal value (must be unique). |
steps | list | No | Steps that belong to this stage (by id or order number). |
always_show | boolean | No | Show this stage even if not reached. |
Step References
Section titled “Step References”Steps in a stage can be referenced by:
- Step ID (string) — the
idfield on a step definition - Order number (integer) — 1-based position in the depth-first step tree
steps: - action: lookup_record id: check_approval - action: create_task id: provision_access - action: send_email id: notify_user
stages: - label: Approval value: approval steps: - check_approval # By ID (preferred) - label: Fulfillment value: fulfillment steps: - 2 # By order number - 3Step IDs are more stable than order numbers since they survive reordering.
Validation
Section titled “Validation”flowctl --validate checks:
- Each stage has a
labelandvalue - No duplicate
valuefields - Step references (by ID) point to valid top-level step IDs
- Step references (by number) are >= 1