While not yet taken advantage of in ITSM OOTB, AR System did introduce hierarchical groups in AR System 7.6.0x to address these kind of situations:
Hierarchical group relationships for access control You can now define a parent-child relationship between access control groups to simplify permissions management. When this is defined, and when the object properties allow for permission inheritance, object permissions assigned to the child group are also granted to the parent group. A group hierarchy can also be applied dynamically during row-level security processing to grant permission to a parent group, if the appropriate object properties are enabled. See the Form and Application Objects Guide, “Using a parent group for permissions inheritance.” Perhaps through some customizations, you can take some advantage of this. It is hoped that ITSM applications will take full advantage of this in a future release. -David J. Easter Manager of Product Management, Remedy Platform BMC Software, Inc. The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Frank Caruso Sent: Tuesday, May 08, 2012 7:35 AM To: arslist@ARSLIST.ORG Subject: Number Of Support Groups ITSM 764 sp2 Due to how the organization is structured the number of support groups needed is becoming very large. The company has hundreds of locations to support throughout the country and each location has specific personnel assigned to support that location. My current estimate is there will be over 1200+ support groups. Due to the limited number of Support Group Levels provided in ITSM the menu display of support organizations and groups that will be presented to end users will be large. Through the use of templates and auto assignment most incidents can have a support group auto populated, but I am wondering whether I should attempt to decrease the number. Are there any limitations in ITSM on the number of support groups that can be created/managed? Has anyone else had to configure a large number of support groups? In order to assign an incident to a support person they must be part of a support group, or is there some other hidden way to handle this in ITSM 764? Since there are only two levels to define a support group, can anyone share some possible naming conventions? (This company is split out by roughly 10 regions which could be set using the Organization field). Any feedback is appreciated. Frank _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
