OutSystems Delivery Specialist flashcards

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

Module

The basic unit of OutSystems application design, containing entities, logic, screens, and references; a module is versioned, deployed, and reused independently of other modules.

Library module

A module type that holds only server-side logic and no UI; used to share business rules and integrations across applications through public elements and references.

Producer and Consumer

A Producer module exposes elements as Public so other modules can reference them; a Consumer module references those public elements and depends on the Producer's version.

Client Action

Logic that executes in the browser or mobile device; it cannot query entities directly and must call exposed Server Actions or use Client Aggregates for data.

Server Action

Logic that executes on the OutSystems server; it can access entities, run aggregates, call integrations, and be exposed for reuse by client-side logic or other modules.

Block

A reusable UI fragment with its own inputs and logic that can be placed on multiple screens; changes to the Block propagate to every screen that uses it.

Layout

A reusable screen wrapper that provides shared chrome such as header, menu, and footer; screens choose a Layout, and themes can set a default for all screens.

Static Entity

An entity whose records are fixed at design time and identified by a Record Id string; it cannot be created or deleted at runtime and is ideal for enumerations and lookup values.

Aggregate

A visual query that returns a structured result set with filters, sorts, and group-by; it supports functions like Count, Sum, Average, Min, and Max without writing SQL.

Aggregate join types

Only With is an inner join, With or Without is a left join, and With or Without and Only Without is a full outer join; the choice determines which unmatched rows appear.

SQL query element

A read-only query written in SQL for requirements aggregates cannot express, such as unions or window functions; it must declare an output structure for the result.

Client Aggregate

An aggregate that runs in the browser or device against data returned by exposed Server Actions; it filters and sorts locally and cannot query entities directly.

Reference attribute

An attribute of type Entity Identifier that creates a relationship to another entity; it implements 1-to-Many or 1-to-1 relationships and stores the referenced entity's Id.

Many-to-Many relationship

A relationship requiring an explicit join entity with two reference attributes, one to each side; the join entity can also carry relationship-specific attributes.

Delete Rule Protect

The default delete rule; it blocks deletion of a record while other records reference it, preserving referential integrity unless the rule is changed to Delete or Ignore.

Delete Rule Delete

A cascading delete rule; deleting the referenced record also deletes all records that reference it, so use it only when dependent data should not survive.

Prepare event

A server-side screen lifecycle event that runs before rendering; it is the correct place to load data and validate input parameters before the screen is built.

Ready event

A client-side screen lifecycle event that runs after the screen renders; use it for client-only initialization such as focusing a field or starting a client widget.

Screen input parameter

A value passed into a screen or Block by value at navigation or render time; it is read-only inside the screen and cannot be used to persist state across navigations.

Session Variable

A server-managed value scoped to a user's session, used to carry state across screens; it is stored server-side and should not hold large or sensitive payloads unnecessarily.

Client Variable

A client-side value scoped to the browser or device session; it survives navigation within the app but is visible to the client and unsuitable for secrets.

Exception Handler flow

A built-in flow that catches unhandled exceptions; branch on Exception types such as DatabaseException or CommunicationException to show appropriate messages and recovery.

Consume REST API

A Service Studio feature that imports a REST API definition and generates methods and structures; you map responses into local structures before persisting or displaying data.

Timer

A scheduled server-side action that runs logic at intervals or set times; timers may retry, so their logic must be idempotent to avoid duplicate side effects.

Role-based security

Access control using Roles defined in a module; roles are assigned to users and checked through screen permissions or built-in role-check functions in logic.

Environment pipeline

The ordered set of environments such as Development, Quality, Pre-Production, and Production; application versions are promoted along it through deployment.

Solution

A container grouping applications and modules for deployment as one unit; deploying a solution version ensures the included modules and dependencies move together.

Publish versus Deploy

Publish compiles and applies changes in the current environment; Deploy promotes a tagged version to another environment and executes the deployment plan there.

Deployment plan

The ordered list of modules and actions executed during a deployment; review it for entity model changes that could require data migration or cause data loss.

LifeTime

The OutSystems console for managing environments, application versions, and deployments across the infrastructure; it is where promotions between environments are executed.

Service Center

The environment-level console for monitoring applications, modules, logs, and timers; it shows runtime health and is a primary triage tool for production issues.

Application lifecycle state

A status such as Development or Production; setting an application to Production protects it from accidental edits and signals it is live for end users.