"Action not authorized" when requesting a Change
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-21-2013 10:29 AM
We recently modified our Change creation process, such that we removed an interceptor that directed the user to the change form. Now, when a user creates a Change Request, they have to save the Draft prior to clicking the "Request Approval" button. If they do not, they get the Info message, "Action not authorized", no record is created, and the work that they did is lost.
Has anyone seen anything similar or have any ideas?
- Labels:
-
Change Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2013 09:00 PM
I have just solved a very similar issue.
In my case, the key was understanding that the conditions on the UI Action are checked *again* on the server once the item is submitted. While I don't fully understand why, my change was no longer meeting the conditions by the time the server checked this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-04-2013 02:32 AM
I also have a similar issue on our DEV instance. It seems the conditions in the UI Action refer the the script running and not just the button being visible. I had a condition in the UI Action which said "(current.approval=='not requested')". When the Request Approval UI Action ran it changed the state to Requested, which then caused the condition to fail with the "Action not authorized" message. I took out that condition and it's now working fine. The wierd thing is the condition is the same on our Production instance and it is working fine there.
Paul Rogers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-16-2014 07:27 AM
We had a similar issue and received the "Action not Authorized" message when requesting approval. Removing the condition in the button receiving the message did not resolve the issue. We had updated two other Request Approval UI Action buttons to perform some validation first and had added duplicate action names. Once we made all three action names unique, the Request Approval completed successfully and we no longer received the "Action not Authorized" message.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-22-2014 04:47 AM
Thanks, this helped me I had duplicated the 'resolve_incident' because I wanted to have a different button for end-users, but I kept the same 'action_name', so I got the error 'Action not Authorized' and I wondered why.... I changed the 'action_name' on the button for the itil users to 'resolve_incident_itil' and now it works! Important is then also to change the action-name call in the gsftSubmit function within the script.