Workflow overview
In Casewhere, all actions related to cases require a workflow, whether it involves purchasing parking tickets, applying for jobs, or sending newsletters. Casewhere offers two types of workflows:
- UI workflows — Display data or collect information from end-users through UI elements. Triggered by users through widgets. Casewhere provides a workflow definition editor with a form builder for designing complex and dynamic UI activities.
- Automatic workflows — Triggered automatically by system events, database changes, or other workflows. Casewhere offers a wide range of workflow triggers for flexible solution design.
To define how workflows operate, create a workflow definition in Casewhere Admin. This specifies the data classes (and thus the processes and cases) the workflow can interact with, the activities to execute, and the triggers that initiate them.
In this section
| Topic | Description |
|---|---|
| Workflow definition | Create and configure workflow definitions |
| Steps and activities | Organize workflows into steps with activities |
| Workflow navigation | Control activity inclusion, required/optional logic, and editability |
| Workflow execution | Triggers, states, and execution paths |
| Concurrency control | Prevent race conditions with exclusive locks |
| Transaction | Atomic, consistent, isolated, and durable operations |
| Triggers | UI · Time · Data · Event · Web |
| Activities | Form · Script · Workflow · Dynamic Workflow · Loop · Stop |