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. + ADD ACTION menu, add the Offline Database > Get Synchronization Log action according to the trigger event you want (Initial Actions, OnClick, OnBlur, etc.).

Get Synchronization Log Action Parameters

• User Name: Used to identify the user performing the synchronisation operations. In scenarios where multiple users are working on the same application, you can query which user synchronised which data.
• Status (Optional): Indicates the status of the synchronisation operations. Can be used to filter successful or failed synchronisations.
• Begin Date (Optional): Specifies the start date of the synchronisation operations. Used to query synchronisation operations performed from a specific date onwards.
• End Date (Optional): Defines the end date of the synchronisation operations. Together with Begin Date, it allows you to examine operations within a specific time range.

Scenario 1: Field Worker Enters Data While Offline

1. Data Entry: A field worker enters customer data into the system while offline, without an internet connection.
2. Synchronisation Success: When the internet connection is restored, the data is synchronised with the server. Thanks to the Get Synchronisation Log action, you can check whether this synchronisation was successful and which data was synchronised.

Scenario 2: User Checks for Failed Synchronisation

1. Synchronisation Error: A user notices that the data they entered while offline has not been synchronised properly with the server.
2. Error Log: Using the Get Synchronisation Log action, you can view which synchronisation failed and the error messages.
3. Error Resolution: The user can resolve the problem by reviewing the error messages and correcting the incorrect entries in the database.

• Time Range Tracking: If synchronisation processes are performed within a specific time frame, you can use the Begin Date and End Date parameters to review all processes within that time frame.
• User-Based Synchronisation Tracking: If your application has multiple users, you can track each user's synchronisation processes separately using the User Name parameter.

Technical Risks

• Synchronisation Errors: Regularly check error messages and codes to ensure that synchronisation errors are recorded correctly.
• Data Conflict: Add a post-synchronisation conflict management system to manage conflicts caused by changes made while offline.

The Get Synchronisation Log action allows you to track synchronisation operations between offline and online databases. You can analyse the success status of synchronisation operations, identify errors, and query the operation history by time intervals. This action can improve your application's user experience by enabling more efficient management of business processes.