For now the task are managed only using JBPM.
This made sense as long as we were using JBPM.
In the context of the integration of Content Routing as a default workflow engine in DM, keeping Tasks in JBPm does not make sense.
So the target is to build a simple task service based on Documents.
In order to make migration as transparent as possible we should be sure that :
- existing automation APIs for creating / listing tasks : will now manage Document based tasks
- existing widgets can display the new Document based tasks without needing changes
The goal for this task is to be able to provide ContentRouting as a 5.5 Addon without having to migrate data and without having to keep JBPM.
=> Be sure all Task related feature can work without any change using the Document based task system