How to Design a Multi-Step Approval Process in Process Designer

In many business scenarios, an approval process involves more than one approver — for example, a department head followed by a finance manager. In ONEWEB, you can design this type of workflow using Process Designer with BPMN elements, SLA tracking, and conditional logic.


1. Open Process Designer

  • In your AppSpace, create a new process in Process Designer.
  • Give it a clear name (e.g., PurchaseRequestApproval).

2. Define the Workflow Stages

Common stages for a multi-step approval process:

  1. Submission – The requestor submits a form (trigger process start).
  2. First Approval – Task assigned to Approver 1 (e.g., Department Head).
  3. Second Approval – Task assigned to Approver 2 (e.g., Finance Manager).
  4. Finalization – System updates records or triggers related actions.

3. Configure Human Tasks

  • Drag Human Task nodes for each approval stage.
  • Use Role-Based Assignment to route each task to the correct user group or role.
  • Link each task to a Smart Form for the approver’s decision.

4. Add Conditional Logic

  • Use Gateways to control process flow:
    • Approved → move to the next approver.
    • Rejected → end process or send back for revision.
  • For parallel approvals, set the gateway to wait for all responses before continuing.

5. Apply SLA and Escalation Rules

  • Define Service Level Agreements (SLA) for each approval stage (e.g., 2 business days).
  • Configure escalation paths if an approver does not respond in time.

6. Integrate with Data & Pages

  • Use Smart Forms to trigger the process when a request is submitted.
  • Display process status in a dashboard page so requestors and managers can track progress.

7. Test and Monitor

  • Use the Process Monitoring Dashboard to track live instances.
  • Check for bottlenecks and adjust SLA or routing rules as needed.

:light_bulb: Pro Tip: Clearly define your approval rules — for example, unanimous approval vs. majority approval — before building the workflow. This avoids rework and ensures your process matches your organization’s policy.