After it has been determined what has to be done, it has to be determined who will do it. Phpgroupware already has a system to manage users and groups, so that saves a lot of work. Phpgroupware also has a practical ACL system. There is however a big difference between the questions "Who is authorized" and "Who will do the task". The answer to the first question will be the same for a longer period of time. The answer to the second question can be different for each case. For example it could be practical that as many task as possible of one given case are handled by the same resource. Or maybe there has to be a separation of duties. So the assignment of tasks to resources is a much more dynamic concept.
It appears that there are more than twenty ways to assign tasks to users. At this stage, I think it is usefull to support the following ways of assigning tasks:
- by specifying a user or group
- relative, by specifying a step, and the relation to that step (same resource, different resource, ...)
- dynamic, by specifying a field in the "table with case data"
- custom, by specifying a function
Geen opmerkingen:
Een reactie posten