Workflow activity
Introduction
Workflow activity is a solution for reusing shared functionality. It allows us to share some forms or scripts for different workflows.
For example, "sending email" is a frequently used feature. It can be used to make a new account, change an email address, or warn about something...
Using workflow activity, we simply create a workflow called "Sending Email" and then add it to other work flows.
To add new workflow activity in Casewhere, you can find it in the Add Activity Definitions section, and drag it into the step of workflow.
Configuration
The following details are needed to set up workflow activity:
Name: A name must be unique and meaningful.
Workflow Definition: Choose the workflow you want to run. It's also referred to as "embedded workflow."
Input Data Objects: It is only used for the "edit case" workflow. There are two options for sending data to the workflow.
Get("VariableName"): retrieves the value of a variable in the current workflow.
LoadDataObject("DataClassName").Id: Load a data object from the data class.
Process: A new case is created every time Casewhere executes the workflow.
Output Workflow Variable: Create a variable that holds the value returned by the workflow.
Queue Workflow: When checked, the workflow will be queued and executed in the background.
Navigation: Setting for navigation between workflow activities. To learn more, read the article Activity Navigation.
Advanced Settings: Configure some additional advanced settings for the form.
The advanced settings are:
| Settings name | Description |
|---|---|
| Auto Commit Changes | If this checkbox is ticked, the filled data will be committed automatically without completing the whole flow. This setting is used to support the case of multiple activities where the next activity needs the data from the previous one before completing the flow. These settings should only be used when necessary, because they may have a negative effect on performance. |
| Audit Event Name | Is used to customize the event name for audit. From version 2.7, Casewhere auto audits all events that change the data state. The activity name is used for audit by default, but you can customize it by using this settings. |
| Enable Exclusive Lock | Casewhere allows you to control concurrency at an activity level using an exclusive lock. To learn more, read the article "Workflow concurrency control". |
| Lock Context (optional) | When the exclusive lock is enabled, Casewhere will only allow one activity to execute at a time, in the entire system. This is obviously not optimized for many scenarios. By providing a lock context, you can control the concurrency logic on a more granular level. For example, you can enable the lock on specific data objects to execute more activities as long as they're on different objects. The setting accept an expression using the same syntax with navigation rule |
| Waiting Timeout | Casewhere will release the lock if it lasts longer than the configured timeout, even when the activity is not finished. |