OutSystems Associate Developer study plan

Map the OutSystems web development lifecycle from module creation through deployment, writing a one-page summary in your own words

Create a Reactive Web App module and build at least three screens with navigation between them

Identify and label the core elements of a screen: widgets, placeholders, and screen actions

Explain how the Service Studio interface organizes logic, data, and UI into separate layers

Model a normalized entity structure with at least two related entities and appropriate data types

Create and consume a server action that queries and filters entity records

Bind entity data to a table or list widget and verify the rendered output

Apply input validation using built-in validators and explain where validation logic executes

Compare Reactive Web and Mobile app architectures and list the constraints unique to mobile

Create a Mobile App module and build screens that use mobile-specific widgets

Configure local storage entities and demonstrate offline-tolerant data entry

Explain how screen lifecycle events differ between web and mobile screens

Reuse a server action across both a web and a mobile module by describing the sharing pattern

Implement role-based screen access and verify behavior with two test users

Debug a failing action using the debugger and document the root cause

Refactor duplicated logic into a single reusable action

Describe how ODC differs from traditional OutSystems platform deployment and lifecycle management

Create an app in ODC and publish it to a development environment

Explain the ODC concept of environments, stages, and asset reuse in your own words

Identify which built-in capabilities replace self-managed infrastructure tasks

Build a multi-screen ODC app that reads and writes data using ODC entities

Integrate an external REST API call and handle both success and error responses

Add user authentication and restrict a screen to authenticated users only

Document the app's architecture in a simple component diagram

Build a complete small web app from requirements to published version without following a tutorial

Apply consistent UI patterns using layout blocks and reusable web blocks

Handle exceptions at the action level and surface friendly error messages to users

Write and execute a manual test checklist covering at least eight scenarios

Build a small mobile app end to end and publish it

Review all four domains and list your three weakest subtopics with a remediation action for each

Complete a timed 60-question self-assessment and score it honestly

Re-explain the five concepts you got wrong until you can state them accurately without notes