Easily react on process execution to evaluate complex variable handling with code or update the internal database.
User Problem 🤦
Summary:
Customers require the ability to perform pre and post-execution tasks, often involving custom code, for activities within a process definition. These tasks should not be represented as separate steps in the BPMN diagram, as they are purely technical in nature.
Details:
Currently, there is a lack of functionality to respond to transitions within a process instance in order to track the progress of process execution in external systems and execute code both before and after specific process elements. The external code typically encompasses business logic that relies on data from various internal systems to update flow node instances before or after specific elements.
The only available option for achieving this functionality is by employing code within an external task, which is limited to service tasks. In scenarios where such logic needs to be applied to other elements, this approach becomes impractical, as it either becomes impossible or necessitates the modeling of service tasks before and after each activity.
Release Notes
Have you ever faced a situation when you needed to add pre- and post-processing logic for specific elements in the process definition without bloating the diagram? With this release, Camunda introduces Execution Listeners to respond to transitions within a process instance effectively. Users can now add ELs to any activity, including process instances, to facilitate their use cases.
Developers can use the existing job worker concept to efficiently handle listener jobs, passing additional variables as needed and using usual job properties like retries or job type.
User Stories 🧑🚀
Modeling
As a Process Designer, I can model Execution Listeners (EL) on any activity, including Process Instance
As a Process Designer, I can define ELs for different event types (start and end)
As a Process Designer, I can define a job (listener) definition type - to subscribe to as a worker
As a Process Designer, I can define the same properties as for the “usual” job (retries, etc.)
Execution
As a Developer, I can use the existing job worker concept to work on the listener job. This involves API, incidents and process operations
A a Developer, I can pass additional variables when completing a listener job
Documentation and monitoring
As a Developer, I can read documentation about Execution Listeners - concept, how to use that
As a Product Manager at Camunda, I can track the usage of Execution Listeners
Value Proposition Statement 🚀
Easily react on process execution to evaluate complex variable handling with code or update the internal database.
User Problem 🤦
Summary: Customers require the ability to perform pre and post-execution tasks, often involving custom code, for activities within a process definition. These tasks should not be represented as separate steps in the BPMN diagram, as they are purely technical in nature.
Details: Currently, there is a lack of functionality to respond to transitions within a process instance in order to track the progress of process execution in external systems and execute code both before and after specific process elements. The external code typically encompasses business logic that relies on data from various internal systems to update flow node instances before or after specific elements.
The only available option for achieving this functionality is by employing code within an external task, which is limited to service tasks. In scenarios where such logic needs to be applied to other elements, this approach becomes impractical, as it either becomes impossible or necessitates the modeling of service tasks before and after each activity.
Release Notes
Have you ever faced a situation when you needed to add pre- and post-processing logic for specific elements in the process definition without bloating the diagram? With this release, Camunda introduces Execution Listeners to respond to transitions within a process instance effectively. Users can now add ELs to any activity, including process instances, to facilitate their use cases.
Developers can use the existing job worker concept to efficiently handle listener jobs, passing additional variables as needed and using usual job properties like retries or job type.
User Stories 🧑🚀
Modeling
Execution
Documentation and monitoring
Implementation 👷
Scope:
:robot: This issue is automatically synced from: source