Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reset active sequence flows upon terminate end event activation #10789

Merged
merged 2 commits into from Oct 26, 2022

Conversation

remcowesterhoud
Copy link
Contributor

@remcowesterhoud remcowesterhoud commented Oct 21, 2022

Description

After a terminate end event has been completed the flow scope should be completed as well. When there are active sequence flows this doesn't happen as we have checks preventing a flow scope from completing when there is any active element instance or active sequence flow. By resetting this on activation of the terminate end event we can pass this check.

Related issues

closes #10590

Definition of Done

Not all items need to be done depending on the issue and the pull request.

Code changes:

  • The changes are backwards compatibility with previous versions
  • If it fixes a bug then PRs are created to backport the fix to the last two minor versions. You can trigger a backport by assigning labels (e.g. backport stable/1.3) to the PR, in case that fails you need to create backports manually.

Testing:

  • There are unit/integration tests that verify all acceptance criterias of the issue
  • New tests are written to ensure backwards compatibility with further versions
  • The behavior is tested manually
  • The change has been verified by a QA run
  • The impact of the changes is verified by a benchmark

Documentation:

  • The documentation is updated (e.g. BPMN reference, configuration, examples, get-started guides, etc.)
  • New content is added to the release announcement
  • If the PR changes how BPMN processes are validated (e.g. support new BPMN element) then the Camunda modeling team should be informed to adjust the BPMN linting.

Please refer to our review guidelines.

@github-actions
Copy link
Contributor

github-actions bot commented Oct 21, 2022

Test Results

   948 files  ±  0     948 suites  ±0   1h 42m 6s ⏱️ - 2m 41s
7 488 tests  - 84  7 480 ✔️  - 85  7 💤 ±0  1 +1 
7 680 runs   - 84  7 670 ✔️  - 85  9 💤 ±0  1 +1 

For more details on these failures, see this check.

Results for commit 13d00b2. ± Comparison against base commit c5f0f0a.

♻️ This comment has been updated with latest results.

Copy link
Member

@saig0 saig0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@remcowesterhoud looks good. 👍

I have one optional suggestion. Please have a look.

… completed

After a terminate end event has been completed the flow scope should be completed as well. When there are active sequence flows this doesn't happen as we have checks preventing a flow scope from completing when there is any active element instance or active sequence flow. By resetting this when the terminate end event is completed we can pass this check.
@remcowesterhoud remcowesterhoud force-pushed the 10590_parallel_gateway_terminate_end_event branch from 64f5a93 to 13d00b2 Compare October 26, 2022 12:14
@remcowesterhoud
Copy link
Contributor Author

bors merge

@zeebe-bors-camunda
Copy link
Contributor

Build succeeded:

@backport-action
Copy link
Collaborator

Successfully created backport PR #10821 for stable/8.1.

zeebe-bors-camunda bot added a commit that referenced this pull request Oct 26, 2022
10821: [Backport stable/8.1] Reset active sequence flows upon terminate end event activation r=remcowesterhoud a=backport-action

# Description
Backport of #10789 to `stable/8.1`.

relates to #10590

Co-authored-by: Remco Westerhoud <remco@westerhoud.nl>
@korthout korthout added the version:8.1.3 Marks an issue as being completely or in parts released in 8.1.3 label Nov 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
version:8.1.3 Marks an issue as being completely or in parts released in 8.1.3
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Terminate end event does not terminate process when waiting at parallel gateway
4 participants