Yeah, I saw that. All of our Approval Processes have nothing selected for Change Timing, and on the Mappings, they are Normal for the Close Down Approvals.
Rick On Tue, Jan 12, 2010 at 4:28 PM, Martinez, Marcelo A <[email protected]>wrote: > ** > > FYI… if we do get it to work, here is an article that says that there is a > defect if the change has “latent” timing selected, the close down approval > will not fire. > > > > BMC Knowledge Base article ID: 20006650 > > > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *Rick Cook > *Sent:* Tuesday, January 12, 2010 6:16 PM > > *To:* [email protected] > *Subject:* Re: Close Down approval > > > > ** No, it looks like you have all bases covered. FWIW, there is a thread > on the BMCDN for the same issue on Patch 7. > > > http://communities.bmc.com/communities/message/135856#135856 > > Rick > > On Tue, Jan 12, 2010 at 4:12 PM, Martinez, Marcelo A <[email protected]> > wrote: > > ** > > Rick, > > Have you taken any other steps than I have? Anything else you think I > should check? > > > > Thanks, > Marcelo > > > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *Rick Cook > *Sent:* Tuesday, January 12, 2010 5:52 PM > *To:* [email protected] > *Subject:* Re: Close Down approval > > > > ** 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" > > > _Platinum Sponsor: [email protected] ARSlist: "Where the Answers > Are"_ > > _Platinum Sponsor: [email protected] ARSlist: "Where the Answers > Are"_ > > > _Platinum Sponsor: [email protected] ARSlist: "Where the Answers > Are"_ > _Platinum 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"
