applicationlandscape2markdown
Reactive icon

ApplicationLandscape2Markdown

version 1.0.0 (Compatible with OutSystems 11)
Uploaded
 on 16 Sep (21 hours ago)
 by 
0.0
 (0 ratings)
applicationlandscape2markdown

ApplicationLandscape2Markdown

Documentation
1.0.0

Release Notes 

Version 1.0.0 

  • Initial release. 
  • Features included: 
  • Multi-application export 
  • Markdown generation 
  • Architecture classification 
  • Entity ownership discovery 
  • Entity dependency analysis 
  • Cross-application dependency discovery 
  • REST integration inventory 
  • SOAP integration inventory 
  • Mermaid dependency diagrams 
  • Mermaid integration diagrams 
  • AI-ready application landscape documentation


Benefits 

  • Architecture visibility 
  • Faster documentation generation 
  • Landscape discovery 
  • Dependency mapping 
  • Integration inventory 
  • AI-ready output Mermaid diagram generation 
  • Multi-application analysis 
  • Metamodel-driven documentation


Generated Information 

The current version includes: 

  • Applications 
    • Application metadata 
    • Application composition 
    • Module inventory 
  • Modules 
    • Module metadata 
    • Suggested architecture layer 
  • Entities 
    • Entity ownership 
    • Entity descriptions 
    • Entity classifications 
  • Dependencies 
    • Module-to-module dependencies 
    • Cross-application dependencies 
    • Referenced entities Integrations 
    • Consumed REST integrations 
    • Consumed SOAP integrations 
    • Endpoint inventory 
  • Diagrams 
    • Entity dependency diagrams 
    • Integration diagrams


Limitations

Current dependency discovery is based on entity references. 

The current version does not include dependencies that exist exclusively through: 

  • Public Actions 
  • Structures 
  • UI Blocks 
  • Themes 
  • Extensions 
  • Runtime-only interactions


The current integration inventory includes: 

  • Consumed REST services 
  • Consumed SOAP services 


The current version does not include: 

  • Exposed REST APIs 
  • Exposed SOAP services 
  • Individual REST operations 
  • Individual SOAP methods 


Architecture classifications are inferred from naming conventions and should be validated by solution architects when required.