Workflow overview

In Casewhere, all actions related to cases require a workflow to be executed, whether it involves purchasing parking tickets, applying for jobs, or sending newsletters. Casewhere offers two types of workflows:

• UI workflows: Display data to your users or collect information from them using UI elements. UI workflows are triggered by end-users through widgets. Casewhere provides a workflow definition editor with a form builder, allowing you to design complex and dynamic UI activities.
• Automatic workflows: Triggered automatically by events in the system, changes in the database, or other workflows. Casewhere offers a wide range of workflow triggers, providing the flexibility needed to design solutions for a variety of complex scenarios.

To define how workflows operate in Casewhere, you must create a workflow definition in the Casewhere Admin. This will specify the data classes (and thus the processes and cases) with which the workflows can interact, as well as the activities that will execute under specific conditions. Since workflows do not execute automatically, you will also need to define the workflow triggers, specifying who or what can initiate them.