The following is the description about the FileNet Roaster. Does camunda provide the similar function?
T-San
A workflow roster is a database structure that stores information about all workflows in an isolated region. Workflow rosters provide the workflow system and workflow administrators with an efficient way to locate specific active workflows.
However, I think the FileNet roaster is different than Cockpit. The roaster is a task queue.
In general, we create a queue for each step of a workflow.
When the work of a step is completed, this task is stored in the queue (roaster) of the next step.
The access right is defined for each roaster.
By using roaster, a user can know which tasks in which roasters are candidate tasks for him/her.
When login to the workflow system, a user’s task list would be something like
Step 1 ----- Task A, Task B
Step 3 ------ Task F
Step 5 ------ Task X, Task Y
User will select a task to be processed from the task list. (Only accessible tasks are displayed)
I hope Camunda does implement this concept in a different way. If so, I’d like to know how to do it.