Most Powerful Open Source ERP

Guideline Workflows Should Define Worklists

So user knows what he has to do in My Favorites.
  • Last Update:2017-04-07
  • Version:001
  • Language:en

Workflows Should Define Worklists

Every workflow should define several worklists.

Worklists have to be configured so that a user should just have a look to his "my favourites" menu to know what he has to do in ERP5. The order of the worklist has to be defined according to the lifecycle of the related documents. It is also important to use security correctly, for a validation_workflow if you make a worklist of all states in draft state that have to be validated by the Assignee, specify Assignee in the "Role(s)" guard and add &local;_roles=Assignee in the URL. Also, whenever it makes sense, worklists names should describe what the user have to do (good example: "Documents to validate"), and not what documents are selected (bad example: "Documents in draft state"). We usually create one worklist for each step in the workflow.

Good Example:

Bad Example: