1. Define the Action in UI Design

• Log in to the Kuika platform.
• Select the project you want to work on from the Apps screen.
• Go to the UI Design module.
• Open the Properties panel on the right side.
• Select the element you want to define the action for (for example, a “Clear Form” button).

• ADD ACTION menu, select the Local Storage → Delete From Session Storage option according to the trigger event you want (Initial Actions, OnClick, OnBlur, etc.).

2. Configuring Action Parameters

• Key (String, required):
  
  • Specifies the key name of the session data to be deleted.
  • Example: “formStep1Data”, “tempUserSelection”, etc.

Dynamic Definition with Data Sources:

• Fixed: The key name can be defined as fixed.
• Symbol Picker: Page inputs, component data, method results, or current context data can be used.

A user cancels a multi-step form while filling it out. In this case, the form data temporarily stored in Session Storage during the session must be deleted.

Application Flow

• Go to the UI Design module.
• Drag and drop the following element from the Elements panel:

• Button: “Clear Form” button

Action Flow

• When the button is clicked, the Delete From Session Storage action is executed.
  
  • Key: “draftFormData”
  • (Optional) The form is reset or the user is redirected to the main screen.

• Clear Multiple Data: You can define separate Delete From Session Storage actions to delete multiple session data.
• Conditional Deletion: For example, if the user has checked a checkbox, it can be used with the If action to perform the deletion.
• Step-by-Step Forms: In multi-step forms, temporary data from previous steps can be deleted as each step is completed.
• Use with Action Chain: Screen clearing, form reset, or navigation actions can be defined as an action chain after Session Storage is deleted.

Technical Risks and Precautions

• Invalid Key Usage: If the specified key value does not exist in session storage, the deletion process may be ineffective. Therefore, make sure that the key is spelled correctly and exists at that moment.
• Data Loss Risk: In cases where session data may still be in use, the deletion process may negatively affect the user experience. Make sure that the data is not being used before deleting it.
• Platform Incompatibility: The action is only valid on browser-based platforms. Availability should be checked on native mobile applications.
• Conflicting Key Names: Using the same key name in different components can cause unexpected data deletion. Unique and meaningful key names should be preferred.
• Access to Empty Data After Deletion: If an attempt is made to access data deleted from the session in the next action, the application may return an error. The action sequence must be carefully configured.
• Browser-Based Limits: Session Storage has different limits in each browser. Large amounts of data should not be stored, and efficiency should be ensured with the deletion process.

Delete From Session Storage enables controlled cleanup of temporary data used during the session in Kuika applications. It plays a critical role in form steps, transaction tracking, and temporary selection management. It is an ideal solution for secure and user-friendly data management processes.