Help with Prescedence of UI Actions

[SEDatSAS]

The case task form is displaying a Delete button that I want to remove. I went to the UI actions and it seemed that the Delete action was coming from the Global table, so I copied the global one, changed the table to sn_customerservice_task and added the condition  gs.hasRole("admin"). I only want admins to see the button.

It works as expected in the CSM Workspace after the change. But if I use the classic UI a non-admin user still has the delete button. The UI Action table now has three Delete actions for the form table. How do I ensure that my table specific version takes precedence over the the global actions?

Thanks in advance.

Sue

[Community Alums]

You can check below things

1)Check UI Action Order: First, check the order of UI actions for the form table. Go to System UI > UI Actions and filter by your form table (sn_customerservice_task). Ensure that your table-specific Delete action appears before any global Delete actions in the list. You can adjust the order by modifying the Order field.

2)Check Conditions: Ensure that the conditions on your table-specific Delete action are correctly set to limit visibility to admin users. Double-check that the condition gs.hasRole("admin") is correctly specified.