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.

Sign up for GitHub

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

Jump to bottom

Support completion condition for multi-instance #5439

Closed
lzgabel opened this issue Sep 28, 2020 · 2 comments · Fixed by #8321
Closed

Support completion condition for multi-instance #5439

lzgabel opened this issue Sep 28, 2020 · 2 comments · Fixed by #8321
Labels
blocker/stakeholder Marks an issue as blocked, waiting for stakeholder input kind/feature Categorizes an issue or PR as a feature, i.e. new behavior scope/broker Marks an issue or PR to appear in the broker section of the changelog version:1.3.0 Marks an issue as being completely or in parts released in 1.3.0

Comments

@lzgabel
Copy link
Contributor

lzgabel commented Sep 28, 2020 •
edited by saig0
Loading

Is your feature request related to a problem? Please describe.
Now there is a scenario where I have a multi-instance, i need set a completion condition for multi-instance when one of them is completed, all instance job are completed.

Describe the solution you'd like
Support a completion condition for multi-instance.
@lzgabel lzgabel added the kind/feature Categorizes an issue or PR as a feature, i.e. new behavior label Sep 28, 2020
@saig0 saig0 changed the title Is there any plan to support completion condition for multi-instance in the future? Support completion condition for multi-instance Sep 28, 2020
@saig0
Copy link
Member

saig0 commented Sep 28, 2020

Related topic in the forum: https://forum.zeebe.io/t/how-to-set-completion-condition-for-multiinstance/1643

@saig0 saig0 added scope/broker Marks an issue or PR to appear in the broker section of the changelog Status: Needs Priority and removed Status: Needs Triage labels Sep 28, 2020
@npepinpe npepinpe added blocker/stakeholder Marks an issue as blocked, waiting for stakeholder input and removed Status: Needs Priority labels Sep 28, 2020
@saig0
Copy link
Member

saig0 commented Sep 28, 2020

This attribute is defined in the BPMN specification.

See also the usage in Camunda 7 here: https://docs.camunda.org/manual/7.13/reference/bpmn20/tasks/task-markers/#multiple-instance

@lzgabel lzgabel mentioned this issue Dec 7, 2021
Merged
9 tasks
@korthout korthout mentioned this issue Dec 14, 2021
Closed
@lzgabel lzgabel mentioned this issue Dec 16, 2021
Closed
@ghost ghost closed this as completed in 9e70bb9 Dec 20, 2021
@korthout korthout added the version:1.3.0 Marks an issue as being completely or in parts released in 1.3.0 label Jan 4, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blocker/stakeholder Marks an issue as blocked, waiting for stakeholder input kind/feature Categorizes an issue or PR as a feature, i.e. new behavior scope/broker Marks an issue or PR to appear in the broker section of the changelog version:1.3.0 Marks an issue as being completely or in parts released in 1.3.0
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(engine): support completion condition for multi-instance lzgabel/zeebe
4 participants
@npepinpe @korthout @saig0 @lzgabel