You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Conditions (and other places with FormalExpressions) currenly ignores the language attribute and always assumes that the content is JUEL. Some conditions are hard or impossible to write in JUEL (i.e. "is the country of one of the addresses in the US?"), so it would be great to be able to use i.e. Groovy instead.
Describe the solution you'd like
SequenceFlows (and BoundaryEvents etc.) should parse the language attribute of the bpmn:condition. ExpressionManager.createExpression() should use the language to load the ScriptEngine using javax.script.ScriptEngineManager, probably only accepting languages from a configurable whitelist.
It looks like a fairly straightforward task, and I will be happy to supply a PR, if I can get an indication that it is likely to be merged.
The text was updated successfully, but these errors were encountered:
rasmusfaber
added a commit
to rasmusfaber/flowable-engine
that referenced
this issue
May 14, 2024
Is your feature request related to a problem? Please describe.
Conditions (and other places with
FormalExpressions
) currenly ignores thelanguage
attribute and always assumes that the content is JUEL. Some conditions are hard or impossible to write in JUEL (i.e. "is the country of one of the addresses in the US?"), so it would be great to be able to use i.e. Groovy instead.Describe the solution you'd like
SequenceFlow
s (andBoundaryEvents
etc.) should parse thelanguage
attribute of thebpmn:condition
.ExpressionManager.createExpression()
should use the language to load theScriptEngine
usingjavax.script.ScriptEngineManager
, probably only accepting languages from a configurable whitelist.It looks like a fairly straightforward task, and I will be happy to supply a PR, if I can get an indication that it is likely to be merged.
The text was updated successfully, but these errors were encountered: