What are the actions available for synchronization in OutSystems?

In OutSystems, both client and server actions are integral to the synchronization process. This is due to the platform's architecture, which facilitates a seamless flow of data between the client-side (the mobile application) and the server-side (where business logic and data reside).

Client actions are responsible for handling user interactions and can call server actions to either fetch or send data. When a client action initiates a synchronization process, it may involve invoking a server action that performs necessary operations like retrieving updated data from the server or saving user-generated data.

Server actions, on the other hand, are executed on the server and can be designed to facilitate bulk data processing, handle data integrity, and reduce the amount of data transferred over the network, which is essential for efficient synchronization.

Thus, the combination of both client and server actions enables a comprehensive synchronization strategy, allowing the application to maintain consistency and up-to-date information across the mobile client and the backend. This dual-action capability is what supports the dynamic nature of mobile applications built with OutSystems, empowering developers to create responsive and data-driven user experiences.