Well, all I can say is that we're having the same problem. The users have the right permissions, the Approval Process is configured, the Approval Mapping references it, but it just doesn't fire. I would love to see a little help on this, too!
Rick On Tue, Jan 12, 2010 at 3:47 PM, Martinez, Marcelo A <[email protected]>wrote: > Hello Listers, > Need help in implementing close down approvals for Change Management > version 7.0.03 (ARS7.1 / SQL2005). I have PhaseName: "implementation > approval" working.. > > I am able to create an "Approver Mapping" select the correct > categorization, criteria, set the "Phase Name*" to Close Down Approval and > set level=1 and approve if risk is <=3. > > I have gone to Application Admin>Foundation>Advanced Options>Approval > Process Configuration: > Using the default process with name "Close Down Approval". > Begin: Completed (no status reason) > Approved: Closed (no status reason) > Rejected: Rejected (no status reason) > No Approvers: Closed (no status reason) > > Problem: when I create a change ticket, send it off thru the phases, then > resolve it... the close down approval does not fire. > > I'm sure I'm missing a step, if anyone has implemented this close down > phase please advise what to check? (in the meantime I'll keep going over the > Approval Server Manual for Users and Admins). > > Do I need to check/create/enable something under AP:Administration????? > > Thanks!! > > Marcelo Martinez > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum > Sponsor:[email protected]<sponsor%[email protected]>ARSlist: > "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
