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, select the desired trigger event (Initial Actions, OnClick, OnBlur, etc.) and select Offline Database → Download Offline DB.

Parameters in the Download Offline DB Action

• ID: Specifies the ID of the database or data set to be downloaded. Used to define which database or table to download.

Scenario 1: Viewing Customer Information While Offline

1. Data Retrieval: A field worker uses the Fetch Offline DB action to access customer information without an internet connection.
2. Data Access: The worker can view customer information in the local database, but since there is no internet connection, the data is limited to the latest information stored on the device.
3. Result: The employee can interact with and process data while offline.

Scenario 2: Viewing Order Information While Offline

1. Data Retrieval: While offline, a user retrieves old order information from the local database using the Fetch Offline DB action.
2. Data Viewing: Since there is no internet connection, the user can only see the data stored in the local database.
3. Result: The user can view old order information while offline and perform operations on this data as needed.

• Multiple Data Set Synchronisation: You can download and synchronise multiple databases or tables in offline mode. For example, you can download and synchronise customer data and order details at the same time.
• Scheduled Synchronisation: You can ensure that data is automatically synchronised with the server at specific intervals. This allows you to ensure that data is updated regularly.
• Data Conflict Management: You can add data control mechanisms to manage conflicts caused by changes made while offline. For example, if multiple users make changes to the same data, an approval process can be initiated in case of a conflict.

Technical Risks

• Data Conflicts:To prevent conflicts between changes made while offline and data on the server, add conflict management during synchronisation. When conflicts are detected, a notification can be sent to the user.
• Data Loss:To prevent changes made in offline mode from being lost, ensure that sufficient security measures are in place in the local database. For example, you can enable automatic data backup.
• Data Synchronisation Issues: Carefully configure data transfer processes to prevent data loss during synchronisation. You can also add error checking mechanisms during the synchronisation process.

Download Offline DB action allows users to use your application efficiently even when they don't have an internet connection. With this action, database data can be downloaded to the device's local database, and changes made while offline can be synchronised with the server when the internet connection is restored. The ability to work offline improves the user experience and allows you to continue your business processes without interruption.