OutSystems Professional DevOps Engineer flashcards

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

LifeTime deployment plan

An ordered list of environment steps that a solution follows from Development to Production, with optional manual approval gates between steps.

OutSystems CLI (OSCLI)

Command-line tool used in CI pipelines to authenticate to an environment, deploy solutions, publish modules, and query application state without the LifeTime UI.

LifeTime REST API

HTTP API under /lifetimeapi/rest/v2/ that exposes deployments, applications, environments, and health data for automation by external CI servers.

Solution version label

A version string assigned to a solution when deployed; stored in the target environment and queryable via API to trace which build is live.

Impact analysis before publish

A platform check that identifies dependent modules affected by a change, marking them as needing republish so the pipeline can deploy them together.

BDD tests in pipeline

Behavior-driven tests written in Gherkin/SpecFlow and executed in the Quality environment as a pipeline stage before Production promotion.

Service account token

A non-human credential used by CI tools to authenticate to OutSystems environments; scoped to the minimum roles required for deployment.

Deployment controller

The environment component that receives deployment requests from LifeTime, pushes modules to front-end servers, and reports deployment status back.

Environment registration

Adding an environment to LifeTime by its deployment controller address and assigning a role such as Development, Test, or Production.

Asynchronous deployment

A deployment is queued and executed in the background; the pipeline must poll status (success, failed, needs-republish) rather than assume completion.

Dependency deployment

A rule requiring all solution dependencies to be deployed together or already present in the target; missing dependencies cause a deployment failure.

Destructive schema change

A database change such as dropping a column or altering a type; OutSystems requires manual confirmation because it can cause data loss.

Rollback by redeploy

Reverting to a prior state by redeploying the previous solution version from the source environment; the platform retains prior module versions in the target.

Environment health check

A pre-deployment validation of controller connectivity, database connectivity, session database, and license status; failures block deployment.

Front-end scaling

Adding front-end servers behind a load balancer to increase capacity; the deployment controller distributes modules across all front-ends.

Service Center monitoring

Real-time and historical performance counters in Service Center showing requests per minute, average response time, errors, and exceptions per module.

Log severity levels

Error, Warning, Info, and Debug categories for platform log messages; Debug must be enabled per module and disabled after troubleshooting.

Integration logs

Records of consumed and exposed SOAP/REST calls including request and response payloads, with configurable retention per environment.

LogMessage action

A platform action that writes custom entries to the OutSystems log with a chosen severity and module context for traceable diagnostics.

Slowest Queries screen

A Service Center screen ranking database queries by execution time, used to locate performance bottlenecks before code review.

Health Monitor alerts

Environment-level alerts triggered by conditions such as high error rate or database connection issues, with thresholds configured per environment.

ExceptionHandler in flow

A flow element that catches unhandled exceptions, logs them, and allows the process to recover gracefully instead of failing the request.

External log shipping

Forwarding platform logs to an external SIEM or log store; requires custom integration because native logs reside in the platform database.

LifeTime roles

Administrator, Developer, Tester, and Operations roles that determine who can create deployment plans and execute deployments.

IT user federation

Authentication of platform users via built-in credentials, Active Directory/LDAP, or SAML 2.0/OpenID Connect identity providers.

End-user authentication

Application-level login using the Users application, an external IdP via SAML/OIDC, or custom authentication, with sessions stored in the session database.

Site Property secrets

Configuration values that may hold credentials; they must never be committed to source control or exposed in client-side code.

Per-environment licensing

OutSystems licenses are assigned per environment; Production requires a full license while non-production typically uses development or test licenses.

Deployment audit trail

LifeTime records who deployed which solution and when; Service Center logs configuration changes and user administration actions.

Platform backup routine

Periodic backups of the platform and application databases plus certificate renewal and server patching, scheduled as part of platform operations.

Production publish restriction

A governance control limiting who can publish to Production and requiring impact analysis plus approval before any deployment proceeds.