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.
When including forms in applications, developers often wonder if they need to re-validate data on the server side after having checked it on the client. Why go to the trouble of checking the data twice?
When developing an OutSystems reactive web app, you would expect to display data quickly, but it doesn't always happen. Do you know why? We'll explore the reasons and how to tackle them.
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.