Skip to main content





Implement Application Logic

In OutSystems, the logic of your applications is implemented through Actions. While developing your applications, you can create your own custom actions and use the actions OutSystems provides you:

  • Custom actions: The actions that you create to define your business rules, fetch data from the database, run integrations with external systems, among other operations.

  • OutSystems built-in actions: Actions that are defined by the platform and cannot be modified or inspected. You can use them in your action flows, such as Entity Actions, System Actions, or Role Actions.

  • Actions that handle System Events: Actions that run at specific moments of the application life cycle, such as when a web session starts or a mobile app resumes. You are able to design the flow of these actions according to your business rules.

Actions in Mobile and Web Applications

The architecture of mobile and web applications is different and that affects the type of actions available and how they are used in both architectures. While in web applications all the logic runs on the server, in mobile apps you have logic that runs on the server and logic that runs on the client — the user device.

When developing the logic of your mobile app you must take into account that every time your client side logic needs to execute server side logic, the user device will make a request to the server and wait for the server response. This communication requires that the user device is online (connected to the internet).

Check the actions that you can create and use in web applications or in mobile apps.

Articles in this Section

  • Was this article helpful?