1. Log in to the Kuika platform and open the project you are working on.
2. Go to the UI Design module and open the Properties panel on the right panel.

3. From the + ADD ACTION menu, add the Offline Database > Delete Offline DB action according to the trigger event you want (Initial Actions, OnClick, OnBlur, etc.).

• Scenario 1: Deleting Invalid Customer Records
  
  • While offline, a field worker updates customer information.
  • After updating some customer information, the user deletes old customer records that have become invalid from the local database with the Delete Offline DB action.
  • As a result, the employee cleans up the local database without losing any changes made while offline and focuses on the current data.
• Scenario 2: Offline Order Data Cleanup
  
  • While offline, a user enters orders, but some orders are cancelled.
  • With the Delete Offline DB action, cancelled orders are deleted from the local database.
  • As a result, the user only has valid order information and is freed from unnecessary data entries made while offline.

• Bulk Data Cleaning: You can delete multiple data sets at the same time. For example, you can use this action to delete old customer records and cancelled orders in bulk.
• Scheduled Cleaning: To perform regular cleaning of the local database, you can integrate the Delete Offline DB action with scheduled tasks.
• Pre-Synchronisation Cleanup: You can trigger the Delete Offline DB action before synchronisation to clean up unnecessary records before data is synchronised to the server.

Technical Risks

• Data Loss: To prevent accidentally losing data that was deleted while offline, you can back up the data or make the deletion process require confirmation.
• Data Synchronisation Errors: To prevent deletion operations performed while offline from causing incorrect data transfer during synchronisation, you can add data control mechanisms.

The Delete Offline DB action allows users to securely delete invalid or unnecessary data from the local database while offline. This action keeps the local database organised and focused on valid data. Especially in mobile applications, it prevents data loss during offline operations, enabling more efficient data management.