Problem: every time I create an entity I have to create wrapper methods to add business logic to the core module(_CS) actions. Manually I have to define the structure will be used, the way I will manage logical deleted registers, default values and exceptions that will be raised

Proposed solution: create a graphical interface that could generate metadata (the same approach OutSystems uses today to enable development) to create automatically the core actions. Microsoft has similar product I am suggesting, but when I try to add a CurrentDate() concept like in the OutSystems way in your model-driven-app, it doesn't work well. The final code generated, after modeling, could be linked to the application by a kind of connector where I could send all my data to the database

Benefits: save time to the developer and improve quality of code/data. Can add controlled layers of visibility to access data in the entities and the visual control will simplify the understanding and flexibility to adapt to other systems developed using OutSystems. I dare to say that it even could foster the use of domain architecture approach. In the future, the business modeler would standardize the way that core modules should be created to get the best quality of OutSystems development, avoiding multiple interpretations that occur nowadays when we need to define the strategy to create core service modules for complex systems.