-
Notifications
You must be signed in to change notification settings - Fork 494
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
Support completion condition for multi-instance #2641
Comments
@barmac Thanks for the fix. I see that this is connected to the 5.0.0-alpha release. Will that be the next generally available modeler version? Or will there be a stable release that will contain this feature? |
The alpha is already available publicly at https://downloads.camunda.cloud/release/camunda-modeler/5.0.0-alpha.0/ Feel free to check it out and share your feedback. |
@barmac I'm asking because of camunda/camunda-docs#509 (review). We want to publish the documentation once this feature is supported by the modeler. Is the alpha release a real release, or just something to try out stuff? If it's not stable, is there another stable release on the horizon? |
Let's sync via DM. |
Is your feature request related to a problem? Please describe.
Zeebe will gain support for completion condition for multi-instance with camunda/camunda#8321. Users should be able to model this expression in the modeler, instead of having to change the XML directly.
Describe the solution you'd like
I want to be able to set the completion condition expression for multi-instance elements from the modeler's properties panel.
In the properties panel, under
Multi-Instance
, a new input field could be added that:<completionCondition>
element inside the<multiInstanceLoopCharacteristics>
element if thecompletionCondition
element does not yet exist, and always updates the content of the element with the provided text<completionCondition>
element from the<multiInstanceLoopCharacteristics>
element.Describe alternatives you've considered
None
Additional context
In the xml, a multi-instance element has a
<multiInstanceLoopCharacteristics>
child element. ThismultiInstanceLoopCharacteristics
element should have a child element<completionCondition>
which itself contains the expression as content. See BPMN/2.0.2 pages 192, 198, 432 and 433.Zeebe expects the completion condition to be a FEEL-expression that evaluates to a boolean value.
Zeebe expects FEEL-expression to be prefixed by
=
.See: bpmn-io/bpmn-js-properties-panel#530
The text was updated successfully, but these errors were encountered: