-
Notifications
You must be signed in to change notification settings - Fork 107
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 FEEL for multiselect values
#673
Comments
6 tasks
bpmn-io-tasks
bot
added
in progress
Currently worked on
and removed
backlog
Queued in backlog
labels
Jun 5, 2023
pinussilvestrus
pushed a commit
that referenced
this issue
Jun 12, 2023
pinussilvestrus
pushed a commit
that referenced
this issue
Jun 12, 2023
pinussilvestrus
pushed a commit
that referenced
this issue
Jun 13, 2023
bpmn-io-tasks
bot
added
needs review
Review pending
and removed
in progress
Currently worked on
labels
Jun 13, 2023
pinussilvestrus
pushed a commit
that referenced
this issue
Jun 15, 2023
pinussilvestrus
pushed a commit
that referenced
this issue
Jun 15, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What should we do?
We should enable FEEL to populate
values
dynamically. We would have following alternativesvalues
andvaluesKey
to provide an expression (e.g.valuesExpression
values
directly and deprecate other options (cf. Enable FEEL or template for following properties #653 (comment))Why should we do it?
Follow up of #653
Community slack message: https://app.slack.com/client/T6VHNLZRR/C01Q8GLSNA1
The text was updated successfully, but these errors were encountered: