We are seeing an issue where, when we apply a task to a change the next approval is skipped. For example, if the normal path is Draft->Request for Auth->Request for Change then if I apply a task while the change is in Draft status, when the user tries to move the record to the next stage, it goes to Request for Change and skips Request for Authorization completely. It's not that it is applying the approvers and thinking it has been approved, it seems to skip the step entirely as if it weren't part of the process flow. We are using ARS 7.5 p 6 with ITSM 7.6 p 1. Has anyone else seen this? Does anyone have ideas on how to fix? I'm thinking it must be a hidden field that helps the ticket apply the approvers or know what the next stage is that task creation also writes into-causing confusion. I've not had luck in finding it yet, though.
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. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
