The statement is false. According to the official OutSystems 3-Layer Canvas architecture, the Foundation layer is designed exclusively for non-business services. Its primary purpose is to provide reusable, non-functional logic and to abstract integrations with external systems. Core business concepts and their corresponding services (e.g., Customer, Product, Order) must be placed in the Core layer. Placing business services in the Foundation layer is considered an architectural anti-pattern as it breaks the intended abstraction and creates incorrect dependencies, leading to a monolithic and less agile application portfolio.

The "True" option is incorrect because it violates the fundamental principle of separation of concerns defined by the OutSystems 3-Layer Canvas. The canvas explicitly segregates non-business, technical services (Foundation) from core business logic and entities (Core). This separation is crucial for ensuring reusability, maintainability, and loose coupling across the application landscape.

1. OutSystems Official Documentation

"Designing the architecture of your OutSystems applications

" The 3-Layer Canvas

Foundation layer.

Reference: "The bottom layer contains all modules that provide reusable non-functional logic

and integration with external systems. These modules are the building blocks of your application portfolio... Examples of foundation modules are services to integrate with a legacy system

or a library with functions to handle complex security requirements." This source explicitly defines the Foundation layer for non-functional and integration purposes

not business services.

2. OutSystems Official Documentation

"Designing the architecture of your OutSystems applications

" The 3-Layer Canvas

Core layer.

Reference: "The middle layer contains modules that encapsulate the core business concepts of your application portfolio... Core modules provide reusable services and data around a business concept (e.g. Customer

Product

or Invoice)." This clearly designates the Core layer as the proper location for business services.

3. OutSystems Official Documentation

"Architecture Dashboard

" Code analysis patterns

"Incorrect Foundation dependency (IFD)".

Reference: "This finding is triggered when a Foundation module references a Core or an End-user module. Foundation modules should be independent of any business context to be truly reusable across all applications. Referencing a Core or an End-user module introduces a business context in a Foundation module." This technical enforcement rule confirms that Foundation modules must remain free of business context

which is embodied in business services.