Workflow steps and activities
A Casewhere workflow is composed of steps and activities. Steps and activities are executed in the order they were designed. The below example shows how a workflow looks in Casewhere Admin and in worker site. Here you can see that a workflow is generally a sequence of steps, and a step can have one or more activities.

On a worker site, the workflow opens in a dialog. The step pane on the left lists the steps by their labels, and the form of the current activity fills the rest of the dialog. Script activities run without showing anything to the user. In the example below, the user has completed Step 1, and the dialog shows Applicant form of Step 2 with the applicant that the script activity Set data source of Step 1 has chosen.

Configure steps
In the Steps section of the workflow definition editor, click Add step to add a new step.

A step has the following fields:
| Name | Description |
|---|---|
| Name | Step name in a workflow must be unique |
| Label | The step title is displayed in the workflow wizard. You can use a text resource key here |
| Hide Activity Navigation Pane | If a step has more than one activity, you can enable a tab-pane to support your users in navigating between activities. |
| Always Show | The step is always displayed in the workflow wizard, even when none of its activities is included. |
For automated workflows, steps don't have much meaning as they do in UI workflows and are mostly used for organizing activities in the workflow definitions. It's still a good practice to group related activities in the same step.
Configure activities
You can add one or more activities to a step: select the step and click an activity type in Add activity, or drag the type onto the step.

Currently, Casewhere supports the following activity definitions:
| Name | Type | Description |
|---|---|---|
| Form | UI Activity | Collect information from or display information to end-users |
| Script | Automated Activity | Execute a C# script |
| Workflow | Automated Activity | Execute another workflow |
| Dynamic Workflow | Automated Activity | Execute a workflow determined dynamically at runtime based on conditions |
| Loop | Automated Activity | Loop through data objects filtered by a given condition and trigger a new workflow per data object |
| Stop | Automated Activity | Terminate the workflow execution immediately |
The key difference between a UI and an automated activity is that when the workflow engine navigates to a UI activity, it will idle while awaiting end-user interaction. No end-user interaction is needed for automated activities — the workflow engine continues after executing them.