FREE OutSystems Workshops - Build an OutSystems App in 1 hour | ENROLL NOW

Tech Bites - Why you shouldn't be using CRUD actions everywhere

< Back to Blog

One common architecture issue when people start learning OutSystems is using entities' CRUD actions in multiple places.

Using our Order Management application as an example, we have a form to create, update and check the status of customers ' orders.

In this case, the Approve and Submit buttons in the save action do not invoke the CRUD action, as you can see.

We use a "server action" as a wrapper between the client-side and the database.

That action, implemented on a core module, makes all the validations needed before committing changes to the database.

Every one of those validations aborts the create or update action if the data is invalid.

For example: trying to approve or submit an amount lower than zero.

This way, when handling orders, we have a server action, which only accepts valid input data!

There are many things to grasp about software development architecture and, in particular, OutSystems architecture layers. Join us in one of our programs to learn more about it and other advanced topics.

Turn Up Academy

Apply to our Turn Up Boot Camp


Latest Articles

Tech Bites - How to use Screen templates

How to use Screen templates

Did you know that the OutSystems Platform has tens of screen templates to help you quickly put together your apps? Let me show you how you can use them.

Tech Bites
Tech Bites - Set timers to delete records

Set timers to delete records

In this tech bite, we will demonstrate how to set timers to delete records and use an online store as an example.

Tech Bites
Tech Bites - How to import data from an excel file

How to import data from an excel file

In this video, we’ll show you how to upload and store data from an excel file.

Tech Bites