Optional technical reference. This material is for developers, integration specialists and platform administrators. For the consultant lesson, read the practical guide.
Preserved from source baseline
d4587c7c0e073e58c2d430342f65ac55dd701bf4; source/static examples retain their stated scope. They are not new runtime verification or required consultant setup steps.
Current model-key correction — 8 November 2026. The preserved examples below contain historical camelCase record-type/field keys. Do not copy those keys into the current editor or API: use record type leave_request and the lowercase field keys in the current model worksheet, including request_id, employee_id, manager_id, start_date, end_date, requested_days and decision_comment. Form, rule and case input names are separate declarations; map them explicitly rather than mechanically renaming every input. The preserved body remains historical source material, not a current executable model payload.
Build a vacation workflow and complete its manager task
This tutorial connects the data, form, lifecycle and human-task pieces of a Leave requests application. It teaches the handoffs, not a fictional built-in leave package or a complete importable application. All people and records are synthetic. The author has not executed this tutorial against a live product/provider environment; its steps and contracts were checked against current source.
Start with identity milestones1–4, the leave data/rules tutorial and only the preparation/publication milestones of the App Shell/interface tutorial, including its explicit manager decision-form construction. Stop before its task-host and ordinary-user milestones, which need the workflow produced here. Complete this tutorial's authoring/publication/Debug milestones1–4, then shell milestones8–9 to configure the published start action and native task host. Review/apply the complete application contributions in identity milestone6 before returning to this tutorial's normal-user milestones5–8. Finish shell milestone10 and identity milestone7 for the ordinary-user matrix. Use actual returned IDs and versions, not names copied into URLs.
| Story element | Shared value | Actual identity to record |
|---|---|---|
| Workspace | people-ops |
Resolved admitted workspace ID/key |
| People | Mohammad employee, Sara manager, Nadia builder/operator | Real selected directory accounts and their current scoped capabilities |
| Data | Model leave, record type leaveRequest, business reference leave-2026-014 |
Model/publication/record handles returned by the data flow |
| Dates/duration | 2026-12-14 through 2026-12-18, requestedDays 5 |
Typed Date and numeric values, not a claim of a built-in workday calculation |
| Business status | PENDING, later explicitly updated to APPROVED or DECLINED |
Record field maintained by an authored admitted business action |
| Lifecycle position | Working state review, then terminal approved/declined |
Actual immutable release, parent/child execution IDs and stable state IDs |
| Engine status | Such as RUNNING or SUSPENDED |
Runtime state; there is no separate WAITING instance enum |
A data row with statusPENDING is not itself an engine case. A case in Review can be RUNNING while its human task waits. App Shell page bindings use their actual screenKey/latest-published-page contract; task forms and workflow/rule references retain their own captured or explicit version semantics. Do not apply one universal “everything is pinned” rule.
Prepare only owned, admitted test resources. Existing runtime/data/provider/private/native/CI/PR3228 holds remain; the instructions do not authorize creating or changing a shared environment.
Milestone 1 — Carry the data outputs and actor choices into a case worksheet
Scenario and inputs. The data tutorial has produced the leaveRequest record and actual model/publication/record references. Its employeeId/managerId are Text business identifiers. Nadia has the supported lifecycle authoring capability, while Mohammad and Sara have only the published application/task rights intended for their roles.
Procedure. Record the actual workspace, directory selections and source record handle. Declare the lifecycle case file deliberately: requestId as Text, startDate/endDate as Date, requestedDays as Number, selected employee/manager User values where needed, and the approved/comment outputs. Map record fields through admitted authoring controls; do not cast an arbitrary record string into actor authority. Inspect required-at-start/default settings and the actual published eligibility rule selection supplied by the data tutorial.
Expected result. The worksheet distinguishes typed business data, authenticated identity and resource references. The5 days are an agreed synthetic input, not a hidden platform calendar computation or a newly granted manager right.
Failure and recovery. If the account/resource cannot be selected, fix the actual prerequisite with its owner. Never use root/development headers as ordinary Mohammad/Sara evidence, guess a model/publication ID or assume creating the row has already started a workflow.
Sources. ProcessLifecycleController.java:81; LifecycleModel.java:46.
Milestone 2 — Author one working Review state and explicit terminal outcomes
Scenario and inputs. The saved leave lifecycle uses a workspace-unique key such as leave-request. Nadia has a real published decision form available from the interface tutorial. The form’s actual submit actions and allowed output fields are known.
Procedure. Create initial Review and terminal Approved/Declined states. In Review’s Open flow, author a human task with explicit manager assignment and the actual captured form key/version. Declare the state’s allowed case-file outputs and its completion outcomes. Connect each outcome to the intended terminal state. If a record must change status, author that separate admitted rule/record action and its binding; case progression alone is not automatic record mutation. Save before Verify.
Expected result. There is real business work in an owned flow and a traceable path from the chosen form action to declared outputs and lifecycle outcome. A terminal marker without work can finish automatically; an empty whole application scaffold does not qualify as the required working flow.
Failure and recovery. Open each validation issue at its actual state/node coordinate. Correct missing flow, unmatched outcome, missing form publication or incompatible variable mapping instead of importing raw process XML to bypass lifecycle authoring.
Sources. ProcessLifecycleController.java:651; LifecycleState.java:20.
Milestone 3 — Review and publish one saved revision
Scenario and inputs. The actual saved draft and revision are available, and Nadia has the current update/publish rights. No other editor’s unsaved assumptions are part of the release. Required business acknowledgement remains a conscious decision.
Procedure. Read validation and then the saved revision’s compatibility assessment. Inspect parent/state changes, actual permitted impact projection and requiresAcknowledgement. Publish the exact assessed revision with releaseNotes and explicit acknowledgement only where reviewed. Native original-attempt clients retain the issued release intent and execute/observe that original command; direct legacy API callers use their documented route. Read the immutable release and retain the parent version and each state-flow pin.
Expected result. The release is a consistent parent/child publication. It identifies the actual source revision and captured child definitions. Existing running cases do not silently switch to the new release simply because publication succeeded.
Failure and recovery. A missing expectedRevision is refused and a stale one conflicts. Reload/reconcile/reassess rather than copying a newer revision into an old body or setting breaking-change consent automatically. UNKNOWN observation after a lost reply is not permission to issue another publication intent.
Sources. ProcessLifecycleController.java:440; ProcessLifecycleController.java:953; LifecycleAttemptObservation.java:4.
Milestone 4 — Test the captured Review flow in Debug
Scenario and inputs. A saved draft revision or explicit published release can be captured, and Nadia has the actual authoring/debug permission. If participant simulation is needed, its separate capability and captured Screen access are present.
Procedure. Choose DRAFT with lifecycleDraftId/expectedRevision or PUBLISHED with definitionKey/version. Select the actual Review entry and state-qualified node breakpoint. Start the isolated session, inspect its lifecycleContext, then Step/Continue to the waiting task. Read eligible participants, choose only an admitted one, fill the captured form and inspect the transcript/resulting child frame. Keep source release version separate from private debug execution coordinates.
Expected result. The author can inspect the captured flow and its declared result without creating an ordinary customer case or granting herself Sara’s production task rights. A later release or canvas selection does not rewrite or restart the existing session.
Failure and recovery. A stale setup requires a new valid capture. Missing/denied participant/form access remains a real refusal. On a lost Step response, read current session/transcript rather than repeating Step. A successful debug scenario is not ordinary-user runtime/video acceptance.
Sources. ProcessDebugSessionController.java:45; ProcessDebugSessionController.java:238; ProcessDebugSessionController.java:269.
Milestone 5 — Let Mohammad start the published request once
Scenario and inputs. Mohammad signs into the published application through an approved normal session. The actual app/action admission allows this lifecycle start. The form supplies the intended dates,5 requested days, business reference and any other required values from the published input contract.
Procedure. Use the published interface’s real startLifecycle action and its native confirmation/reconciliation flow. Inspect the published input contract, preserve the original action/start intent or idempotency context supplied by that implementation, and retain the accepted actual case identity. Treat the separate source row and engine case as distinct objects. Use the returned/observed case rather than constructing its ID from leave-2026-014.
Expected result. One accepted parent case starts with its explicit published source and initial working flow. Best-effort enrichment of a current lifecycle-state field is not the only acceptance witness for the original start; accepted birth and current inspection are separate evidence.
Failure and recovery. A definite required-input refusal is corrected before a new admitted attempt. A lost/uncertain start response is observed/reconciled through the original native intent, not assumed failed and repeated. Do not use authoring visibility or a generic record-create operation as a substitute for runtime start authority.
Sources. LiveForm.tsx:11469; ProcessLifecycleController.java:252; ProcessLifecycleController.java:456.
Milestone 6 — Let Sara claim and save only the permitted task form
Scenario and inputs. The actual Review task is assigned/offered to Sara under the published rule. Sara signs in normally and can view its captured form. The task’s ID, form key/version and draft revision come from current authorized responses.
Procedure. Open the task through the published task experience or admitted Live action. Claim only when the candidate policy offers it. Read the pinned form and /api/tasks/{taskId}/form-draft. With no saved draft, the initial save uses the actual absence/null revision; later saves use the last returned revision. Retain a stable clientMutationId for one unchanged save intention. Fill only fields the captured form allows; retain protected fields only through the native supported contract.
Expected result. Sara’s draft is attributed to her authenticated identity and its current task/form state. It survives a reload without overwriting another device’s newer draft or disclosing values that her task preparation withheld.
Failure and recovery. A409requires reread/reconciliation. Reusing a mutation ID with different values is an idempotency conflict, not a shortcut. If completion won the save race, inspect the task/receipt instead of reopening it. A read-only task view does not grant draft saving.
Sources. TaskController.java:145; TaskController.java:384; TaskServiceImpl.java:1584.
Milestone 7 — Submit the authored decision and read what happened next
Scenario and inputs. Sara has the current allowed action, permitted answer fields, actual draft revision and any existing formSubmissionId/row context supplied by the native form. Approval is an authored action/outcome, not a universal string that grants effects.
Procedure. Submit the existing task action once through its actual form flow. The HTTP task DTO uses flat output/formData, not the worker command’s VariableMap envelope; native submitActionRows/keepFields/expectedDraftRevision still follow the captured policy. Read the canonical completion receipt after the reply or an interruption. Explain decision/action display labels and progression. If the workflow includes an explicit admitted record update, inspect that separate effect under its own current reference.
Expected result. The receipt explains whether the response was recorded, is waiting for others, moved the case, or completed it. It exposes safe display/progression fields, not generic receiptId/operationId or internal case IDs. The authored route determines Approved versus Declined and any declared business effect.
Failure and recovery. A timeout does not justify another decision. Read the receipt/current task and reconcile the original submission. Do not invent missing output/action fields, submit hidden answers, call an unrelated next task a successor, or claim record status changed without its actual authored action/result.
Sources. TaskController.java:208; TaskController.java:848; TaskCompletionReceiptResponse.java:10.
Milestone 8 — Inspect the real case and document negative controls
Scenario and inputs. The accepted parent case, actual child references and related source record are known. Operations has only the current inspection/intervention rights it was granted. A separate denied reader and stale authoring tab are used only in an admitted test environment.
Procedure. Read lifecycle-context/history and resolve the original parent/child model pins. Compare business record status, lifecycle state, engine status and task receipt as separate evidence. Document a denied unrelated-user view, a stale revision save/publication and the original uncertain-action recovery path. If pausing is part of the business test, record its reason and remember that already-dispatched remote work cannot be recalled.
Expected result. The reader has an auditable explanation of this case’s design and business result, plus meaningful negative controls. Source/example validation and actual executed browser/API/DB evidence remain separate records.
Failure and recovery. A missing historical model stays unavailable rather than falling back to draft/latest. A denied deep link is neutral; an access outage is not zero cases. Keep failed and uncertain receipts, and do not start shared services, providers, CI or private/PR3228 proof work to make an unexecuted tutorial appear verified.
Sources. ProcessOperateController.java:525; ProcessOperateController.java:543; WorkflowRuntimeController.java:185.
Completion worksheet
| Evidence | Record from your admitted run |
|---|---|
| Data foundation | Model/publication/record handle and eligibility rule publication |
| Application | Actual published App Shell/page resolution and normal actor |
| Workflow | Saved assessed revision, immutable release and exact child pins |
| Start | Original native intent/context and accepted actual parent case |
| Human work | Actual task, pinned form, saved draft revision and selected authored action |
| Result | Canonical completion receipt and separately confirmed authored record effect |
| Limits | Any denied/stale/unavailable/unknown outcome and its supported recovery |
Continue with the document workflow, identity and permissions, and operation/deployment. Source-backed written steps are not a substitute for a recorded actual ordinary-user workflow when claiming product verification.