OutSystems Associate Developer flashcards

33 cards. Read the term and the definition here. The deck at the top of this page is optional.

Screen lifecycle order

Initialize runs first, then Prepare, then Render builds the UI, and Ready fires on the client after display. Each event has a distinct purpose in the screen's execution.

Aggregate purpose

An Aggregate queries the database and returns a Record List. Its output must be assigned to a screen or action variable to be used elsewhere.

Server vs Client Action

Server Actions execute on the server and can access the database. Client Actions run in the browser and cannot directly query the database.

Session Variable scope

A Session Variable persists for the duration of a user's session and is shared across screens. A Screen Variable is limited to one screen instance.

Site Property definition

A Site Property is a configuration value that can be changed at runtime in Service Center without redeploying the module. It is read by server logic.

Screen role access

Screen access is controlled by adding Roles to the screen's Roles property. Only users with a matching role can open the screen.

Web Block communication

A Block is a reusable UI component with its own scope. It receives data through Input Parameters and notifies its parent by raising Events.

Input vs Output Parameter

Input Parameters pass values into a Screen or Action. Output Parameters return values from an Action back to its caller.

Mobile screen lifecycle

Mobile screens follow Initialize, Prepare, Render, Ready. Prepare executes on the device rather than the server, unlike reactive web screens.

Offline Data Sync

Offline Data Sync keeps local entities on the device synchronized with the server. Entities must be configured with appropriate sync behavior in the data model.

Client Variable persistence

A Client Variable is stored on the device and survives app restarts. A Screen Variable exists only while that screen instance is alive.

Mobile navigation pattern

Mobile navigation targets a destination Screen with optional Input Parameters. The platform manages the back stack automatically.

Mobile UI templates

List, Detail, and Edit are standard mobile screen patterns. Templates pre-wire navigation and data binding so developers customize rather than build from scratch.

Device plugin usage

Plugins expose device capabilities such as camera, GPS, and notifications. Each requires a plugin reference and a build that includes it.

Mobile offline limitation

In offline mode, mobile apps cannot rely on server-side screen Aggregates. Use local entities and client-side logic to supply data instead.

Native shell rendering

A mobile module generates a native shell that renders screens locally on the device. Browser preview does not fully reflect native behavior.

Mobile build requirement

A mobile module must be generated and installed on a device or emulator to test native features. Publishing alone does not produce an installable app.

ODC app structure

In ODC, an App contains one or more Modules. Each module is typed as Web, Mobile, or Library depending on its purpose.

ODC deployment stages

ODC uses a stage-based pipeline with Development, Test, and Production stages as separate environments. Apps are promoted through these stages.

Library module role

A Library module exposes reusable Actions and Entities but contains no screens. Other modules reference it as a producer.

Public Elements exposure

Actions, Entities, and Structures must be marked as Public Elements in the Producer module before a Consumer module can reference them.

ODC identity model

ODC uses OIDC-based authentication. End users are managed by the identity provider configured for the organization, not inside the app.

ODC Portal vs Studio

The ODC Portal manages users, roles, apps, and environments. ODC Studio is the IDE where modules are built and published.

Entity Identifier attribute

Every Entity has an auto-generated Identifier attribute that uniquely identifies each record. It is used for lookups, updates, and deletes.

App-level deployment

Deployments in ODC are triggered per app and promote all of the app's modules together through the pipeline stages.

App template starting point

Templates such as Reactive Web or Mobile pre-generate screens, theme, and navigation. Developers then customize rather than build structure from scratch.

Build order rule

Create Entities first, then Aggregates to read them, then Screens that bind Aggregate outputs to widgets. Data drives the UI.

Form save pattern

A Form bound to an Entity creates or updates records. The Save action persists the record and returns the identifier of the saved row.

List widget binding

A List widget bound to a Record List renders one row per record. The List Item defines the template for each row.

Input validation rules

Set Mandatory and data-type constraints on inputs. Server-side validation runs in the Save action before the record is persisted.

Delete flow pattern

Pass the record Identifier as an Input Parameter to the delete screen or action, then call the Delete Entity action to remove the record.

If widget usage

The If widget renders its content conditionally based on a Boolean expression. It is used to show or hide UI sections at runtime.

Publish and test cycle

After building, publish the module and open the generated screens in a browser or device. Use the debugger to inspect runtime errors.