I agree. We used the same concept in a different way and we needed different approval paths based on Change Type so we actually created some additional values in the Change Type fields. It takes some minor customization to update these entries on the Change form and the corresponding approval mapping and process configuration forms. In the end, you can have your "Release" Change Type Changes follow their own approval path separate from your "child" change requests.
From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Rick Cook Sent: Tuesday, November 29, 2011 2:33 PM To: [email protected] Subject: Re: Using Change for Release Mgmt, ** That is exactly how you do it. Then manage Child Changes and tasks to allow for child changes to resolve under the parent, with the final parent approval closing the Release. Rick _attend WWRUG12 www.wwrug.com 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 attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
