The Push Offline DB To Server action is used to synchronise offline transactions with the server when the internet connection is restored. This action allows you to send transactions performed offline by users to the server without losing any data. When the connection is restored, the data in the local database is automatically synchronised. This allows you to maintain data integrity and continuity in your application and provide an uninterrupted user experience.

Technical Features

Offline Data Synchronisation: Used to transfer database changes made while offline to the server.
Synchronisation with Local Database: When an internet connection is available, data in the local database is automatically synchronised with the server.
Seamless User Experience: Users do not lose any of their offline activity, and this activity is sent to the server when the connection is restored.
Web and Mobile Compatibility: The Push Offline DB To Server action is supported in both web and mobile applications.

Push Offline DB To Server Action Application Steps

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

3. Select the button and add the Offline Database > Push Offline Db To Server action from the + ADD ACTION menu according to the trigger event you want (Initial Actions, OnClick, OnBlur, etc.).

Usage Scenario: Offline Data Synchronisation

Scenario 1: Field Worker Updates Customer Information While Offline
- While offline, a field worker updates customer information.
- When the internet connection is restored, the Push Offline DB To Server action is triggered and the customer information in the local database is sent to the server.
- As a result, the worker synchronises all changes made while offline to the central database when the connection is restored, without losing any data.
Scenario 2: Offline Order Update
- A user creates an order without an internet connection.
- When the user reconnects, the order information is synchronised with the server using the Push Offline DB To Server action.
- As a result, the user transfers the changes made while offline to the server without losing them, and the system is updated.

Push Offline DB To Server Action Advanced Customisations

Scheduled Synchronisation: You can enable automatic synchronisation of data at specified intervals. This ensures that data is updated regularly.
Data Conflict Management: You can add data control mechanisms during synchronisation to manage conflicts with changes made while offline.
Multiple Data Set Synchronisation: You can synchronise multiple databases or tables at the same time. This ensures that data is kept up to date.

Technical Risks

Data Conflicts: Add conflict management to prevent conflicts between changes made offline and data on the server.
Data Loss: To prevent changes made in offline mode from being lost, ensure that adequate security measures are in place in the local database.
Data Synchronisation Issues: Carefully configure data transfer processes to prevent data loss during synchronisation.

The Push Offline DB To Server action allows users to synchronise all database changes made in offline mode to the server. When the internet connection is restored, all data in the local database is transferred to the server without being lost. This action is critical for users working offline, especially in mobile applications, and ensures an uninterrupted user experience.