Page History
...
- we want to be able to display tasks independent of the presence of an underlying workflow engine
- i.e a one-shot task (e.g. a short translation assignment given to a particular user) for which setting up a whole workflow process would be overkill.
- we want to be able to retrieve the status of a given task
- ideally we would like the list to be updated automatically as new tasks arrive, are taken, updated or completed.
jBPM User
...
As the plain messages we currently use don't work well with tasks, we figured out two options
...
- PRO
- would be the "proper" way to implement manual tasks in jBPM (we currently fake them with a Service Task, that is a task usually performed by an automated system, which sends a message to Pulse)
- we'd take advantage of all the properties already available there, such as groupId, actorId, comment, etc., no need to reinvent the wheel
- CONTRA
- no clear documentation on how to integrate it - one is basically left with the source code only. TODO verify that this claim is actually true
- what about tasks independent of a workflow engine presence?
- how to make the workflow engine aware of Magnolia groups and users?
...
- would handle any type of task, regardless of a workflow engine presence
- easier to persist and query, most of the job already being done by the MessageStore API
...
A basic sequence diagram showing how Workflow and Pulse can collaborate.
A sequence diagram showing a TaskManager between Workflow and Pulse
...
Tasks
What is a User Task?
From the official jBPM documentation:
...
Overview
Content Tools