Zeebe User Tasks

[pinussilvestrus]

• Adds support to model user tasks in Zeebe diagrams
• Adds the Headers and Input/Output tab for user tasks
• Adds the new user task form definition for user tasks

Related to camunda/camunda-modeler#2104

Can be tested via

npx @bpmn-io/sr camunda/camunda-bpmn-js#2104-zeebe-user-tasks -c "npm run start:cloud"

[pinussilvestrus]

@andreasgeier fyi: I think a design review is not necessary for this one, since it includes one input field only. The rest is part of what we discussed yesterday.

[pinussilvestrus]

The zeebe-bpmn-moddle changes are released and integrated ✅

[barmac]

I left one comment to be addressed and also have two remarks below:

• How about if we validate the form configuration to not accept non-JSON input?
• A single-line input looks a bit odd for a multi-line JSON. Still, if this is a transition state I am OK with leaving this as it is.

[barmac]

Great job overall :)

[pinussilvestrus]

• How about if we validate the form configuration to not accept non-JSON input?
• A single-line input looks a bit odd for a multi-line JSON. Still, if this is a transition state I am OK with leaving this as it is.

Good points. I think since we have a transition state here, it's okay to not have validation and the single line input. I'd not put any more effort into the user interaction.

[pinussilvestrus]

I added another commit (bb96973) which adds an modeling behavior which

• ensures cleanup on deletion & replace
• ensures a new user task form with the same content on copy & paste

Ready for review again.

[pinussilvestrus]

@barmac @MaxTru any chance to get this thing reviewed / merged?

[barmac]

I can look into that today.

[barmac]

One unexpected behaviour:

When I copy a User Task from one diagram to another,
the form definition as well as zeebe:userTaskForm are copied
but the form contents are removed (Form JSON Configuration is empty).

I am OK with merging the PR as it is.

[pinussilvestrus]

I think that's pretty much because we can't currently copy the userTaskForm properly, since we don't know where to get the value from, since the rootElement from the copied one isn't available in the newer diagram.

I would also be fine with merging this and wait once someone is reporting it.