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.
Script tasks were automated using engine-internal scripting.
Beside only supporting FEEL, Zeebe currently does not have the capabilities to execute script tasks using inline or referenced scripts.
However, the converter prepares a script task to be executed like a service task, using a special job type and headers that describe the scriptFormat, script or scriptResource.
Describe the solution you'd like
On booting the adapter, a script worker will come up that is implemented exactly against the converted script task.
Is your feature request related to a problem? Please describe.
Script tasks were automated using engine-internal scripting.
Beside only supporting FEEL, Zeebe currently does not have the capabilities to execute script tasks using inline or referenced scripts.
However, the converter prepares a script task to be executed like a service task, using a special job type and headers that describe the scriptFormat, script or scriptResource.
Describe the solution you'd like
On booting the adapter, a script worker will come up that is implemented exactly against the converted script task.
The script worker can be taken from here: https://github.com/camunda-community-hub/zeebe-script-worker
Given all scripting engines that were registered to the process application are still there, we should be able to execute the scripts like before.
Describe alternatives you've considered
There is a script worker project in the community hub as well, maybe this one could be re-used
Additional context
.
The text was updated successfully, but these errors were encountered: