Action not authorized message when creating a new Workflow

[riaz_mansuri]

When I try a create a new workflow I am now receiving the error Action not authorized

The table I am trying to create a workflow from is the ast_contract

I am an Admin and have never seen this before

Any ideas?

Thanks,

Riaz

[riaz_mansuri]

Hopefully the resolution to mine is the same as yours. The agent with my ticket is also aware of your one.

[riaz_mansuri]

Sorry just to update I have not received a fix for this yet.

[Binh Truong2]

Hi Steven,

I am now experiencing this issue after upgrading to Helsinki. Have you heard back?

Thank you

[sgoldberg]

Hello Binh,

Here is the solution to INT2986364

Issue Summary: While creating a new contract and hitting the 'submit for reveiw" button UI Action. A blue banner pops up stating "Action not authorized".

Reason: Duplicate UI Actions Names

Solution Proposed:

Action Name on a UI Action must be unique within the instance. Risk Management added a UI Action also named "Submit For Review" with an Action Name of "submit_for_review" (table = Issue ), which caused a conflict with an identical UI Action used in Contract Management.

Find UI Actions for duplicate Action Names and rename one of them, being careful to also change the action name if it is referenced in the script.

[riaz_mansuri · Accepted solution]

I have received the solution from Service Now and it is now working well.

I had a UI action which worked before but when the system upgraded from Geneva Patch 1 HF 5 to Geneva Patch 3 HF 2, on June 9th it broke.

The current release, it shows the UI Action, even if the condition is false. Then when trying to Submit the form, the issues occurs.

UI Action name is Submit

The last valid version, applied contained the following condition: current.canCreate() && !current.getTableName()=='change_request' The exclamation mark at this position is evaluated before the comparison (==) and therefore, it fails, returning false. The correct condition, which was applied in both instances, should be like this: current.canCreate() && current.getTableName() != 'change_request' Now the != is evaluated correctly comparing the return or getTableName method and comparing it with the string 'change_request'.

The issue is resolved.

Thanks,

Riaz