It was just whispered to me that: --quote -- The inherent group option is there but hidden due to its complexity.
It can be activated if you need it. Go to SYS:Menu Items form and search for Menu Type="Approver For". On the entry where Menu/Label 1="Inherent Group/Role", set Status="Enabled". The steps to enable is supposed to be documented somewhere on the config document. --end quote- Thanks AB. I tried and it works, giving one more option besides "Individual" and "Group" on Approval For menu on approval mappings form. What it does is you can select "inherent groups" such as "Incident Assigned Group", "Incident Owner Group" or you can select roles such as "Incident Manager" to be the approving group. So the config guide is right. But it still doesn't give you what you are looking for. Another option is to start all your approval group names with, say, "zz", or "AG-" and train people not to use those for assignment, or change the menu in the main places, such as Incident's Assigned Group and Owner Group fields to not list them. Still not an elegant solution, but what you get is proportional to the time you are willing to spend. ====== Jiri, Config guide, pg 273 talks about Inherent Group/Role, but it seems they are talking about a pie in the sky, because the approval mapping form has no such options. The menu on Assigned Group field on Incident form lists all groups for that company and organization with enabled status without regard to any other criteria, so there is no way to have any defined group not show up in that menu and still be available in approval mapping form. It does look like a step backward from old "approval role" feature. Quick dirty fix with the least amount of work/impact on the app...for groups intended only for approval, set the stauts to something that you would otherwise not use, say "Archive". Then change menu on approval mapping form to show only groups with that status...or perhaps that status and enabled ones, depending on what you wish. Will take 2 minutes. This is a quirky solution, yes, but you said you don't want to do much coding. --- Jiri Pospisil <[EMAIL PROTECTED]> wrote: - Hide quoted text - > ++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Please Read The Disclaimer At The Bottom Of This > Email > ++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > Hello listers, > > can anybody advise on a way to set up approver > groups in ITSM 7, but making sure they are not > displayed as potential assignee groups within the > Incident Management and other modules? > I cannot believe there is no way to achieve this. > Oh, the requirement is to have approver groups that > not necessarily match support groups. And it is > understandable that these approver groups should not > be displayed as potential assignee groups within > other modules, i.e. Incident. > We are trying to achieve this without any > development, just using the configuration options > ITSM 7 provides. > > Thanks for your suggestions. > > Jiri Pospisil > Remedy Administrator > IT Production > > LCH.Clearnet __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
