3B Portals & Mobile App version 1.20 changelog
Revision as of 00:24, 9 June 2024 by Admin (talk | contribs) (Created page with "== New == * Portals loading speeds on desktop have been optimized, and in some cases, loading can be up to 100x faster due to a better caching mechanism. * Mobile apps loading times are up to 70x faster. * We are now using IndexedDB web api for cache management across the Portals application. == Changes == * We will cache pages content for 168 hours. This means, that once a user has accessed a portal, they will be served with the state of the portal for 168 hours afte...")
New
- Portals loading speeds on desktop have been optimized, and in some cases, loading can be up to 100x faster due to a better caching mechanism.
- Mobile apps loading times are up to 70x faster.
- We are now using IndexedDB web api for cache management across the Portals application.
Changes
- We will cache pages content for 168 hours. This means, that once a user has accessed a portal, they will be served with the state of the portal for 168 hours after which, the system will auto-bust the cache and load the latest version.
- We will cache page data (e.g. merge tags on a portal page) for up to 2 minutes.
- We will cache portal components for up to 168 hours.
- We will cache portal styles/scripts for up to 168 hours.
Deprecated
- We are deprecating the "Disable Caching" checkbox on the Page record.
Notes
Since we are introducing a new caching mechanism, portals/mobile apps should only be distributed once fully built. If changes are applied to a portal/mobile app, the changes will not propagate for up to 168 hours. A quick fix is to clear the user's browser cache.
Installation
https://login.salesforce.com/packaging/installPackage.apexp?p0=04tWS000000CLtV