A. Screens as layouts that have placeholders and load content from blocks. The blocks come from CW modules.
B. Blocks grouped in functional modules with independent life cycles
C. CSS should only be placed in the mobile theme module
D. Include the Common flow and Menu artifacts
E. Put CSS in blocks or screens. Allows better performance and seamless screen transitions
A. Core modules should have public Read-only Entities.
B. Core modules should not have Core Entities.
C. Core modules should not have business logic.
D. Core modules should have Front-end Screens for testing purposes.
A. Reusable Core Services with public entities, actions, and blocks.
B. 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.
C. Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.
D. 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.
E. Isolated Business Logic (Actions), to manage complexity, composition or to have its own 'ifecycle.
A. Only Foundation Modules.
B. End-User, Core, and Foundation Modules.
C. Foundation and Core Modules
D. End-User and Core Modules.
A. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
B. 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
C. 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)
D. ... 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
E. ... Entity is not in Outsystems but in an external ERP system. IS just makes remote call to 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
F. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
G. ... 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)
H. 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.
I. 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
J. ... 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. Core Application.
B. Foundation Application.
C. End-User Application.
A. It is not possible to customize a built-in Style Guide, since it is part of OutSystems UI.
B. When you want to introduce extensive changes to an existing theme.
C. When minor customizations to the base theme should be done inside the app theme.
D. When it is not possible to benefit from any existing theme and extensive changes are needed.
A. 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
B. Unmanageable dependencies : System not isolated from each other. Updating or replacing a system has a cascade/snowball effect on other systems
C. Poor service abstraction : Business concepts not correctly isolated, business rules tend to be spread over different systems and little to no code reuse
D. Tech Debt : AI Mentor will raise architectural tech debt such as cyclic dependency and side to side dependency
A. Store all records no matter if relevant or irrelevant
B. Group relevant information
C. Denormalize the local storage
D. Define only used attributes
