[Implement Tracking] Enable FEEL and Templating for more properties

[Skaiir]

This is the implementation epic for https://github.com/camunda/product-hub/issues/722

What should we do?

We have just successfully integrated the feelers syntax in the text component text property in 8.2. We want to now convert over a few properties in the application to accept this syntax or simply FEEL expressions.

This includes

This needs to be broken down properly

• Support readonly
• Move disabled to a toggle switch #639
• Update FEEL toggle properties-panel#240
• Add optional FEEL checkbox and toggle switch properties-panel#194
• Enable FEEL or template for following properties #653
• Ensure getSchemaVariables utilities are updated
• Clarify breaking changes (if any)
• https://github.com/camunda/form-linting/issues/52
• Ensure schema version is updated
• https://github.com/camunda/team-hto/issues/247
• Integrate updates into products
  • Tasklist
    • add dev data for readonly
    • add dev data for more expressions
  • Desktop Modeler
  • Web Modeler
• Spread the word

Why should we do it?

Change the behavior of your form reactively via simple rules, based on the context provided by process variables and other form input.

We have the technical capabilities in place, now let's enable it.

Additional context

Related to https://github.com/camunda/product-hub/issues/722
Related to this, and tightly coupled: https://github.com/camunda/product-hub/issues/918. It makes sense to start on this in parallel, to have the proper support of FEEL in readonly
Miro: https://miro.com/app/board/uXjVMMtnox0=/

[pinussilvestrus]

A user mentioning disabled as needed for FEEL: camunda/camunda-modeler#3600 => responding that readonly even fits better 👍

[pinussilvestrus]

Kickoff results

https://miro.com/app/board/uXjVMMtnox0=/

• We consider use feelers for all feel optional string fields
• We do not support FEEL for disabled
• We consider a standalone docs page about templating (not only in text views)
• @pinussilvestrus to clarify with @RomanKostka and @christian-konrad: really no tracking? => we aim to handle this via generic properties panel tracking
• Follow up: initiate for BPMN properties (e.g. task title)
• Discuss discouraging disabled fields (cf. Discourage the use of disabled fields #362)
• @pinussilvestrus to clarify with @RomanKostka: how do we indicate feelers fields? => not separately, as we indicate them via the optional FEEL icon already

[pinussilvestrus]

Implementation is done and released via [email protected], basically waiting for the next release cycle for integration into Tasklist and the Modelers.