Server action to expose the read-onIy entities.

Best practice in OutSystems, by exposing an Entity as Read-only, and then create Server Actions to expose functionality to change the Entity data in consumer modules.

I saw the above statement in a Iearning materiaI.My doubt is

1)what is the purpose of setting an entity as read onIy if it can be edited.

Hi Remya,

please check this post, you will find your answer.

Regards,
Miguel

Hi Remya, 

The above post which Miguel has mentioned has all the answers, Also don't forget to read the below articles published by Justin on CRUD wrappers.

https://medium.com/@jmjames/outsystems-crud-wrapper-basics-e9a577a3e044

https://medium.com/@jmjames/outsystems-crud-wrapper-checklist-c7efb2ad9115

Thanks,

Sachin

Remya T wrote:

Best practice in OutSystems, by exposing an Entity as Read-only, and then create Server Actions to expose functionality to change the Entity data in consumer modules.

I saw the above statement in a Iearning materiaI.My doubt is

1)what is the purpose of setting an entity as read onIy if it can be edited.


Hi,


The main purpose of the Read-Only entity to block CRUD operation outside the module so no one can perform EDIT/DELETE/UPDATE operation directly from other modules. Like the centric solution to maintain Integrity.


For that always have the read-only entity and use server action to allow CRUD from other modules.