I've had a question from some of our application users on the change management status flow.
Our existing system is running on ARS 7.5, with a virtually standard 7.6 change management installation. In the early days of the systems configuration, we decided that when a change was rejected, that it would go to a status of cancelled (with a status reason giving a further breakdown). Sometimes a change may be rejected due to scheduling conflicts, at which point it is restarted, new dates put in and goes back through the approval process. It'll happily move a change from cancelled back to draft. Due to changes in other parts of the business, I've been asked to look into rejections setting the status to rejected. The problem appears to be that rejected is a very definite "final" status, there is no status transition rule configured to allow move back to draft. From a brief look at our 8.1 installation (which is only partially live), it looks to have exactly the same configuration. So, the question - on ITSM 7.6 and onwards, once a change is rejected, is that it? No chance of restarting the request? If so, I'm guessing the suggestion is that a new change should be submitted, according to BMCs understanding of the ITIL guidelines? Regards Dave Barber _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
