This would be particularly useful for large 3/4 layer applications
When an application is selected, the containing espaces are presented to the developer in the form of their location in the current Outsystems Architecture Canvas and their dependencies. For example:
UXOrchestration
"Order Process Interface"
Composite Applications
"Order Business Logic"
"Customer Business Logic"
Core Business Services:
"Order Services"
"Customer Services"
Infrastructure:
"XML wrapper"
"Salesforce Integration"
I think having this organic model as a current representation of the application's architecture would give better readability, promote cleaner architecture and allow support or new developers get up to speed faster.
Matt
When an application is selected, the containing espaces are presented to the developer in the form of their location in the current Outsystems Architecture Canvas and their dependencies. For example:
UXOrchestration
"Order Process Interface"
Composite Applications
"Order Business Logic"
"Customer Business Logic"
Core Business Services:
"Order Services"
"Customer Services"
Infrastructure:
"XML wrapper"
"Salesforce Integration"
I think having this organic model as a current representation of the application's architecture would give better readability, promote cleaner architecture and allow support or new developers get up to speed faster.
Matt