OutSystems Professional DevOps Engineer key terms

The OutSystems central management console where you register environments, deploy applications between them, manage users and roles, and inspect platform-wide logs and health information.

An isolated OutSystems installation, such as Development, Quality, or Production, that hosts its own applications, database, and deployment target for a given stage of the delivery lifecycle.

A saved mapping in LifeTime that defines which applications move from a source environment to a target environment, including the order in which they are deployed.

The LifeTime component that orchestrates a running deployment, sequencing application compilation, database synchronization, and publishing across the source and target environments.

A named snapshot of an application's current modules and versions, used to mark a release candidate so it can be deployed later without picking up subsequent development changes.

A numbered revision of a deployed application in LifeTime, incremented on each successful deployment and used to identify exactly what is running in an environment.

Restoring a previously deployed application version in a target environment, typically to recover from a faulty release; database schema changes may limit how far back it can go.

The per-environment OutSystems management console for inspecting modules, solutions, timers, and published application details within that single environment.

A grouping of related OutSystems modules that are compiled and published together as a unit, often used to bundle an application with its shared libraries.

The basic deployable unit in OutSystems, such as a reactive web app, a service module, or a library, containing the logic, screens, and data model it exposes.

A LifeTime-level container that groups one or more modules and is the unit tracked through deployment plans and versions across environments.

A command-line interface (OSPT or oml) used to script build, pack, and deploy operations, enabling automation of OutSystems delivery inside external CI/CD tools.

A REST API exposing LifeTime operations such as creating deployments and querying applications, letting external pipelines trigger and monitor deployments programmatically.

An automated sequence that builds, tests, and promotes OutSystems applications through environments, usually orchestrated by an external tool calling the LifeTime API or CLI.

A dedicated machine or agent that compiles OutSystems modules and produces deployment packages, keeping heavy compilation work off developer machines and production environments.

The step in which OutSystems translates a module's model into executable code and validates it, producing errors or warnings that block or allow a deployment.

The Service Studio action that compiles a module and deploys it to the current environment, commonly used in Development but discouraged as a production release mechanism.

The OutSystems integrated development environment where developers build modules, run local tests, and initiate publishes to the connected environment.

The deployment phase that applies model changes to the target database schema, adding or altering tables and columns; destructive changes require manual intervention.

The practice of externalizing environment-specific values, such as endpoints and credentials, so the same application package can run correctly in every environment.

A sensitive configuration value such as a password, API key, or connection string that must be stored encrypted and never hardcoded in module logic or source control.

An OutSystems authorization concept that grants a set of permissions to users, checked at runtime to control access to screens, actions, and exposed service operations.

A specific granted capability, such as executing an action or viewing a screen, that is attached to roles and evaluated by the platform when a request is made.

The process of verifying a user's or system's identity, configured per environment and often delegated to an external identity provider through a supported plugin.

An authentication pattern in which users log in once through a central identity provider and gain access to multiple OutSystems applications without re-entering credentials.

A record of inbound and outbound integration calls, including SOAP and REST requests, used to diagnose failures, latency, and payload issues between systems.

The Service Center tool for browsing general, error, and integration logs in an environment, filtering by module, date, or severity to investigate incidents.

A log capturing exceptions and unhandled errors raised by modules, including stack details and the module and action where the failure occurred.

Structured logic that catches and responds to runtime errors, logging meaningful context and returning controlled responses instead of exposing raw error details to users.

An explicit entry written by application logic to record diagnostic information, used to trace business flows and correlate activity across modules and integrations.

Observing response times, throughput, and resource usage of deployed applications to detect degradation and validate that releases meet service expectations.

A LifeTime view summarizing an application's health across environments, including deployment status, errors, and performance indicators for running modules.

A configured notification triggered when a monitored condition, such as repeated errors or high response time, crosses a threshold, prompting operator investigation.

A scheduled background job defined in a module that runs at configured intervals; monitoring its execution history helps detect failures and overlapping runs.

A chronological record of administrative and security-relevant actions, such as deployments, permission changes, and logins, used for accountability and investigation.

The policies and controls that regulate who may develop, approve, and deploy applications, ensuring consistent quality and compliance across teams and environments.

A verification that an environment is reachable and correctly configured, including database connectivity and service status, typically run before or after a deployment.

A compiled artifact containing one or more modules and their dependencies, produced by a build step and transported to a target environment for deployment.

A reference from one module to another, such as a producer module or extension, that must be resolved and deployed in the correct order during a release.