Process Hub · Business scenarios to work through
Business example: resolve a damaged-product case
Build and run a Forms process from customer intake through Quality review to resolution.
On this page
Before you start
- Use a training profile and synthetic data. NovaNest Living is a fictional home-goods business; names, records and amounts below are examples, not installed customer configuration.
- Ask your administrator to prepare the approved runtime connection and member roles. Use the linked build guide before this walkthrough; only authorised people should publish/deploy.
People and field plan
Care logs and resolves the case; Quality verifies the damage. Use real authorised profile identities for these responsibilities.
On smaller screens, scroll the table sideways to see all columns.
| Setting | How to use it |
|---|---|
| customer_reference / Text | CUST-DEMO-01 |
| order_reference / Text | SO-1001 |
| issue_type / Choice | Damaged, Missing, Other |
| description / Long text | One bottle arrived cracked |
| quality_finding / Long text | Required when returning from Quality |
| resolution_notes / Long text | Required to close |
| evidence / Attachment | Synthetic photo/document only |
Action plan
On smaller screens, scroll the table sideways to see all columns.
| Action / transition | Required evidence | Work effect |
|---|---|---|
| Send to Quality: New → Quality review | issue_type and description | Complete Care work; create claimable Quality task due in one day. |
| Return to Care: Quality review → Resolution | quality_finding | Complete Quality work; create claimable Care resolution task. |
| Close case: Resolution → Closed | resolution_notes | Complete current Care work; no next task. |
Follow these steps
Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.
- Create a standalone Forms process named Customer Case using the build guide. Add the example fields below and use stable keys. Configure intake requirements and evidence attachments.
- Enable Business lifecycle. Add New (First after submit), Quality review, Resolution and Closed (Terminal). Configure intake fields editable before submission, Quality finding editable during review and Resolution notes editable during resolution. Under After submission add a Task / My Work assignment to the Care role for initial triage.
- Create the three actions in the action plan below. Use Change state, explicit allowed/target states and required evidence. For each handoff complete current stage work and create the named next task; Close case completes current work without a new task. Set work access to the assigned user or role claimant where ownership is required.
- Save, publish and deploy. Grant Care and Quality the process/record access and navigation they need. Configure any separate optional due-event notification policy and release it; remember lifecycle assignment already sends required In-app notification.
- As Care, create case CASE-1001 for order SO-1001: issue Damaged, description “One bottle arrived cracked”, plus demo evidence. Save a draft, reopen it and confirm the lifecycle has not started. Submit, confirm New and claim the Care triage task when required.

Save draft keeps unfinished work. Complete required answers before starting final submission. - Use Send to Quality. As an eligible Quality member, find/claim the task, review the evidence and enter “Packaging damage confirmed” in quality_finding. Return it to Care with the configured next task.
- As Care, record “Replacement agreed” in resolution_notes and use Close case. Check the completed work/history and that the closed record leaves an active Operational Queue.
- Repeat with missing resolution notes, a user outside Quality and an overdue review task. Confirm the expected block/access/message result in each case.

A terminal stage can leave the record visible and read-only. Follow the process owner’s correction procedure when work must be revisited.
Expected test outcomes
On smaller screens, scroll the table sideways to see all columns.
| Setting | How to use it |
|---|---|
| Save draft | No lifecycle entry yet. |
| Submit | State New. |
| Send to Quality | Care work completed; Quality work created/claimable. |
| Close without resolution notes | Blocked with required-field validation. |
| Close with evidence | State Closed; no active stage task. |
What you should see
One customer case retains its evidence and history across clear stages, with the correct worker owning each task.
If something goes wrong
Care cannot edit the final notes
Check Resolution field access and the current work owner/claim. A global read-only setting still wins.
The example was expected to create a refund or shipment
This process records the resolution. Actual refunds, replacement orders or shipping need separately configured supported processes/integrations.