Session Storage Manager — Reference

Keep JSON-compatible browser state for the current tab’s page session.

Before you begin

• An App Connect page with the State Management component included. Use a dedicated test key for experiments.

Session Storage Manager

Keep JSON-compatible browser state for the current tab’s page session.

Properties, data and actions

Part	Meaning
ID	The component name, for example sessionState.
Define Session Storage Items	Declares names/types for editor pickers, not stored values.
Values	Use sessionState.data.name for the current value, such as sessionState.data.wappler_docs_preference.
Set: Name / Value	Stores the JSON representation under a dmxState- key in sessionStorage. A reload can read it again in the same page session.
Data	Schema-driven controls for an object item build the value supplied to Set.
Remove	Removes one named session-storage item.
Remove All	Removes the dmxState- entries in this tab/origin’s sessionStorage, including entries used by other manager instances with that prefix. It leaves unrelated keys alone.

Worked example

Use sessionState.set(‘wappler_docs_preference’, ‘compact’) and display sessionState.data.wappler_docs_preference. Reload in the same tab to confirm it remains, then remove the named key. Test a fresh page session separately instead of assuming it shares the same state.

Lifetime and boundaries

This is client-side sessionStorage, not a Server Connect server session or Security Provider login. Browser tab/session restoration can affect lifetime, so explicitly remove completed drafts rather than using tab closure as a security or expiry mechanism.

Choose the right storage

Compare URL, cookie, session and local state before choosing where application data belongs. Browser state never replaces server-side access checks.

Check your result

You can use the correct data path, configure a value and verify the storage/removal scope.