Documentation for end execution listeners does not explicitly state that end listeners will always trigger at the end of the activity. #3046
Labels
scope:documentation
Changes to the product documentation.
type:task
Issues that are a change to the project that is neither a feature nor a bug fix.
version:7.20.0-alpha1
version:7.20.0
Acceptance Criteria (Required on creation)
Documentation for end execution listeners does not explicitly state that end listeners will always trigger at the end of the activity.
For this specific use case, the customer creates an interrupting sub process that gets triggered, in addition, they add in a user task in the parent process with an end event execution listener. The confusion lies in the fact that the end execution listener fires even though the user task was not completed.
This is working as intended but in the documentation we don’t state explicitly that the end listener will always kick off when the activity has ended, even if the activity was interrupted.
Would it be possible to clarify this in the documentation for end execution listeners?
Hints
Here is what we have documented in our documentation specifically about end execution listeners.
Link to Documentation: https://docs.camunda.org/manual/7.18/user-guide/process-engine/delegation-code/#execution-listener:~:text=Java%20Delegates.-,Execution%20Listener,-Execution%20listeners%20allow
Links
https://jira.camunda.com/browse/SUPPORT-15500
Breakdown
Screenshot of simple BPMN breakdown of what is referenced up top.
Please let me know if you can provide any additional insight or if you have any questions.
The text was updated successfully, but these errors were encountered: