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

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

Service Action

REST API

framework to support Architecture Conventions for Modules in Outsystems

framework to support application architecture design in Outsystems

framework to support Architecture Design Process in Outsystems

Denormalize the local storage

Define only used attributes

Group relevant information

Store all records no matter if relevant or irrelevant

Discovery automatically assigns a module to an Architecture Canvas layer, following the module's naming convention.

Discovery only validates architecture rules at the module level.

Discovery allows you to determine for every module, which elements are being consumed by other modules.

Discovery cannot categorise modules to domains

Core modules should have Front-end Screens for testing purposes.

Core modules should not have Core Entities.

Core modules should have public Read-only Entities.

Core modules should not have business logic.

Poor service abstraction

Reduces costs

Reduces risk

Supports planning

Screens as layouts that have placeholders and load content from blocks. The blocks come from CW modules.

Include the Common flow and Menu artifacts

Put CSS in blocks or screens. Allows better performance and seamless screen transitions

Blocks grouped in functional modules with independent life cycles

CSS should only be placed in the mobile theme module

Store password in local storage

Encrypt (only) sensitive data

Authentication : Use google or facebook for online authentication or fingerprint or pin for offline authentication

Security and scalability.

Speed up the development phase.

Improve performance and maintainability.

Allows apps and the Style Guide to be deployed to Production.