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

Deploy workflow with sequential multi-instance service task / sub-process #2847

Closed
saig0 opened this issue Jul 16, 2019 · 0 comments · Fixed by #2919
Closed

Deploy workflow with sequential multi-instance service task / sub-process #2847

saig0 opened this issue Jul 16, 2019 · 0 comments · Fixed by #2919
Assignees
Labels
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

Comments

@saig0
Copy link
Member

saig0 commented Jul 16, 2019

Is your feature request related to a problem? Please describe.
I want to use sequential multi-instance on a service task and sub-process to execute it for each element of a collection - one-by-one.

Describe the solution you'd like

  • I can mark a service task / sub-process with the multi-instance marker and isSequential=true
  • when one instance of the service task / sub-process is completed, it creates the next instance for the collection
  • when the last instance is completed, the service task / sub-process is left

Same as #2845 and #2846 but sequential instead of parallel.

Additional context

The BPMN XML could look like:

    <bpmn:task id="Task_1f0s1iu" name="task">
      <bpmn:multiInstanceLoopCharacteristics 
        isSequential="true"
        zeebe:collection="items" 
        zeebe:elementVariable="item" />
    </bpmn:task>

requires #2845
requires #2846

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants