Scaffolding can be extended to consider layer of modules. (_CS, _IS)
130
Views
3
Comments
New
Service Studio

I need to create default summary and detail screen for an entity by dragging the entity to mainflow canvas.

Current capacity is not considering the layer of components. (UI module is directly accessing the entity from _CS layer)

I would like to have a scaffold/shortcut feature to bring DTO object and method to fetch data from _CS module entity to _Web (UI) layer. So that the Entity will not be exposed to UI layer.

Note: This manual conversion takes more time (80% of time) in the current capacity to build a summary and detail screens.

Changed the category to
Service Studio

Hi Saravanan,

There's a workaround for your use case, which is creating the scaffolded screens (typically, the list and the detail) while the entity is not read-only. That gives you almost everything you need to build those screens.

Then, you can set the entity as read-only, refresh the UI module's dependencies, and fix the errors by replacing the Entity actions by their matching CRUD actions.

Hope it helps.


Regards.

Hi Recardo, 

Thank you for your suggestion.

Exactly the same way I am managing to do. Still My case is to reach the UI from DB layer, I need to imlement the read or write methods in all the layers/modules with shared DTO structure. 

"fix the errors by replacing the Entity actions by their matching CRUD actions " - This takes  the 70 to 80% of the total tie to build a basic screen.

Regards,

Saravanan Nagooran