Hi,
as I'm doing my analysis on Discovery, I came across some modules with warnings. When clicked, those warnings state something as shown below:
I don't really understand the meaning of "trespassed elements" and I have found nothing related to it anywhere. Can someone help me understand the meaning?
Thanks.
Hello Tânia,
Thanks for your question.
The new Trespassing feature is related to Domains. It allows the export of the visual findings in the Domains view (if activated) to an excel file.
You can find more details on the release notes of the component.
Any further question please let me know.
Best regards,
ROM
@Ricardo Marques could you please share the release notes of the component?
Hello, i have same query, can someone please knows what is trespassed element, what does mean?
Hi Menna and Soni.
Discovery allows you to validate the architecture from 3 levels of abstraction - module level, application level and domain level.
what is a domain ? Think of a domain as a way to arrange and put a boundary around a set of related applications ,like, the applications that support a given Line of business (lob) or department.
Now lets suppose we have two domains - Human Resources (HR) and Finance (FI). Lets also suppose there are a couple of applications to suport HR and a couple of other application to support FI.
The HR and FI departments they don't live "alone" they collaborate, sometimes HR needs some approval from FI and in some scenarios FI might require some additional information from HR.
This collaboration across the organization is reflected in the application, in fact, HR and FI , they also need to communicate, but they way this is materialized in the code is very important in order to keep HR and FI independent
What I mean is that , this collaboration should be implemented via weak references (like service actions) to make sure HR and FI are kept independent.
So HR and FI are your domains, there is a boundary around the applications that support each one of the departments (the domain) and every time you cross the domain boundary to collaborate you should use a loosely coupled option.
If you don't , them your are in fact coupling HR and FI toghether and you are trespassing the boundaries the domains in the wrong.
You can model your domains in Discovery , map applications to domains and them have Discovery to automatically show you when this tressapassing is done.
hope it helps to clarity.
Check if this changes in agregates filter can help you
https://www.outsystems.com/forums/discussion/92741/discovery-way-too-many-false-positives-when-it-comes-to-trespassers-at-applicat/