We have this issue as well. We use emergency change and as long as the change is entered within 24 hours, we find we can use the progress bar up top to walk the change through it's lifecycle. We can't use the dates tab or it will give us the error you say, but if we use the progress bar up top and enter dates when prompted, it works fine.
Anne Ramey *********************************** E-mail correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties only by an authorized State Official. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Enslin Van Blerk - MWEB Sent: Tuesday, May 18, 2010 10:35 AM To: arslist@ARSLIST.ORG Subject: ******** Change issues Classification > "Timing" "Timing Reason" etc. ** Hi I require your assistance please. I don't really work with the Change management module thus I am a bit in the dark here, asking this question. We have occasions where people will do a change in production and then 3hours later, they want to log the change and resolve it etc. According to what I found in the documentation these changes can be logged as a Latent Change and will then close automatically. We can use this but it is not always the case and sometimes for record purposes we still require people to approve. People log tickets as an emergency in these situations and because this was logged as an emergency we cannot close the ticket because it was logged after the actual start dates. First we get a message, telling us it will be saved to Expedited because the Requested Date is before the earliest Start Date. I will save it as expedited, enter the times for actual start/end date. Then it will tell me, Only Latent changes can have actual start dates that come after the infrastructure change submit date. At this point we have values in "Earliest Start Date" and "Submitted Date" If we try to save the timing field to latent we just receive ARNOTE again telling us it will be saved to Expedited because the Requested Date is before the earliest Start Date. We are not able to close this change with the correct times now, what can we do with these situations? Regards Enslin ________________________________ [https://webmail.mweb.com/logos/footer.gif]<http://www.mweb.co.za/productsservices/> This electronic communication and the attached file(s) are subject to a disclaimer which can be accessed on the following link: Disclaimer<http://www.mweb.co.za/disclaimer> - or copy the following URL into your browser - http://www.mweb.co.za/disclaimer. If you are unable to view the disclaimer, please contact ab...@mweb.com<mailto:ab...@mweb.com> for a copy. ________________________________ _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
