There are other posts on the forum about modifying the configuration files for Camunda 7, which specify which file types to auto-scan for when the application server starts up. By default it only scans for .bpmn, .dmn, .bpmn2.xml (I think). You have to modify this to also scan for .form
Auto deployment has a number of issues, that I’m not sure that updating the configuration files to scan for.form files will solve. See also Automatic Resource Deployment | docs.camunda.org
You need to add in the .form to be scanned for in this configuration
Yes, aware of EOL of 7. (Oct 2025).
We are a couple of months in with 7 because of logistical issues getting 8 supported in a corporate env. Desktop dev is also an issue given the Docker requirement for 8, which again runs afoul of corp policy.
BTW, not using .form files - just custom html, but I daresay the issue is similar.
I thought (though I’m likely wrong since I don’t do a lot of deployment - just modelling) that HTML forms were meant to be hosted on a different system…
I don’t know if I can find the documents on HTML forms in the help pages. That’s going to be your best place to look.
Ok, so the problem is nothing (yet) to do with not loading the forms.
It appears that the problem is that I have no Process Application or more specifically Process Application Name. (we have no processes.xml) This results in there being no contextPath in the form definition - which (not sure why) the web ui cannot deal with.
So, IOW, we are failing before we try and load any form.
SO, the question is, how can we set a process application name with this default project: https://start.camunda.com/
The error I am getting is:
“EMPTY_CONTEXT_PATH”: “The context path is either empty or not defined.”,
This error is nothing to do with where static resources are loaded from and everything to do with the fact that there is no Process Application (see here)
Once a Process Application (not just a process engine) has been deployed, then and only then, is it possible to load custom forms.
And the html forms are indeed loaded from classpath://static/*