The work app is our generic extension to the workflow app. The Flow database model is a link to the Flowable process.


The workflow app (Apps) is not used to control access to the REST / Ember API (Ticket 5555).

For now, the App model is just used to help people find their way to the Ember app.


Add the apiUrl variable to the start process of the workflow. This will add the URL of the API to the variables for the process.

Create Workflow

Use a script task to set the following parameters:

var ObjectMapper = com.fasterxml.jackson.databind.ObjectMapper;

var data = {};
data.processKey = "navigatorTrainingTwo";
data.processId = execution.getProcessInstanceId();
# comma separated list of user IDs e.g. '1,2,3'
data.userPks = execution.getVariable("userPk");

var httpTaskData = JSON.stringify(data);
var json = new ObjectMapper().readTree(httpTaskData);
execution.setVariable("httpTaskData", json);]]></script>


Additional variables will be added to the new workflow (if they are included in the start event).

POST to this URL in an HTTP task:


Refresh Workflow

Update the workflow variables. Useful for long running process where information may change over time e.g. the manager for an employee.

PUT to this URL in an HTTP task:


Ember Addon

The Task::List::TaskUrl component decides whether to use Django or Ember for a task:



If the task should be handled by Ember, is_work will be true.

When the task is completed, we redirect to the next task. The code for handling this is taskRedirectTask in:


To handle all tasks using the Ember UI:

  1. Remove else from task-url.hbs

  2. Update taskRedirectTask so all tasks transitionToRoute.

  3. Remove {{#if task.is_work}} from addon/templates/task/form.hbs.