Cache

In the portal, every component used in the configuration has a cache setting. The cache setting is designed for the Designer to optimize data caching or refreshing for the best end-user experience and performance.

Data is cached in IndexedDB.

The portal's caching approach can be divided into three sections: Default setting, Configuration options, and End-user options.

Default setting

Data is fetched from the component the first time it is encountered. After that, cached data is used.

• Expiration time: Data expires at the start of a new calendar day.

• Sign out: Cache is cleared upon signing out.

Default details

• Page (all portlets on a page): Data is cached when entering the page for the first time.

  • Sign in and enter page 1: Data is fetched from the data sources and stored in the cache.

  • Move to page 2: Data is fetched from the data sources and stored in the cache.

  • Go back to page 1: Data is retrieved from the cache.

• Pre-fetch filter: Data is cached the first time the filter is applied.

  • Pre-fetch 1: Data is fetched and stored in the cache.

  • Pre-fetch 2: Data is fetched and stored in the cache.

  • Pre-fetch 1 again: Data is retrieved from the cache.

• Post-fetch filter: The filter is applied after data has already been fetched to the portlet.

• Cache versioning: Data is cached with a component version, so a new component version will clear the cache.

• DEV: In the development environment, the latest committed version of a component is always used, and the cache is unaffected by changes to the component. The developer must manually refresh.

• List of Values (LoV): Since a LoV is based on a component, its data is treated the same way as data from data source components.

Configuration options

All data sources and Lists of Values have an Update cache setting, where the developer can choose how often the cache is updated.

• Daily: Data expires at the start of a new calendar day. This is the default setting when creating a new portlet or adding a new List of Values.

• Live: Data is always refreshed.

  • Exceptions:

    • Working within a portlet (e.g., sorting, querying, or grouping) will not refresh the data.

    • Applying a post filter will not refresh the data.

• Custom: Data remains valid for a specified number of minutes (X minutes).

End-user options

• Refresh Button on Portlet: Clears all cached data and refreshes the data.

  • Any filters applied to the portlet will remain after the refresh.

  • The List of Values cache is cleared upon portlet refresh (table and record).

• Clear Page: Available under Profile; this option clears the cache and refreshes the active page.

• Clear All: Available under Profile; this option clears all cache and refreshes the active page.