Greetings listers! I've been seeing some oddities in our change approval process lately so I wanted to kick this out to the list for feedback. The Details: We're on AR 7.0.01 Patch 006 (Win2k3, SQL 2005, etc); we're using Approval Server 7.0.01 and Change Management 7.0.03 Patch 006. At "Scheduled for Review" we call the Change Management Chain process to get manager approval. After approved it goes to Scheduled for Approval where it awaits Change Manager (CAB) approval. So here's the catch...if you manually add an approver before the change is in one of these approval processes it screws everything up. Lets say I add 3 people prior to the approval process...then move the change to "Scheduled for Review" and my manager is added. If my manager approves before the other 3 people the change moves to the next status. Sometimes we get duplicate approvers and in trying to cancel the duplicates it can cause the change to jump to the next status (per the Approval Process Configuration settings) which totally screws everything up. Anyone seen this type of behavior before?
Thanks! Eli _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
