Support placeholder for properties (String, Text)

[johnBgood]

Is your feature request related to a problem? Please describe.

We would like to guide the users, placeholders are a best practice for this use case.

Describe the solution you'd like

We could use a new placeholder property in our JSON templates. This should be available for String, and Text properties. Not sure it makes sense for others.

Describe alternatives you've considered

Currently, we use tooltips but it doesn't have the same purpose imo.

---

Cf. template generation good practices

[barmac]

I think it makes sense. Thanks for the suggestion.

[johnBgood]

tagging @sbuettner for information
tagging @YanaSegal for design information
tagging @chillleader for context, as we'll need to update the Element Template Generator to support this as well

[crobbins215]

@nikku is this something we could add to the spring cleaning list?

[nikku]

Tagged accordingly and added to the list. The value is clear; we just have to ensure this lands consistently across our different editors, including our FEEL editor (cf. CodeMirror#placeholder).

[YanaSegal]

I am adding this doc for context.

[nikku]

@YanaSegal any specific section in the document you want to highlight? Any specific detail you want to share?

[nikku]

@johnBgood Maybe you could share a specific place where you'd see values from placeholder strings (attach a screenshot). This helps us to better understand the user value these bring.

[johnBgood]

@nikku Absolutely, here's an example using the SQL Connector.

Using placeholders we would avoid the user reading the docs as it's super that we want a specific format (JDBC URL), and that the best practice is to set the user/password using variables instead of the URL.

I hope it clarifies the purpose, let me know if you have more questions.

[barmac]

I am looking into this.

[barmac]

So this assumes that the FEEL editor supports a placeholder.

[barmac]

Breakdown:

• allow to provide a placeholder in the JSON schema feat: support placeholder property camunda/element-templates-json-schema#144
• support placeholder in the FEEL editor feat: support placeholder feel-editor#52
• support placeholder in the properties panel entries Support placeholder in text and FEEL text entries properties-panel#363
• pass placeholder to custom properties from the templates feat: support placeholders on String and Text properties #103