Here's the situation. We're doing approvals by CI. Our "Business Approvers" are not always support staff. We have about 75000 CIs and business approvers are required in 3 of the 4 approval phases for 90% of those CIs. I need a way to build a grouping of "non-support" people and "support staff" people into a "one-must-sign" approval algorithm. I could use a series of support groups: <CI NAME> BUSINESS APPROVERS, <CI NAME> IMPLEMENTATION APPROVERS, and <CI NAME> CLOSE DOWN APPROVERS. But creating those collections of people as support groups causes the groups to have a support consideration in the system (the groups show in the "Assignment" menus for incident, change, task, etc.). Going that route also concerns me in terms of the number of records that will end up in the group cache (3+ for every CI=225000 group entries). We don't want to modify the OOTB workflow if we can avoid it. Any ideas as to how I might accomplish this?
It was easy in v.5 and v.6. Back then the approval mappings and approval roles did not consider support groups as the source for collections of people. Sometimes I miss those days. Thanks, Jonathan Jones Southern Company Services 205-257-4799 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
