OutSystems mentions an Orchestrator domain in their documentation, but Discovery doesn’t currently support it.
Adding this would help align Discovery with OutSystems best practices and improve the clarity of architecture in complex factories. It would make it easier to separate orchestration logic from core functionalities and enhance maintainability.
https://success.outsystems.com/documentation/11/app_architecture/outsystems_domain_driven_architecture/domain_driven_design_with_outsystems/
Hi Damian, thank you for you comment. Consider the orchestrator domain as a "thin"/"slim" domain with just enough logic/rules/artifacts to provide a given experience/journey to your final users (e.g. the customers). This orchestrator domain is just presenting a set of UI and coordinating the business capabilities that are owned by other domains as well as leveraging some foundational capabilities (provided by the horizontal domains). In the end , this is just another vertical, that consumes business capabilities from other verticals and this config is fully supported by Discovery. Notice the color of the orchestrator domain matches the color of the vertical domains, although I understand the way it is depicted can open the door to some confusion has it seems to be pointing to some kind of hierarchy between "orchestrator" and verticals - which is not the intention.
Long story short, you can simply config the orchestrator domain as a vertical on Discovery and name it "Orchestrator XYZ" if you need to distinguish from remaining vertical domains.
Best regards