1.) There are several approaches to override a parent table UI Action:
a) Hide the Parent Table UI Action and Create a New One
- Add a condition in the parent table’s 'Condition' field:
current.getRecordClassName() != '<table_name>'
Here, <table_name> refers to the extended table.
b) Use the 'Overrides' Field
- Leverage the built-in 'Overrides' field to replace the parent UI Action functionality.
c) Recommended Approach – Use the Same Action Name
- Create a new UI Action on the extended table using the same Action name as the parent. This is the most effective and clean way to override a parent UI Action.
2.) Use Unique Action Names in Ui Actions
- Ensure that your action names are uniquely named or you run the risk of another UI Action's script executing if those actions are on the same table
3.) Use 'Requires role' list on UI Action form
- Its recommended to use the "Requires Role" when you want to limit, by role, who can use the UI Action as that doesn't require the use of scripting
4.) Visibility by View in UI Actions:
- Utilize the "UI Action Visibility" related list as the preferred way to define specific form views for when the UI Action should be visible
