"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-25-2017 11:53 AM
This issue just happened to me and I was not able to figure it out until reading this string! Thanks for everyone's contribution! I will add mine that makes full sense now...I created a new table/form that was extended from alm_asset. This caused the form to contain buttons that did not make sense to utilize on the page so I did an insert and stay on the ui actions and conditioned them by adding "&& current.TableName ==" and put the new custom table name. This causes the Global UI Action to no longer display on the form and it also prevents the one created for the table from displaying. I'm not sure I understand how that works, but I learned this trick years ago. The problem is I didn't change the Action Name, so there were two UI Actions that were over the same table with the same Action Name. Once I changed the action name on the button that prevents the alm_asset table button from displaying, I no longer received the issue. Yeah!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-17-2017 02:24 AM
I had the similar issue, I've changed the Action name in UI Action for Client and it worked
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2020 11:10 PM
Ensuring my action names were unique fixed this issue for me. I had copied the Request Approval UI action and not changed the action name.
However in addition to changing the action name I had to also update the gsftSubmit function within the script. Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2020 11:17 PM
Hello USer,
The possibilities are,
1.As you remove the interceptor, it may cause an error,b.coz based on the interceptor, the state field is auto-populated.
2.Also check the process flow Formaetter. It may also the reason for the error.
3.Also try to check the error reason by clicking f12 so that inspect will get open and then go to the console.
And try to check the error over there.
Please Mark it helpful/correct if my answer helps in any way to resolve your query.
Reach out to me if any more help required.
Regards
Yash.K.Agrawal
