In Camunda Platform 8, I can define an inline FEEL expression for a BPMN script task

[saig0]

Problem you would like to solve

Since Camunda Platform 8.2, a BPMN script task can define an inline FEEL expression. If the process instance enters the script task then it evaluates the FEEL expression and writes the result in a process variable with the given name.

Sample XML:

<bpmn:scriptTask id="Activity_1f7zluu">
    <bpmn:extensionElements>
        <zeebe:script expression="=today()" resultVariable="result"/>
    </bpmn:extensionElements>
</bpmn:scriptTask>

Previously, a script task could define only a job type and job retries. The new option to define an inline FEEL expression is an alternative implementation of the script task. It is similar to the different options for a BPMN business rule task.

I want to model a process that contains a script task with an inline FEEL expression.

Proposed solution

• zeebe-bpmn-moddle supports zeebe:script
• Allow to implement Script Task as a FEEL expression bpmn-io/bpmn-js-properties-panel#825
• Linting validates script task support for 8.2+ bpmnlint-plugin-camunda-compat#67
• Support implementation rule in bpmnlint-plugin-camunda-compat linting#38

Alternatives considered

None.

Additional context

• Product hub issue
• Zeebe issue

[nikku]

Cannot be happier to see this issue open. A good day for users of Camunda 8. 🎉

[nikku]

As I understand this will be released with the next zeebe alpha? If not, please clarify.

[CatalinaMoisuc]

fyi, issue added to the breakdown of the Product Hub epic: https://github.com/camunda/product-hub/issues/511.

[barmac]

If I select the Camunda Platform version 8.2 for my BPMN process then I want to choose the implementation of a new BPMN script task.

The way we handle unsupported features in Desktop Modeler is via linting rules, i.e. you are still able to select the unsupported feature but you see an error on the diagram. This is how I'd implement this.

[barmac]

This one will not make it to the 5.6 release.

[barmac]

With all tasks done, this will be part of the next release.