Skip to content

Record a delete reason when tasks and activities end without completing - #4332

Open
BertMatthys wants to merge 3 commits into
flowable:mainfrom
BertMatthys:task-delete-reasons
Open

BertMatthys wants to merge 3 commits into
flowable:mainfrom
BertMatthys:task-delete-reasons

Conversation

@BertMatthys

Copy link
Copy Markdown
Contributor

Some engine paths end a task or activity with a null delete reason, so history and listeners cannot tell it from a completed one:

  • The tasks of a child case deleted together with its parent case through a case task (also a grandchild case): cmmn-state-transition-delete-case.
  • An interrupting conditional event sub-process: event subprocess(<startEventId>), with the start event as cancel activity, like the other event sub-processes.
  • The remaining activities of an ad-hoc sub-process whose completion condition is met: they are now cancelled, as BPMN 2.0.2 describes, with the new DeleteReason.ADHOC_SUBPROCESS_COMPLETED. ACTIVITY_CANCELLED is dispatched with the completing activity as cause, and the child process of a call activity ends as cancelled instead of completed. They are deleted before the completing activity is left, so all its outgoing sequence flows are still taken.

Check List:

  • Unit tests: YES
  • Documentation: NA

… condition is met

The remaining activities ended with a null delete reason, like completed ones. They are now cancelled with the delete reason "adhoc subprocess completed": ACTIVITY_CANCELLED is dispatched with the completing activity as cause, and the child process of a call activity ends as cancelled. They are deleted before the completing activity is left, so all its outgoing sequence flows are still taken.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant