Flowable Task - Use Non-Embedded Engine?

We use Camel etc. in combination with flowable.

Now we would like to use the task app for some simple user tasks. Is there a way to configure the task app to use a different engine instance that the embedded one?

The task application consists of the following modules (see https://github.com/flowable/flowable-engine/tree/master/modules/flowable-ui-task) :

  • app
  • conf
  • logic
  • rest

You can build your own task application, by doing something similar like in app (depending on logic/rest jars. maybe even depend on the app dependency to include the html/js), but not adding the default conf module and add your own Configuration classes yourself, using a custom engine configuration.

Or alternatively, have a bean with the same name that overrides the default engine (might need to add @Primary): https://github.com/flowable/flowable-engine/blob/master/modules/flowable-ui-task/flowable-ui-task-conf/src/main/java/org/flowable/app/conf/FlowableEngineConfiguration.java#L87