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
If a script task is converted, the header used to define the scripting language is scriptFormat, just like it was in Camunda 7.
This is not compatible with the zeebe-script-worker which requires language
Steps to reproduce
Define a Camunda 7 script task with inline script and script format
Convert it
The scriptFormat has become the header scriptFormat
Run the process with the zeebe-script-worker
it fails as no language is present
Expected Behaviour
The scriptFormat is translated to language
Library version
0.6.1
Camunda Platform 7 version
7.20.0
Camunda Platform 8 version
8.3.0
The text was updated successfully, but these errors were encountered:
As a follow-up: I've seen the issue mentioned in the release 0.8.0, and I'm wondering if the dependency to the script-worker, that is introduced here, is documented anywhere?
Maybe it's worth to provide an example for script migration? And explain which docker contain to integrate to the cluster.
Describe the bug
If a script task is converted, the header used to define the scripting language is
scriptFormat
, just like it was in Camunda 7.This is not compatible with the zeebe-script-worker which requires language
Steps to reproduce
Expected Behaviour
The scriptFormat is translated to language
Library version
0.6.1
Camunda Platform 7 version
7.20.0
Camunda Platform 8 version
8.3.0
The text was updated successfully, but these errors were encountered: