Modeler 5.0 doesn't show multi-line fields for scripts anymore

[michaelarnauts]

Describe the bug

The rework of the property panels in 5.0 doesn't support multi-line property fields anymore. This is needed when writing a script to be executed by a script worker (on Camunda Platform 8), or when working with JSON values.

Steps to reproduce

1. Add a script task.
2. Give it type script so it can be picked up by https://github.com/camunda-community-hub/zeebe-script-worker for example.
3. Add a header language = javascript.
4. Add a header script and try to add a script there. There is only room for one line.

Expected behavior

It should be possible to expand the input field so it can contain multi-line values. This is how it worked in Modeler 4.x and earlier.

Environment

• OS: Ubuntu 22.04
• Camunda Modeler Version: 5.0
• Execution Platform: N/A (happens with Camunda Platform 7 and 8 BPMN files)
• Installed plug-ins: N/A

Additional context

No response

[pinussilvestrus]

Thanks for your request!

The rework of the property panels in 5.0 doesn't support multi-line property fields anymore

The properties panel still supports multi line fields, for example Camunda Forms configuration

Headers are one-line inputs, that was already the case in Camunda Modeler 4.x

I think this is intended, as the docs don't describe the option for multi-line values.

If you think this would be a valuable addition, let's make this one a feature request and discuss it 👍

/cc @christian-konrad

[christian-konrad]

@michaelarnauts What is your use case of adding a script to the header?

[michaelarnauts]

It seems to be the way how it's implemented in https://github.com/camunda-community-hub/zeebe-script-worker

Also, there is no other field available in models for Camunda 8.

[irlaer]

I have the same problem with editing names of elements

[marstamm]

@irlaer , I believe this is a slightly different issue (name vs. script fields). I created https://github.com/bpmn-io/bpmn-js-properties-panel/issues/705 to track the Name issue

[nikku]

I think this is something we want to have (again), some day. Moving to backlog.

[nikku]

CC @christian-konrad

[nikku]

Improved upstream via https://github.com/bpmn-io/bpmn-js-properties-panel/issues/705.

[michaelarnauts]

Fixed upstream via bpmn-io/bpmn-js-properties-panel#705.

Only for name field, not for the headers or field injections.

[nikku]

Thanks @michaelarnauts.

Removed fixed upstream. Would be a good candidate to now clean this up end-to-end. We have all foundations in place.