Local Storage

Local storage is a feature used by the BPC to store data directly on the user’s device within the browser. This feature allows certain information to be retained across sessions, ensuring a consistent user experience.

Usage

Local storage is used by various modules. Below is an overview of the main uses.

ExtJS Framework

ExtJS uses local storage to persist component states and user settings. This allows preferences such as filter settings, table sorting, or layout configurations to be retained even after the browser session ends. When the application is reopened, this stored information is automatically loaded to ensure a personalized and efficient user experience.

Core

  • Module version of the FE-Core

  • The last language selected

  • Activation/deactivation and value of the global date filter (see Global Date Range Filter

  • The read status (read/unread) of BPC notifications (see Notifications)

Monitor

Dashboard

  • Configurations such as the dimensions of individual widgets

  • Modifications to the configuration of individual widgets that have not yet been saved to the dashboard

The dashboard offers the option to reset the local cache (see resetuserstate under Quick Functions). This function resets the local storage of the selected dashboard instance, thereby removing all changes that the user has not yet saved. This allows you to restore the dashboard to its default state, as defined in the BPC settings.

Resetting Local Storage

You can reset the local storage using the action deleteLocalStorage.

If, while loading the BPC, it is detected that the content in local storage was written by a different BPC version, the local storage is reset for compatibility reasons.

This happens, for example, during a BPC update.

Advanced users can also inspect and analyze local storage in the browser’s developer tools under the “Application” tab. This section provides detailed insight into the stored data and allows for the selective removal of individual entries as needed.


Keywords: