End-User, Core, and Foundation Modules.

Foundation and Core Modules

Only Foundation Modules.

End-User and Core Modules.

Inflexible and slow-moving legacy systems : adapting legacy systems to business changes may be difficult. Changes in complex and inflexible systems can take a long time

Tech Debt : AI Mentor will raise architectural tech debt such as cyclic dependency and side to side dependency

Unmanageable dependencies : System not isolated from each other. Updating or replacing a system has a cascade/snowball effect on other systems

Poor service abstraction : Business concepts not correctly isolated, business rules tend to be spread over different systems and little to no code reuse

... Entity is not in Outsystems but in an external ERP system. IS just makes remote call to p external system/database. No data is being kept inside OS. Data retrieval may not be optimized as it needs to traverse two different systems to get the information back. Con: Integration API must support all use cases

... is a pattern with two modules, a connector module that can be used to encapsulate an O external API with the input/output structures and a wrapper module to expose the normalized API to the consumers.

p Same as ECS with local replica but synchronization logic is separated. Pro: Code

independence. Consumers of CS is not affected by Sync. Sync can orchestrate several CS

... a wrapper used to contain the logic, actions and data that will expose code that is inside of external library or to inspect external database and import the data structures so they can be used as entities inside of OS

... caches only summary data that is frequently lister, joined or searched. Full detail for a single entry is fetched directly from external system. Use when whole database too big or costly to synchronize. Details are only required for single entities (not lists)

... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update

F Same as Base ECS pattern, but have a local replica. Store data to serve as a local cache. Pro: Leverage Entity Use, Simpler Integration API. Con: Less impact on source system

G ... tries to fetch data from local cache entity, if not there, get single entry from the external system. Cache only that record (read-throug

... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.

Same as ECS with local replica but API module is provided. So any changes to the external system can notify OS, which OS then gets update from the ERP system (subscription system)

... Entity is not in Outsystems but in an external ERP system. IS just makes remote call to

p external system/database. No data is being kept inside OS. Data retrieval may not be optimized as it needs to traverse two different systems to get the information back. Con:

Integration API must support all use cases

... caches only summary data that is frequently lister, joined or searched. Full detail for a single entry is fetched directly from external system. Use when whole database too big or costly to synchronize. Details are only required for single entities (not lists)

... a wrapper used to contain the logic, actions and data that will expose code that is inside of external library or to inspect external database and import the data structures so they can be used as entities inside of OS

Same as Base ECS pattern, but have a local replica. Store data to serve as a local cache. Pro: Leverage Entity Use, Simpler Integration API. Con: Less impact on source system

... is a pattern with two modules, a connector module that can be used to encapsulate an external API with the input/output structures and a wrapper module to expose the normalized API to the consumers.

... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update

. Same as ECS with local replica but synchronization logic is separated. Pro: Code independence. Consumers of CS is not affected by Sync. Sync can orchestrate several CS