Hello everyone,
I’ve noticed a discrepancy in the Application Objects (AOs) count for the Discovery O11 component (latest version 6.0.3). On the OutSystems Forge, the component shows 103 AOs, but when I check after installing it in my environment, it reports 112 AOs.
Has anyone else experienced this difference? Could you please check in your environments and share your results? I’m trying to understand if this is an isolated case or a common behavior.
Thank you for your help!
Hey everyone,
the issue has been fixed and the Discovery Component should be showing the correct number of AO's.
We are also recalculating the AOs of other Forge O11 assets that were showing the wrong number and they should be correct by end of tomorrow.
Thank you for reporting this issue.
Best,
Ana Vaz
Hello @Ana Vaz ,
Thank you very much for your response.
Do you know if this incorrect count also affects the statistics shown in the customer portal? (Menu: Platform → Analytics / URL: https://www.outsystems.com/csportal/Analytics)
Hey @Anderson Davi,
This error was only affecting Forge.
Customer Portal's Analytics uses directly the AO information of your infrastucture, however, if you see there any issues or number that don't match, please report it.
Hi @Anderson Davi ,we can view AO Count in two ways
1-Service center - Reads live data from platform.Path(Administration-->Licensing --> Application Objects)
2-DiscoveryTool(ForgeComponent) - Use a snapshot taken at time of analysisIn your case if the development happened after Discovery scan it will differ.Thanks,Ananth
Hi Anderson,
Yes, that behavior is expected.
The AO count shown in Service Center reflects the live state of the platform, while Discovery relies on a snapshot taken at the time of analysis. If any development or structural changes occurred after the Discovery scan, the numbers will naturally diverge.
In practice, the Service Center should always be considered the source of truth for licensing and current AO counts. Discovery is intended for assessment and estimation purposes, not for real-time validation.
Best, Miguel
@Anderson Davi ,
yes, just installed it in my PE, and if I add them up, I see 112, just like you. I'll ask Outsystems how the counting is done, both in Forge and Service Center and if they see a reason why these would be different. If data on Forge is wrong, that takes away the value of showing it.
@P Anantha Raman and @Miguel Verdasca : please carefully read what is asked before answering. He is talking about the difference between Forge and Service Center for the forge component Discovery, has nothing to do with the functionality itself of Discovery.
Dorine
Hi @Dorine Boudry ,
Perfect, thanks for validating it in yout PE as well.
I'll wait for OutSystems feedback on how the counting is done in both Forge and Service Center, and whether there's any justification for the difference in the numbers. If the data in Forge is incorrect, it really does undetermine the value of the information presented.
Any updates on this topic ?
Hi @Anderson Davi ,
no, had no reply from OutSystems after they said they would look into it.
I'll ask again.
Forge shows only the AOs that are directly implemented in the component at design time.Service Center shows the actual runtime AOs, including generated, dependency, and system AOs created during publish.So the difference in count is expected and indicates runtime behavior, not a defect.
Thanks ,
Sudha Narayanan
@Sudha Narayanan ,
can you explain what those 'generated, dependency and systems AO's' are that you say are getting added ?
Thank you so much, @Dorine Boudry and @Ana Vaz , for your support on this matter.