In Servicedesk Change Management, if a Task, such as an implementation task is put on hold, and the timeout value is reached while still on hold, the Change Request loses its ability to be worked. There are no tasks to activate.
There is, in the design of SD.ChangeManagementSimple, a hanging path component which has a incorrectly configured value for timeout. The process reaches this component via a timeout, and errors, because the timeout variable is incorrect.
This will be fixed in a future release of Servicedesk.
Subscribing will provide email updates when this Article is updated. Login is required.