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.

SettingHow to use it
customer_reference / TextCUST-DEMO-01
order_reference / TextSO-1001
issue_type / ChoiceDamaged, Missing, Other
description / Long textOne bottle arrived cracked
quality_finding / Long textRequired when returning from Quality
resolution_notes / Long textRequired to close
evidence / AttachmentSynthetic photo/document only

Action plan

On smaller screens, scroll the table sideways to see all columns.

Action / transitionRequired evidenceWork effect
Send to Quality: New → Quality reviewissue_type and descriptionComplete Care work; create claimable Quality task due in one day.
Return to Care: Quality review → Resolutionquality_findingComplete Quality work; create claimable Care resolution task.
Close case: Resolution → Closedresolution_notesComplete 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.

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
    Customer Case form with case fields, Print / PDF and Save draft.View full size ↗
    Save draft keeps unfinished work. Complete required answers before starting final submission.
  6. 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.
  7. 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.
  8. Repeat with missing resolution notes, a user outside Quality and an overdue review task. Confirm the expected block/access/message result in each case.
    Completed case with read-only answers and a Closed label.View full size ↗
    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.

SettingHow to use it
Save draftNo lifecycle entry yet.
SubmitState New.
Send to QualityCare work completed; Quality work created/claimable.
Close without resolution notesBlocked with required-field validation.
Close with evidenceState 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.

Need a hand?

Contact your organisation’s Emplyr administrator using your usual internal support channel.

How to ask for help