Optimizing UI and Client-side Performance
Load Data Only for the Most Common Path
When your user's journey contains multiple branching paths, start by loading only the records needed for the most common path. Bring in any extra data only after the user chooses a different branch.
-
Identify the main path and corner cases of your user's journey, map the branches of each sub-journey, and then determine the data required for the start of the user's journey.
Defer the loading of other data until your user's journey requires you to load it to shorten initial load times and to focus resources on the most common use cases.
Source and Default Fields with SuiteBuilder
Avoid using user event scripts and client scripts for simple sourcing or defaulting logic. Instead, you can rely on SuiteBuilder's Field Sourcing and Default Value options to populate custom fields.
SuiteBuilder runs internally with zero script overhead and may improve your scripts' performance.
Delegate Field Visibility
When you build a localization SuiteApp, do not hard-code country-specific field visibility in your own user event scripts or client scripts. Instead, delegate that job to the Localization Assistant SuiteApp's Localization Record Context Field Management (LRCFM) component. The LRCFM component sets field visibility before a page loads, avoiding the extra client script overhead that may run unnecessarily to show or hide fields based on the country or region.
The Localization Assistant runs at load time, so you do not need to implement separate client script workarounds to set any initial visibility or to track country context changes after a user edits a form.
After installing the Localization Assistant for your SuiteApp:
-
Configure the Localization Record Context Field Management component for each record type that contains localized fields.
-
Remove any custom scripts that only show or field fields based on country context.