- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā02-24-2023 07:52 AM
Hi,
I have some little trouble with table and extend table. In my case, to describe it easily i have table A and table Task. Table A extends table Task. But there is some trouble, that is whenever a user access to table A is very slow and i've noticed that I have created some UI Actions in table Task and it runs at table A when i open a record. Table A keeps triggering the UI Actions and results of those query actions are null. Do tables when they extend, they get all UI Actions and Business Rule (BR) and Client Script (CS) from the extensible table ? If so, how can i remove those unuse BR, CS, UI Actions get from table A.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā02-25-2023 11:05 PM - edited ā02-26-2023 12:32 AM
By default, Business Rule and UI Actions will run on all extended tables. However, if you were to put a condition in that states "current.getTableName() == "task", this would then only run on Task and not the extended tables.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā02-25-2023 11:05 PM - edited ā02-26-2023 12:32 AM
By default, Business Rule and UI Actions will run on all extended tables. However, if you were to put a condition in that states "current.getTableName() == "task", this would then only run on Task and not the extended tables.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā02-26-2023 12:03 AM
Thanks for the answer Aavi.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā02-26-2023 12:12 AM
Actually by default, OOB Client Script do not run on extending tables.
When one creates a new Client Script by default option "Inherit" is not checked.
And that is how one prevents running Client Script on extending table.
As for UI Actions, those should not execute anything when a form loads.
Are you sure you mean UI Actions (not UI Policies)?
If you de mean UI Actions, the easy way to prevent those showing up on an extending table is by creating a copy for the extending table (Table A) and setting a condition for it that hides it permanently - so by overriding the base UI Action.