Script tasks behave exactly like service tasks. Both task types are based on jobs and job workers. The differences between these task types are the visual representation (i.e. the task marker) and the semantics for the model.
When a process instance enters a script task, it creates a corresponding job and waits for its completion. A job worker should request jobs of this job type and process them. When the job is complete, the process instance continues.
Jobs for script tasks are not processed by Zeebe itself. To process them, provide a job worker.
Defining a task
A script task must define a job type the same way as a service task does. It specifies
the type of job workers should subscribe to (e.g.
Review the Zeebe Script Worker. This is a community extension that provides a job worker to evaluate scripts. You can run it, or use it as a blueprint for your own job worker.
A script task with a custom header:
<bpmn:scriptTask id="calculate-sum" name="Calculate sum">
<zeebe:taskDefinition type="script" />
<zeebe:header key="script" value="a + b" />