Group Hierarchy

[Ann37]

Hi team,

I have a requirement in which I have to report to my executive management about how each division in my organisation has performed for that month.

When I say division, each division has more than 20 assignment groups. We have created a PA dashboard for this with scores but the problem I am facing is lack of group hierarchy in Servicenow. If A division is having 20 assignment group this tree structure is not implemented in Servicenow. If I am pulling reports from PA dashboard I have to select 20 assignment group manually, even after selecting 20 assignment groups PA dashboard is not giving me a cumulative score but individual scores for each assignment group.

Servicenow is not taking much interest to implement the group hierarchy considering the amount of work involved. If this is not implemented, is there a way to move away from manually selecting the assignment groups?

Any inputs will be much appreciated.

Attached is my PA dashboard.

Regards,

ANN

 

[Adam Stout]

What do you mean by "Servicenow is not taking much interest to implement the group hierarchy"?  It seems like setting that parent groups once would be preferable to having to multiple select on every dashboard for every user.  If you don't implement the hierarchy you also can't set targets on the chain.

[Ann37]

Thank you for your reply Adam.

Considering the organisation ORG structure group hierarchy is too huge to imagine. If this is implemented off course my life will be much simpler.Does Servicenow implement this kind of requirements? When we asked them to do they said there is lot of work involved and cannot take this requirement at this stage.

Is there a way to do this requirement in PA dashboard if it is not organised inside sys_user_group table in Servicenow using Bucket Groups etc? 

Regards,

Ann

[Adam Stout]

I don't really understand how setting a parent field in sys_user_group is a lot of work, if that data exists somewhere.  It can be an organizational problem if we don't know what the hierarchy is but any workaround to using the parent field I can think of would be a lot more work to set up (and a ton more to maintain) than doing it properly.