Form Type Selection Is Misleading

Describe the Bug

The current form type selection on a user task is wrong.

The option <none> can contain form fields for generated forms.

The option Embedded or External Task Form shows the Formkey, which can be filled with a Formkey for a Camunda Form as well: https://docs.camunda.org/manual/7.16/user-guide/task-forms/#form-key

The option Camunda Forms opens the reference to a deployed form. Camunda Forms can be used by Formkey as well.

Steps to Reproduce

1. Create a new BPMN Process for Camunda Platform
2. Add a User task
3. Open the Form tab
4. Select an option from the dropdown

Expected Behavior

The names on the options should fit to the field that the developer has to fill after the selection.

If I select none, nothing else can be added. I would like to select Formkey to fill a camunda Form Formkey. I would like to select Deployed form to fill the reference to the deployed form. I would like to select Generated Form to fill the form fields.

For a new user it seems that Camunda Forms always need a deployment.

Environment

• OS: Windows 10
• Camunda Modeler Version: 4.11
• Execution Platform: don’t care, But my preference is Spring-Boot, 7.16
• Installed plug-ins:

---

Related to CAM-14004

[barmac]

This one is in fact fixed upstream as long as we don’t release and update bpmn-js-properties-panel.

Fixed upstream via https://github.com/bpmn-io/bpmn-js-properties-panel/pull/574

[ingorichtsmeier]

In the moment this issue is a blocker to use the Camunda Forms in our Dev-Trainings. I would appreciate it, if you could just change the labels in the next release of the Camunda Modeler (after the UX discussion).

Maybe move the <none> -part into a different issue.