The suggested fix is "Identify the independent UI flows, with no destinations among themselves, and separate them in multiple Modules.", however I don't have independent UI Flows. All of them are connected somehow.
Am I missing something? There is a way to fix that?
Hi @Gabriel Melo
Refer to this link: https://success.outsystems.com/documentation/11/monitoring_and_troubleshooting_apps/manage_technical_debt/code_analysis_patterns/
which states the following:
This means that your module has too many end user screens. You might have to revisit your application architecture and try to separate some screens into different smaller modules that can have independent lifecycles and separating the common modules as well based on the architecture best practices.
Thanks.Regards,Bryan
This is Tech debt needs to handle with respect to context.
If all screens catering to one aspect or one domain (example p&l account) then it should stay to gather. Then close tech debt by 'False Positive'
If your screens are catering to different domain / aspect (p&l account, general ledger etc) then
1- Separate screens in multiple flows.
2 - move blocks to separate modules. (p&lAccount_cw, GeneralLedget_cw)