Pass the OutSystems Architecture Specialization Architecture-Specialist-11 Questions and answers with CertsForce

Specialize a Built-in: Use when introducing changes to an existing theme for multiple apps. First, create a custom theme that REFERENCE the Base Theme. Second, clone a Custom

Template from the Base Template but this custom theme will reference the custom theme created previously. Third, create new applications based on the Custom Theme and Custom Template

Built-in Style Guide: Uses Built-in style guide from Outsystems UI. Minor customizations to the Base Theme should be done inside the App Theme.

C, Build Your Own: Use when custom style guide cannot benefit from any existing theme. Just like Clone a Built In scenario, clone both Custom Theme and Custom Template from the Base Theme and Base Template, however clone the Base Theme from Outsystems UI.

Since the theme is very basic, front-end developer will have to expand and design the theme from there.

Modify Built-in Style Guide: Use when only small changes are required for single application. First, create a custom theme that REFERENCE the Base Theme. Second, clone a Custom Template from the Base Template but this custom theme will reference the custom theme created previously. Third, reference that application to the custom The

Clone a Built-in: Use when introducing extensive changes to existing theme. First, CLONE a custom theme from a Base Theme. Second, clone a Custom Template from the Base Template but this custom theme will reference the custom theme created previously. Third, create new applications based on the Custom Theme and Custom Template.

Base Theme can be Outsystems UI or your own custom theme.

... 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)

... 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.

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

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

... tries to fetch data from local cache entity, if not there, get single entry from the external system. Cache only that record (read-through caching) Use when whole database too big or costly to synchronize. Integration only touches a small portion of the database. Avoid if access to lists of data is needed up front

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)

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

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.

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

... tries to fetch data from local cache entity, if not there, get single entry from the external system. Cache only that record (read-through caching) Use when whole database too big or costly to synchronize. Integration only touches a small portion of the database. Avoid if access to lists of data is needed up front

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

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

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)

... 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

A BL becomes a Calculation Engine if it performs complex calculations, (e.g. an invoice calculation engine or an insurance simulator). Engines are usually subject to versions.

Logic to Synchronize data in CS's with an external system. Isolating this logic makes the CS completely system agnostic and it's easier to decouple or replace the external system.

Isolated Business Logic (Actions), to manage complexity, composition or to have its own 'ifecycle.

Reusable Core Services with public entities, actions, and blocks.

Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.