I have a table like this for example
User: username, password, name, age, phone is CS Module
My application architecture include these module:
CommonUI, CSBLUI
=> I only want to show some not private info like: name, phone
So I'm thinking about create a structure for only those attribute to show on UI, but I don't know where to store it. In CommonUI? CS? BL?
In your case, the best approach would be to store the structure in a module where it best fits its responsibility. Based on the standard architecture of OutSystems applications and best practices:
Store the structure in the CS (Core Services) module: Since the structure is tied to the entity in the Core Services module (User entity in the CS module), it makes sense to define the structure here. This ensures that all related data and structures are stored in the same logical module. CS is the module responsible for encapsulating the core business entities and their associated logic, such as structures and logic for exposing or transforming data.
CS
User
Expose the structure to the BL (Business Logic) or CommonUI module: Once you've defined the structure in the CS module, you can expose it as a public structure (via the Public property). This will allow it to be used in other modules, such as BL or UI, to fetch and display only the necessary data (e.g., name and phone).
BL
CommonUI
Public
UI
name
phone
Why not CommonUI? The CommonUI module is typically focused on shared visual components (e.g., widgets, themes) and not core data structures. It’s better to keep such structures closer to where the actual data is stored and managed, which in this case is the CS module.
To summarize:
This follows the principle of keeping data and logic as close as possible to its source while maintaining a clear separation of concerns Module count and module bifarcation according to best practices.
Hello.
To clarify the answer, think on the structure as the sharable version of the entity. Instead of making the entity public, you make the equivalent structure public. So they stay on the same module.
Makes no sense to place it in modules above as they consume the CS. A structure above CS that CS needs, would create a circular dependence.
Ok I get the idea, put the structure inside the CS then expose structure outside, noice
Why you create a users entity with password? Will it be used to login to an outsystems app? In that case you should use the built in User identity provider of outsystems.