On Hold Button for Change Request
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Friday
What is the out of the box functionality for the On Hold Button in the Change Management instance. When I've tested it in UAT I noticed when the On Hold button is selected it eliminates any approvals. When the hold is removed the approval is no longer needed and the request is moved to the next approval group without promoting the change to the next state. It's not stuck because there is no way to trigger the change to go into a scheduled state because the On Hold feature skipped the approval.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sunday
Hi @DimyraP,
Change tasks inherit some state conditions from the parent change request they are related to. When a change request is placed on hold, these conditions are applied to it:
- If the change is waiting for approval, the pending approvals are marked No Longer Required. When the change request is no longer On Hold, the pending approvals are reinstated and are Awaiting approval.
- The change can progress only to the Canceled state while it is On Hold.
- If a change request is canceled while it is On Hold, then its On Hold flag is set to false so the change cannot be canceled and still be On Hold.
- If the change request is set to On Hold, the value of the On Hold field for all the active change tasks for that change request is set to true and the On hold reason is copied from the change request to the change tasks.
- If you clear the On Hold check box in a change request, the On Hold field for all the active change tasks for that change request is set to false and the On hold reason is cleared from the change tasks.
- If the change request is canceled, all the active change tasks related to that change request are also canceled.
- A change request can only be closed when all the active change tasks related to that change request are closed or canceled otherwise a pop-up appears notifying that there are open change tasks that require to be closed.
- If there are existing change tasks that are manually placed on hold, those change tasks do not get overwritten when the change request is placed to the On Hold state. Similarly, when the change request is taken off the hold state, the change tasks that were placed on hold manually stays in the On Holdstate.
Source: Place a change request on hold
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */