Team hierarchy using workgroups
Hi,
I have always wondered why there is not a hierarchial structure in a workgroup.I could only see a manager and his reportees.This question is only from a vsibility standpoint and not routing .Just to know if we could make use of the OOTB worklist reports to show the manager , team leader and supervisor different levels of worklist according to the reporting structure
Supervisors will see only their reporting team
Teamleaders should see oly their reporting team and so on
How to configure a team like below using Workgroups and show OOTB worklist instead of customizing
Accepted Solution
Pegasystems Inc.
US
Hello,
I think that things get tricky if you have n levels of reporting, but should be doable for a static structure (i.e. one Manger has 2 Team leads reporting to her and each of them has two to four employees). You're basically looking to build out the tree structure and find a way to display it. I don't know of something handy and out of the box. If I were going to do that (particularly if I don't know the number of layers in the organization), I would probably not use reports, as my sole source, I would create an activity that could call itself recursively. I would have it take a user ID as a param and then call a report definition to find all users with that individual as the manager and add them to a page list. Then I'd call the activity again with each of those individuals as the value of the param and so on, until you've built the tree structure in the clipboard. From there, use nested repeat grids to display it.
I think for large, complex organizations performance may not be great, but at least it would give you a starting point and for something small enough, should be sufficient.
Thanks,
Mike
Accepted Solution
Pegasystems Inc.
US
Hello,
I think that things get tricky if you have n levels of reporting, but should be doable for a static structure (i.e. one Manger has 2 Team leads reporting to her and each of them has two to four employees). You're basically looking to build out the tree structure and find a way to display it. I don't know of something handy and out of the box. If I were going to do that (particularly if I don't know the number of layers in the organization), I would probably not use reports, as my sole source, I would create an activity that could call itself recursively. I would have it take a user ID as a param and then call a report definition to find all users with that individual as the manager and add them to a page list. Then I'd call the activity again with each of those individuals as the value of the param and so on, until you've built the tree structure in the clipboard. From there, use nested repeat grids to display it.
I think for large, complex organizations performance may not be great, but at least it would give you a starting point and for something small enough, should be sufficient.
Thanks,
Mike