Setting up a Development Environment for Camunda HTML Forms

  • Blog
  • >
  • Setting up a Development Environment for Camunda HTML Forms

30 Day Free Trial

Bring together legacy systems, RPA bots, microservices and more with Camunda

Sign Up for Camunda Content

Get the latest on Camunda features, events, top trends, and more.

Are you developing HTML forms for Camunda Tasklist? Are you re-packaging your application with maven and re-deploying it to Tomcat or WildFly for each HMTL form change? Are you annoyed by this? 🙂

There is hope: this post explains how to setup a development environment which allows you to develop forms inside Camunda Tasklist and refresh your changes without re-packaging and re-deploying your application.

We use this kind of setup ourselves when working on the Invoice Example which is provided with the Camunda Distribution.

In the following I am assuming that you have setup an application according to the blueprint provided by our Getting Started Guide.

Step 1: Adding a Maven Profile for development

First you need to add a Maven profile for development:

          <!-- override processes.xml, providing custom process engine -->

The profile includes the Camunda Standalone Webapplication as well as the Jetty Maven plugin for starting it as part of the Maven build.

Step 2: Override some Configuration

Next we need to override some configuration. The maven profile references two resource locations to which we need to add a configuration file.

Place the following xml content into src/develop/resources/META-INF/processes.xml:

<?xml version="1.0" encoding="UTF-8" ?>


  <process-engine name="default">
      <property name="jobExecutorActivate">true</property>
      <property name="authorizationEnabled">true</property>

      <property name="isDeleteUponUndeploy">false</property>
      <property name="isScanForProcessDefinitions">true</property>


This ensures that an in-memory process engine is started and that the processes located in the classpath of the maven build are deployed to it.

Next, place the following XML content into src/develop/webapp/WEB-INF/applicationContext.xml:

<beans xmlns=""


This overrides the Spring Configuration shipped with the Standalone Web Application and makes sure the process engine is not also started using Spring.

Step 3: Start the Application and work on Embedded Forms

You can now start your application by typing

mvn clean jetty:run -Pdevelop

And opening Camunda Tasklist at https://localhost:8080/camunda/app/tasklist/.

If you now change your HTML forms or JavaScript resources, you can simply refresh the page in the Browser and the changes will be visible.


Try All Features of Camunda

Related Content

Transition smoothly from design to implementation with an end-to-end business process. We'll show you how!
See how Funding Societies is taking advantage of process orchestration to automate their lending process, greatly improving outcomes for their customers.
Process blueprints can now be found on Camunda marketplace! Read on to learn how they can help you and how you can contribute.