Which of the below matches the most to Library Module Pattern - Extension Pattern...

The Extension Pattern refers to the use of an Extension Module, which is a specific type of Library module created in OutSystems Integration Studio. Its primary purpose is to extend the platform's native capabilities. This is achieved by either integrating with an external database, allowing its tables to be used as OutSystems entities, or by wrapping custom C# code and external libraries (.NET assemblies) into reusable Actions. This module then acts as a library, exposing this new functionality to other OutSystems applications.

A. This describes the Connector/Wrapper pattern, which is used to abstract and normalize an external API, not specifically to wrap external code or libraries.

B. This describes an event-driven synchronization pattern, a method for data replication, not for extending platform functionality with external code.

C. This describes the Cache-on-Demand (or Lazy Load) data integration pattern, which is a caching strategy.

D. This describes an Aggregation or Federation integration pattern, where a service acts as a broker for multiple external systems.

E. This describes the Abstract Core (or Summary/Detail) data integration pattern, another caching strategy focusing on summary data.

F. This describes the standard Core Service pattern for encapsulating an OutSystems entity and its business logic.

G. This describes the Sync Wrapper pattern, where synchronization logic is decoupled from the Core Service holding the replicated data.

H. This describes a direct integration pattern where no data is cached or stored locally in OutSystems.

J. This describes the Core Service with Local Replica pattern, a full data caching strategy.

1. OutSystems Official Documentation

"Designing the architecture of your OutSystems applications" Guide:

Section: Core Services > Integration Services: This section explains that Integration Services are used to connect with external systems. It states

"To integrate with an external database or to extend the logic with your own C# code

you must create an Extension Module." This directly supports the definition in option I.

Section: Caching external data: This section details the patterns described in options C

E

H

and J (Lazy load

Abstract Core

No cache

Full cache)

confirming they are distinct data caching strategies.

2. OutSystems Official Documentation

"Extend Logic with Your Own Code":

Introduction: This document explicitly states

"To extend the functionality of your OutSystems apps

you can create your own logic in C# and make it available in Service Studio... You do this by creating an Extension Module in Integration Studio." This validates that the core purpose of an extension is to wrap external code

as described in option I.

3. OutSystems Official Documentation

"Integrate with an External Database":

Introduction: This resource details the process of using Integration Studio to create an Extension Module that connects to an external database. It explains how this allows you to "use the tables and views in that database as Entities in your OutSystems application." This confirms the other key function of an Extension Module mentioned in option I.