Actions
The Actions tab lets you configure startable items — processes and building blocks that end users can trigger directly from a case. These actions appear under the start button when viewing an existing case.
Actions provide a way for users to initiate additional workflows from within an existing case. This is useful for:
Starting follow-up processes related to the current case
Triggering reusable building blocks that perform common operations
Providing users with context-specific actions without requiring them to navigate elsewhere
There are two types of actions:
Process
A BPMN process definition linked to the case. Starting this action runs the process in the context of the current case.
Building block
A reusable building block that can be configured with input/output mappings. See Building blocks for more information.
Configuring actions
Expand Admin in the left sidebar
Click Cases under the Configuration section
Click a case definition to open it
Click the Actions tab

The list shows all configured actions with their names and types.
Adding an action
Click Create an action
Select the action type: Process or Building block

Select the specific process or building block from the dropdown

For building blocks, click Next to configure input/output mappings if needed
Click Add to save the action
Reordering actions
Actions can be reordered by dragging and dropping rows in the list. The order determines how actions appear to end users in the case view.
Editing an action
Click a row or use the overflow menu (⋮) on the right side of the row
Select Edit

For processes, change which process is linked; for building blocks, update the input/output mappings
Save your changes
Deleting an action
Click the overflow menu (⋮) on the row you want to delete
Select Delete
Confirm the deletion in the confirmation dialog

Access control
Actions are filtered based on the user's permissions. An action only appears to users who have permission to execute it.
Resources and actions
com.ritense.valtimo.operaton.domain.OperatonExecution
create
Required to start the process associated with the action. This applies to both process actions and building block actions (which have an underlying main process).
When an action is triggered from within a case, the permission check includes the current document as context. This allows permissions to be scoped based on the specific case instance using context conditions.
Examples
Last updated