Lab 9 — Approval workflow for plan updates
Purpose: Build and run a review-then-publish workflow for PHI plan page changes, including rejection and audit inspection.
Who this page is for
| Audience | Why it matters to you |
|---|---|
| All engineers | Pairs with Session 9; completes the core journey |
Goal
Premium changes to plan pages must be approved by a "plan-reviewers" group before publication. Build it, run it, reject once, approve once.
Steps
- Create group
plan-reviewers(add yourself); create a test author userplan-editorwithout replication
rights on /content/phi.
- In the Workflow Models console, copy "Request for Activation" to a new model "PHI Plan Approval".
Set the participant step's assignee to plan-reviewers; add a process step after approval that activates the page.
- Sync/enable the model. As
plan-editor, edit the gold-hospital premium and use Request Publication —
pick your model if prompted, or configure it as the default for /content/phi/plans.
- As a reviewer: open the Inbox, find the task, reject with a comment. As
plan-editor, see the item return. - Resubmit; this time approve. Verify the page activated (check publish tier / replication queue).
- Inspect: Workflow console → instances/history for your run; page → Audit log for the activation record;
page versions — find the version created on activation and view the diff.
Checkpoint
| Verify | Expectation |
|---|---|
| plan-editor direct publish | Not possible — request flow enforced by missing replicate ACL |
| Reject path | Returns to initiator with comment intact |
| Approve path | Page activated; replication queue clear |
| Audit trail | Activation + workflow steps visible with users and timestamps |
You have completed the core journey
You can now model content, build authorable components with models and styles, govern them with templates, deliver them through the dispatcher, and operate their content lifecycle. Next stops: Developer Reference for depth, Production Readiness before your first release.