How to override OOB UI Action?

Frank · ‎08-26-2014

I need to hide the Save and Stay UI Action on the incident form unless the user has a specific role, but I don't want to modify the action directly because it's an OOB function. I've see examples where you can override global UI Actions by adding a UI Action to the specific table, but in this case, the action already is on the incident table. Anyone have any suggestions on how to accomplish this? Could it be done with security policies?

Thanks,

Frank

Frank · ‎08-27-2014

I believe I have a solution. If the UI Action has current.canWrite() in the condition, then creating a security rule where the name is the name of the table and the field names is set to none, not * and then adding the appropriate role seems to work. Marking this as resolved.

Thanks everyone,

Frank

View solution in original post

Brad Tilton · ‎08-26-2014

You could just add another action on the incident table with the same action name, but make the order lower so that it fires first.

Jake Gillespie · ‎08-27-2014

Brad is correct. I recommend opening the original UI action record and doing an "insert and stay". Then, adjust the values as required e.g change the table to specifically reference Incident, add the role condition to the conditions field using gs.hasRole("role_name") etc. Finally check that the action name is the same.

Frank · ‎08-27-2014

Jake,

Thanks. See my response to Brad.

Frank

Frank · ‎08-27-2014

Hi Brad,

I gave it a try, same name, same action name and a lower order and ended up with two Save and Stay buttons. Will the override only work if the original UI Action is on the parent table?

Thanks,

Frank