Hi All,
I am referring the side reference post from the below link,
Why can't we have side reference in End user module | OutSystems
So will it be applicable for single application and multiple application that side reference should not be there to avoid custers?
so how about core and library or core and core side reference,
Thanks
Hi Ujwala,
Core and Library modules may have side references but they must not be cyclic.
For further clarification can follow this URL.
End user application and modules should not have side references.
regards
To improve Vikas' answer:
You shouldn't create cyclic references, but what you call side references can probably be seen as down references if you create middle layers (don't see Core or library as single layers, but as layers of layers).
Now, regarding End User modules, you can have side references to pages. One site can link another. More than that, is not advised as it can easily become a cyclic reference.
Hi Nuno,
Thank you,
That means side reference can be done but to avoid clusters within the same application and in different application with the impact of deployment to be avoided.
So similar applies for core and library as well ?
Like I said, you can see neither Core as a single layer. They will have multiple layers inside. A normal project has maybe 3 layers inside Core. Complex projects can have more. And I always saw Library as a dual layer (IS modules and CS modules).
The first rule is: A Software Architect should be doing that.
Because Developers can get "creative" in the process.
Better if you read the official documentation.
This is a summary, but the More information links at the bottom are very important.
https://success.outsystems.com/Documentation/Best_Practices/Architecture/Designing_the_Architecture_of_Your_OutSystems_Applications/Application_composition/Applying_the_Architecture_Canvas_to_applications