Marcelo/Rick, I am running CHM 7.0.3 p7 and have multiple approval phases working. For close down (and for all the other phases), I ended up setting the OOB phases to Offline and creating my own. We have multitenancy set but only 1 company. I created new approval phases that are specific to our company. On the "Approval Process Config" form, APR-SysApproval Definition I think, the Close down approval is set to use the Process Name - Change Level -Close down. Not sure if you checked this but the field System Approval Flag is Null. If set to YES, the approval will automatically approve regardless of any mappings set.
Marcelo, When you say that the phase does not fire off when you are testing, when you hit the status of Completed, do you then have to manually use the Process Flow Wiz to move it to closed or does it go to Completed and then to Closed? If it is doing the latter, then you may have the Sys approval flag set to Yes. Also, >From reading your post, it shows that part of your criteria is based on Risk. >There is a defect out there in which in the Approval Mappings form, the field >label is "Approve if Risk <=". However, this is wrong. It should be "Approve >if Risk >=" The workflow works in that if a Change has a risk level >= 3 (for >example), the approval will fire. Check that out. I'm thinking that may be the issue here. Tauf Chowdhury | Forest Laboratories, Inc. Analyst, Service Management Mobile:646.483.2779 -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Martinez, Marcelo A Sent: Tuesday, January 12, 2010 6:47 PM To: [email protected] Subject: Close Down approval 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] ARSlist: "Where the Answers Are" ********************************************************************** This e-mail and its attachments may contain Forest Laboratories, Inc. proprietary information that is privileged, confidential or subject to copyright belonging to Forest Laboratories, Inc. This e-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this e-mail, or the employee or agent responsible for delivering this e-mail to the intended recipient, you are hereby notified that any dissemination, distribution, copying or action taken in relation to the contents of and attachments to this e-mail is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender immediately and permanently delete the original and any copy of this e-mail and any printout. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
