Cache for Service Actions
Application Type


I am developing a mobile application. 

I created Business Logic as a Service type application, which interacts with Rest API and provides service action for the frontend. In mobile UI I am using the service actions from the Business Logic module.

Is there any option for cache in Service action similar to Server action?

Or any hint on how we can enable caching for Service actions?




Why you use service action (which is implemented as a rest endpoint by OutSystems) to expose a rest method? That seems to be a bad coding pattern, having to network calls with the latency that comes with those calls.

Maybe you should consider a server action on which cache in minutes option is available.

Hello Daniel,

Thanks for your suggestion. 

Let me describe in brief our workflow so that I can get more information about the restructuring of the application architect if needed.

In our case - This mobile application acts as a portal for different applications in our organization.

Not all the functions of those applications will be available in the mobile app, the functions will be limited like approvals, initiating requests, etc... and all other workflows will be executed and carried forward within the main app.

As the mobile app is communicating with multiple applications, we had designed to have a common business layer that will interact with other applications through rest API and provide the result through service action for loosely coupled. This business logic layer is used to trigger other actions such as notifications and logging the transactions.

That's the reason we chose service action instead of server action.

@Daniël Kuhlmann Would it help if he encapsulated the service action inside a server action and put the caching on that server action?

Hello Stefano Valente,

I liked your suggestion, but I am not clear about the impact. If someone can provide more information it will be highly appreciated.

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.