OutSystems Reactive for Beginners

Learn to build a reactive bank transactions app that tracks debits and credits, categorizes spending, and budgets by category with a dashboard of charts.

Create and publish your first reactive web application in Outsystems by setting up server studio, connecting to your personal environment, and building a module with screens.

Import Excel data into the bank movements application by creating a blank core module, generating entities, a structure, and CRUD actions from Excel files, with id as the primary key.

Discover bootstrapping entities in OutSystems reactive by importing Excel data into the categories entity with a bootstrap action and a publish-time timer to populate records.

Create a budget entity in OutSystems, add year and value attributes, connect it to a category with a category ID, and visualize the one-to-many relationship.

Learn how to consume elements between modules in OutSystems by exposing core entities as public, managing dependencies, and enabling create, read, update, and delete access for a consumer module.

scaffold web screens with drag-and-drop from core module entities, auto creating list and detail views. leverage search, pagination, forms, and control read-only behavior with input variables, aggregates, and local variables.

Learn to scaffold and publish web screens in OutSystems, set and switch the default home screen, then create, edit, and filter records and categories using forms.

Build a custom dashboard screen with a line chart to visualize banking information per month, using an aggregate from the bank movement entity in OutSystems.

Group data by year and month using an aggregate attribute and the month function, returning blue attributes and the sum of debits, mirroring an SQL-like runtime query for dashboards.

Arrange two charts in two columns on the dashboard; bind a line chart to bank movements by month and a pie chart to debits by category using aggregates and joins.

Create and preview two charts in OutSystems reactive, a line chart and a pie chart using the get bank debits by category list, with a conditional label for empty categories.

Define user roles and implement role-based access control to restrict screens and data in OutSystems, creating a bank movement role with check, grant, and revoke operations.

Create and test a new user and groups in OutSystems, assign roles, and verify permissions via the users app, noting the master administrator governs roles and triggers forbidden access.

Manage users and roles by adding and removing roles, creating groups, and testing access in the OutSystems platform. Bind users to data with a user id and one-to-many bank movements.

Publish and refresh modules, then assign the current user ID to new bank movements and filter aggregates by get user ID, enabling user-specific dashboards.

Use server actions and wrapper server actions to secure data by exposing only read-only access from the UI module. Move CRUD logic to the core module and publish changes.

Learn to debug OutSystems apps using the true change console and debugger, set breakpoints, inspect variables, fix frontend and server action issues, and publish before debugging.

Start debugging in service studio, open the bound browser tab, and set breakpoints to inspect form validation, widget, and session variables with watches for persistent debugging insight.

Learn to debug Outsystems applications by using breakpoints across front end and core modules, stepping through actions, updating data, and inspecting server actions, entities, and pagination.

Learn to debug an Outsystems reactive app by using breakpoints, stepping through pagination with start index and max records, and inspecting bank movements in UI module and core module.

Learn to monitor your OutSystems reactive app with service center, view logs, and explore an exception-driven save detail action flow on the bank movement screen.

Explore service center part 2: manage modules, dependencies, and logs; publish, redeploy, and download the bank movements core module and its solution; configure site properties, integrations, and multi-tenancy.

Create, name, and publish or download solution versions with dependencies in OutSystems Service Center, then view and filter error and general logs with detailed entries.

Access and analyze web request logs, screen actions, and service actions to monitor performance, debug errors, and optimize Outsystems apps; explore environment health and security settings.