The component runs on OutSystems 11 (Reactive Web) and needs the dependencies below, all published in the environment before you install it.
Dependency
Why it is needed
(System)
Application, App_Definition_Module, Module, Espace, Entity, Espace_Entity, Web_Reference and Web_Service
ExtendedMetamodel (Forge)
REST_Web_Reference (consumed REST) and REST_Expose (exposed REST)
Sanitization
BuildSafe_InClauseIntegerList, to build the application filter safely
OutSystemsUI
Layout, DropdownSearch, CardSectioned and BlankSlate
Users
Template login and logout actions
https://<your-environment>/ApplicationLandscape2Markdown/
Pick the scope, choose the sections and generate: the document appears below the filters in seconds.
.md
For large landscapes, start with a few applications: the export runs as one SQL query with a 60-second timeout.
The export always holds the header, overview, catalogues and context; the rest follows the options you tick.
Section
What it holds
Shown when
Header
Generation date (server time), scope and number of applications
Always
Overview
Counts of applications, modules, dependencies, findings, entities and integrations
Always (rows per ticked option)
Application Catalogue
Each application with its ID, description and modules with their layer
Suggested Architecture Classification
Modules grouped by End User, Core, Foundation, Platform and Unclassified
Architecture Findings
Upward references, side references between End User modules, direct cycles
Dependencies and findings
Module Dependency Diagram
Mermaid flowchart grouped by layer; each arrow shows the number of referenced entities
Dependencies and findings + Mermaid diagrams
Integration Diagram
Mermaid flowchart of the REST and SOAP services each module consumes or exposes
Integrations + Mermaid diagrams
Module Catalogue
Per module: application, module kind, layer, Depends On, Used By, Owned Entities, Integrations
Always (subsections per option)
Cross-Application Dependencies
Every dependency between modules of different applications
Integration Landscape
All integrations grouped by direction and technology, with URLs
Integrations
Architecture Context and Known Limitations
How to read the document and what it does not cover
Descriptions of applications and entities are added only when Descriptions is ticked.
Layers are inferred from the module name, checked in the order below; the first rule that matches wins.
Order
Rule
Layer
1
Platform system module (for example ServiceCenter)
Platform (not validated)
2
Name ends in _FS, _IS, _TH, _Theme, _Pat, _Lib, _Core, _Drv or _Ext
_FS
_IS
_TH
_Theme
_Pat
_Lib
_Core
_Drv
_Ext
Foundation
3
Name ends in _CS, _BL, _CW, _Sync or _API
_CS
_BL
_CW
_Sync
_API
Core
4
Name equals the application name, with or without spaces
End User
5
Anything else
Unclassified (not validated)
The findings follow the Architecture Canvas, using these layers and the entity-based dependencies:
Adapt the suffixes in the first UPDATE of the qBuildMarkdown SQL query in GetMarkdown if your naming conventions differ.
UPDATE
qBuildMarkdown
GetMarkdown
The export is read-only and reaches only authenticated IT users; it never reads credentials.
BuildSafe_InClauseIntegerList
CheckRegisteredRole()
AccessDeniedException
REST_Web_Reference
REST_Expose
SessionToken
ServiceCenter_Token
SapConfig
Dependencies come only from entity references; everything else a module consumes is not visible to the export.
OSSYS_
Release Notes
Version 1.0.0
Benefits
Generated Information
The current version includes:
Limitations
Current dependency discovery is based on entity references.
The current version does not include dependencies that exist exclusively through:
The current integration inventory includes:
The current version does not include:
Architecture classifications are inferred from naming conventions and should be validated by solution architects when required.