AT:

• Expose org.camunda.bpm.engine.FormService.getTaskFormData(String) via REST API
• Expose org.camunda.bpm.engine.FormService.getStartFormData(String) via REST API

—

Original description:

This request is based on forum topic 10714 but also 3057 and 347. Unfortunately provided solutions in this topics are not at all satisfactory.

I understand Camunda has lots of functionality when running as an embedded engine in another application or when Camunda web interface is used as the interface for the users. But I think all functionality should also be available from REST API if you want to build you own interface. This means you should be able to retrieve ‘all relevant information’ from entities in a structured way (JSON obviously) to build your own user interface or logic.

We intend to run Camunda in it’s own load balanced server environment as a micro service. This means we need to interact with it over REST from other applications in our architecture. But unfortunately when we retrieve the form variables from a user task, we don’t get the possible enum values, constraints and properties, which we need to build our own form fields in our interface. Currently, we only get:

{
“monthlyExpenses”: {
“type”: “Long”,
“value”: null,
“valueInfo”: {}
},
“monthsOfBuffer”: {
“type”: “Long”,
“value”: null,
“valueInfo”: {}
},

(It looks like this is more based on the current values of variables, not so much on the variables themselves.)

Where is (for example) the element “enumValues” and “constraints” of the form variables?

In topic 347 rubenjgarcia does provide some work around code to get the enum vales out of the forms from the process definition XML dump. But this is, in our opinion, just a work around. The REST API should provide this.

So the question is: can one of the Camunda developers add this to the product development backlog?

Thanks!