- Form Session Protection: You can keep track of which step of a form the user is on even if they refresh the browser while filling out the form.
- Role/Permission Information Storage: After the user logs in, screen authorizations can be made dynamic by storing role information in the session.
- Multiple Tab Warning: Tab control can be performed with different session data specific to each tab.
Technical Risks and Controls
- Session Termination: Data is lost when the page tab is closed. If persistent data is required, Local Storage should be preferred.
- Key Collision: If the same key is overwritten with multiple data, the previous data is deleted. Unique naming should be ensured.
- JSON Formatting: If JSON is to be stored as Value, JSON.stringify() should be used when writing and JSON.parse() when reading.
- Browser Restrictions: Each browser has session storage limits (~5MB). Avoid storing excessive data.
- Storing Sensitive Data: Data such as user names and role information can be stored; however, sensitive information such as passwords or tokens should never be stored in plain text.
The Write To Session Storage action is ideal for developers who want to store temporary data for the duration of a session. It can be used effectively in many scenarios, such as personalizing the user experience, saving temporary selections, and managing form processes. With its clean and controlled data storage structure, it offers a simple yet powerful solution for Kuika projects.
