先試後買

A. Architecture Dashboard performs a code analysis that uncovers patterns related to performance, security, architecture and maintainability.

B. Architecture Dashboard allows you to automatically apply a solution to solve a found code pattern.

A. Limit Server side calls to online transactions or Synchronization. Do the bulk of the operations on the Client Side before passing information to the Server Side.

B. Synchronize on every screen or online event for better granularity
No direct calls to backend systems. Do call to Outsystems Core Services and Outsystems will handle the interaction with external backend systems.

C. Direct calls is bad from Security, Performance and Maintainability standpoint. Direct calls will require javascript Code and javascript Code is harder to maintain.

A. Sync data required per use case: Sync summary data on Session start. On data selection, sync p its details.

B. Adopt the correct sync frequency: Either at process start and online or at process/transaction end and online

C. Sync on every screen or online event

A. No Circular References

B. No Upward References

C. No Side References Between End-User Modules

D. No Downward References To Foundation Modules

A. Ensure sync granularity: Prepare for constant retries without repeating work due to network loss. Sync in chunks, incremental by entity

B. Only synchronize delta : Use control timestamps
C Avoid long synchronization in a single transaction

C. Only synchronize relevant data

D. Sync only when strictly required
E Don't sync on every screen or online event

E. Sync only when required. p At session start: sync summary data to local storage At process start: sync process detail to local storage At process/transaction end, sync back to server

F. Do not use Entity Bulk Operation to ensure small lightweight updates

A. Structures

B. Local Storage Entities

C. Database Entities

D. Server Actions

E. Screens

F. Service Actions

G. Static Entities

A. Optimizes lifecycle independence

B. Minimizes impact of changes

C. Promotes segregation and loose coupling of services

D. Promotes abstraction of reusable services

A. Architecture Canvas

B. Architecture Framework

C. Architecture Validation

D. AI Mentor

A. Reusable UI Patterns for layout and display only - no Business logic.

B. to have several integration services with different systems, performing the same type of operation (e.g. printers) you can create several drivers exposing the same API, with specialized implementations (like the transparency services pattern).

C. technical wrapper to consume and normalize an external service.

D. Generic Library module.

E. Theme, look & feel elements, menu, etc.