Improve UX of Deployment to Camunda Cloud

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

As a Desktop Modeler user, I am familiar with how to deploy diagrams to a local Camunda platform. But I failed to deploy to Camunda Cloud. I struggled with:

• I wasn’t sure if Contact point would accept a web address, the placeholder displays an IP
• I wasn’t sure if the URL should contain the port since the port is mentioned in the text file that I downloaded after the client creation but not in the client information dialog on the cluster page. (for contact point, the port is needed)
• I had absolutely no idea what Audience means. This term is mentioned nowhere. (it’s the cluster URL aka contact point but without the port)
• It’s annoying that the credentials are stored only when I successfully deploy a diagram although I toggled Remember credentials. During my attempts to deploy I had to enter the data over and over again (5 inputs!).
• The documentation is outdated and didn’t help at all.

Describe the solution you’d like

• For Contact point, consider a description that makes clear that it accepts a local IP as well as a web address.
• For Contact point, make clear that the port is a required information.
• On the client page on Console, add the port to the Cluster URL.
• On the client page on Console, add a field for Audience.
• The text file that I can download after client creation (with the client secret) should contain the same information as the client information dialog on Console.
• Store the credentials immediately when I toggle Remember credentials
• Bring the documentation up to date.

Describe alternatives you’ve considered

n/a

Additional context

See the differences between text file, client modal, and Desktop Modeler deploy dialog.

[MaxTru]

@nikku @barmac Thanks for raising.

We should adhere to the guideline.

@smbea @christian-konrad I propose to adjust https://github.com/camunda/camunda-modeler/issues/2862 as following:

• Keep the task to:

Extract general error message to not belong to a single field - currently, it is always applied to ‘Cluster URL’ field, regardless of which field is incorrect

• Descope:

Disable the “Deploy” button if there are validation/connection errors

[smbea]

I have adjusted #2862 accordingly