Guidelines for manual fix of User Action condition to disable "Insert and Stay" for users without create permission - Known Error

Guidelines for manual fix of User Action condition to disable "Insert and Stay" for users without create permission Description The condition current.canCreate() is written so the UI Action "Insert and Stay" is shown for any non-new record.

Cause: A user who has create permission and opens an existing record satisfies the condition, so the UI Action is visible.

Clicking Insert and Stay runs the insert logic and creates a new record for the user having create ACLs — the UI condition allows visibility, and the action implementation does not block creation server-side.

Steps to Reproduce

1. Log in to any OOTB instance. 2. Impersonate a user with "write" access to `cmdb_ci_service_discovered` but no "create" access. 3. Open an existing `cmdb_ci_service_discovered` record and click on the "Form header menu". 4. Notice that the "Insert and Stay" UI Action is still visible and can be executed. 5. The user is able to "insert a new record" despite lacking create access.

Workaround Login to instance.

Impersonate with user that has "ui_action_admin" role

Go to UI Action ( .service-now.com/sys_ui_action.do?sys_id=2120e647f32232003c37ae4716612bbe%29" target="_blank" rel="noopener noreferrer">https:// .service-now.com/sys_ui_action.do?sys_id=2120e647f32232003c37ae4716612bbe )

Update "Condition" field with the following: current.canCreate() && current.canWrite() && JSUtil.nil(RP.getParameterValue("sysparm_changeset"))

Click on "Save" in the "Form header menu".

This workaround is applicable for version Z and above.