- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-03-2022 08:13 PM
I am trying to understand why approving a Change during a CAB Workbench meeting returned a warning message to approve the Change when attempting to navigate to the next Change record.
I approved the first Change during the meeting using the Approve button in the upper right of the meeting window. The state of the Change shifted to Scheduled and the option to approve or reject disappeared as a meeting option indicating to me that the change was approved. When I navigated to the the next Change on the agenda, I received a warning:
"Confirmation
The current agenda item has not been approved.
Do you want to move to the next item?
Cancel | OK"
Looking at the agenda item on another screen, I noticed that the state of that agenda item didn't change. I would have expected it to update from Pending to Complete.
Am I missing something?
Solved! Go to Solution.
- Labels:
-
Change Management
- 2,730 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-07-2022 11:33 AM
Not with certainty. We upgraded and ensure that there are no other outstanding approvals requested. Users now haven't been able to reproduce since those changes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-15-2022 03:50 PM
I wish I knew.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-07-2022 07:22 AM
NGanon (or anyone else on this thread) - Were you able to determine the root cause? We are having the indentical problem.
Thanks,
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-07-2022 11:33 AM
Not with certainty. We upgraded and ensure that there are no other outstanding approvals requested. Users now haven't been able to reproduce since those changes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-06-2022 08:27 AM
We too are having this issue, and we are on San Diego. When our users tested in one of our non-production instances that is already on Tokyo, they weren't experiencing the same issue. It's possible the bug is resolved in Tokyo? I suspect so, but the issue is also random, so there's no telling.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-06-2022 09:52 AM
Does anyone know if a HI ticket has been submitted for this issue?