Client Data Store
A Client Data Store stores temporary application data that is available only while the current user is interacting with the application.
Unlike a Server Data Store, which stores persistent business information, a Client Data Store is intended for short-lived values that support the user interface and application state.
Typical uses
Section titled “Typical uses”Use a Client Data Store to store information that only needs to exist during the current application session.
Typical examples include:
- User selections.
- Search, filter, and sort criteria.
- Temporary values used across multiple screens.
- Wizard or multi-step form state.
- Cached values that improve the current user experience.
Client Data Store vs Server Data Store
Section titled “Client Data Store vs Server Data Store”| Client Data Store | Server Data Store |
|---|---|
| Stores temporary application data. | Stores persistent business data. |
| Available only during the current user session. | Available to authorised users and business processes. |
| Supports application and user interface state. | Stores application records and entity data. |
| Typically cleared when the session ends. | Retained until updated or deleted. |
Use a Client Data Store when data is temporary and only required by the current user. Use a Server Data Store when information must be retained as part of the application’s business data.
Best practices
Section titled “Best practices”- Store only temporary or session-specific information in a Client Data Store.
- Store business records in a Server Data Store.
- Avoid storing information that must be shared between users.
- Keep client-side data focused on supporting the current application session.