I am designing the embedded forms in a simple text/html editor (IntelliJ IDEA in this case). Not using any kind of visual designer.
I am setting the form-key of the user task in the Camunda Modeller desktop app (Linux version). (I can edit the XML directly if necessary but I use the Modeller for setting many development/execution related attributes after I get it from the business analyst. I will need to continue to make changes on it with the Modeller after I set the form-key for a task)
I am deploying the forms together with the bpmn diagram into the Camunda instance (with the Camunda Modeller during development, probably the REST API in production via the CI/CD pipeline)
If you have access to the java code, one way to do things is to store your forms anywhere you like, bind the form key to where you stored your form and return the form data when you’re returning the task.
This way you can be efficient with your forms and not worry much about re-writing stuff all over again.
I thought you were gonna render the form on an independent app and not in the camunda modeler. This is why I recommended you use the form key field to bind it to another form-id, in the UI you are rendering your forms in.