Guideliness for creating task groups

[Kouw, FA - SPLTX]

Hi,
 
Is there someone who has some good advise on how to create useful task
groups? With this I mean guidelines for grouping task groups, workflow
templates and tasks in such a way that these groupings are useful for
monitoring purposes.
 
F.i. I have 3 workflows WS A, WS B and WS C. WS A only consists of
tasks, WS B and WS C contain sub-workflows and tasks (WS B contains WS
B1 and WS B2, WS C contains WS C1).
 
One way to group these WS/TS is:
 
   * TG 1: all main workflows (WS A, WS B and WS C)
 
Another ways is to create task groups for each workflow and include
these in another (main) task group. Next it's also possible to include
the sub-workflows (and/or the tasks in the task groups).:
 
   * TG 1: WS A + (?) all tasks in WS A
   * TG 2: WS B + (?) WS B1, WS B2 + (?) all tasks in main workflow
     and/or sub-workflows
   * TG 3: WS C + (?) WS C1 + (?) all tasks in main workflow and/or
     sub-workflow
   * TG 4: TG 1, TG 2, TG 3
 
What is handy depends on the way the transactions that support task
groups for selection purposes use the task groups components. Basically
I need to know if it's a smart thing to include sub-workflows and tasks
in task groups, or is it sufficient to only include the main workflows
in one overall task group.
 
Regards,
 
Fred Kouw
 
 
 
**********************************************************************
This e-mail and any attachment may contain confidential and privileged
material intended for the addressee only. If you are not the addressee, you
are notified that no part of the e-mail or any attachment may be disclosed,
copied or distributed, and that any other action related to this e-mail or
attachment is strictly prohibited, and may be unlawful. If you have received
this e-mail by error, please notify the sender immediately by return e-mail,
and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its
subsidiaries and/or its employees shall not be liable for the incorrect or
incomplete transmission of this e-mail or any attachments, nor responsible
for any delay in receipt.
**********************************************************************
 
_____________________________________________________________________________________________
This outbound message from KPN has been checked for all known viruses by KPN IV-Scan, powered by MessageLabs.
For further information visit: http://www.veiliginternet.nl
_____________________________________________________________________________________________