Guys, it is not perfect but I just made 2 components that may help you:
-> OML 2 XML: https://www.outsystems.com/forge/Component_Overview.aspx?ProjectId=10885
Extension that converts an OML Binary in an XML File. It is similar to what OutDoc already does, converting an OML to XML, but in this case it exports a lot more information. It was based on another component, OutGource. With the informations you can know exactly where some actions are used inside the OML, or specific properties of an entity or screen.
-> OML Elements (Under Development): https://www.outsystems.com/forge/Component_Overview.aspx?ProjectId=10886
It is Like an OML API that uses the extension OML2XML, it is at a very early stage yet with just some functionalities, like the possibility to get the Screen and Actions Tree.
There are also actions to help find the usages of each elements. Since the XML don’t follow a specific pattern for each element, I’m still trying to map the patterns for all types of elements and Modules in order to make a lot more functionalities. I decided to release it, even incomplete, because I think it may help someone with simpler requisites like myself.
The idea is that with that you people can have access to more detailed data of a Module, that is not available in Platform DB Metadata.
Examples would be:
-> Screens that have Anonymous or Registered roles marked which can be a security issue. Or any other role that you may want to track.
-> Specific details of an entity. If it is public.
-> Usages of an element inside a Module.
This way you can build your own complex reports to help manage your code. :)
Hope it helps.
If anyone have a specific use case that would like to do and don’t know how, let me know!
Cheers and Regards