Generic vs Specific workflows

[hreintke]

LS,

When I see the examples of workflows in afresco they are more or less variations on a generic review/approve cycle. The review is either by one person, multiple persons of a group or one of the group members.
Some are combined with a lifecycle status update.

This creates several, nearly identical models.

- Is there a reason for creating all these separate workflows ?
- Would it be possible to create one workflow where the intiator can select one or more persons, groups or pools and the task flow depends on the users input ?

Kind regards,

Herman Reintke

[davidc]

We provide specific examples to demonstrate the capabilities, and to allow copy/paste configuration.  We don't provide a combined one (yet, anyway) as everyone's requirements are different.

Having said that, it is possible to create a workflow whose flow depends on user input.  We actually do that for Web Content Management - the submit process allows the user to select serial or parallel review etc.

At a high level this is achieved by defining a task that collects the relevant information (e.g serial or parallel, assign to person, group or pool, the person(s), group(s) etc).  Then in the process definition use <decision> nodes to redirect the process to the next appropriate state based on the information entered in the task.

Take a look at config/alfresco/workflow/submit_processdefinition.xml for an example.

[hreintke]

David,

Thanks for the link. Gives me a nice starting point for further investigation.

Herman