Application Lifecycle: 1-Click Publish, LifeTime, Environments, and Versioning

OutSystems Certified Associate Developer Reactive Web Apps

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

Exam Overview, Logistics, and Study Strategy

2 Chapter 2 — OutSystems Platform and Reactive App Fundamentals

OutSystems Platform Architecture, Service Studio, and Development Tools Client Variables and State Management Screen Lifecycle Events: OnInitialize, OnReady, OnParametersChanged Debugging and Monitoring with the Service Studio Debugger and Service Center

3 Data Modeling

Entities, Attributes, Data Types, and Identifiers Static Entities and Structures Data Relationships, Foreign Keys, and Referential Integrity

4 Chapter 4: Fetching Data

4.1 Aggregates: Filters, Sorting, and Max Records 4.2 Aggregates: Joins, Group By, and Computed Attributes 4.3 Fetching Data on Screens with Data Actions, Caching, and RefreshData 4.4 SQL Queries and External Integrations: REST and SOAP Consumption

5 Logic Flows and Actions

Client Actions, Server Actions, and Action Parameters Logic Flow Control: If, Switch, For Each, and Assign Form Validations: Mandatory, Email Type, and Form.Valid

6 Chapter 6: Error Handling and Advanced Logic

Exception Handling: Exception Handlers, Raise Exception, System vs User Exceptions, AbortTransaction Timers, BPT Processes, Human Activities, and Built-in Functions

7 UI Design: Screen Widgets

Core Screen Widgets: Screen, Container, Expression, If, Link, and Button Forms, Input Widgets, Data Binding, and Feedback Messages List Widget, Pagination, and Screen Navigation Themes, CSS Styling, OutSystems UI, and UI Patterns (Popup/Modal)

8 UI Design: Blocks and Events

Blocks: Creating Reusable UI Components with Input Parameters and Local Variables Block Events and Parent-Screen Communication

9 Architecture, Security, and Lifecycle

Modular Dependencies, Public/Private Elements, and Layered Architecture Role-based Security: Roles, Accessible By, CheckRole, GrantRole, Anonymous Application Lifecycle: 1-Click Publish, LifeTime, Environments, and Versioning

Application Lifecycle: 1-Click Publish, LifeTime, Environments, and Versioning

Key Takeaways Explain This Topic AI

1-Click Publish runs TrueChange checks, compiles the module, and deploys it to the current environment in one action.

LifeTime is the cross-environment deployment console that moves versioned applications between Development, Test, and Production.

Service Center is the per-environment administration console for error logs, Site Property overrides, and runtime configuration.

Site Property values set in Service Center override Service Studio defaults and survive republishing the module.

The OnBeforeRequest callback modifies outgoing REST requests to add headers or auth tokens before sending.

Last updated: July 2026

Quick Answer: 1-Click Publish in Service Studio compiles, runs TrueChange checks, and deploys a module to the current environment in one action. LifeTime is the OutSystems deployment management console that moves versioned applications across environments (Dev, Test, Prod). Service Center is per-environment administration for logs, Site Properties, and runtime config. Site Properties let you override values per environment without republishing.

1-Click Publish

1-Click Publish is the single-button deployment mechanism in Service Studio. When clicked, it runs TrueChange — OutSystems' static analysis engine that checks for errors, broken references, dependency violations, and type mismatches. If TrueChange finds errors, the publish is blocked. Warnings do not block publishing. After TrueChange passes, the module is compiled into deployable artifacts (server-side code and client-side JavaScript bundles) and deployed to the current environment , typically Development. A new version number is registered automatically.

Step What Happens Blocks Publish?

• TrueChange errors Type mismatches, broken references, missing dependencies Yes
• TrueChange warnings Best-practice suggestions, unused variables No
• Compile Server and client artifact generation Yes if compile fails
• Deploy Push artifacts to the environment server —
• LifeTime and Environments

LifeTime is the OutSystems deployment management console — a separate web application that manages applications across all environments. A typical OutSystems installation has at least three environments:

• Environment Purpose Deployed From
• Development Developer iteration; 1-Click Publish target Service Studio directly
• Test / QA Integration testing, user acceptance LifeTime deployment from Development
• Production Live application for end users LifeTime deployment from Test (approved)

LifeTime lets you create deployment plans that bundle one or more applications with specific versions and deploy them together to a target environment. Deployments are versioned and tracked — you can see who deployed what, when, and from which source environment. LifeTime also supports rollbacks to previously deployed versions when a deployment goes wrong.

Service Center

Service Center is the per-environment administration console. Each environment has its own Service Center instance. Through Service Center you can view application lists and module versions installed on that environment, inspect error logs and general logs for debugging runtime issues, override Site Property values without republishing, monitor environment health (memory, CPU, database connections), and manage security and authentication settings.