Mendix Rapid Developer study materials
Mendix Rapid Developer study resources

Mendix Rapid Developer study plan

Mendix Rapid Developer · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Mendix Platform and Studio Pro Fundamentals & Domain Model and Data Modeling

  • Map every Studio Pro pane, menu, and toolbar action to the concept it controls by building a blank app and labeling each area in a personal glossary

  • Create a domain model with at least six entities, including one generalization/specialization pair, and justify each cardinality in writing

  • Configure associations with correct ownership and delete behavior, then verify the resulting database behavior by inspecting the app's data in Studio Pro

  • Define validation rules on three attributes and predict the error a user sees before testing it

Your checkpoint

A working app with a documented six-entity domain model, a one-page glossary of Studio Pro concepts, and a written justification of every association and validation rule

Week 2

Domain Model and Data Modeling & Microflows and Business Logic

  • Build a microflow that creates, retrieves, and commits related objects across at least two associations without orphaning records

  • Implement a loop with a conditional branch and a decision that uses an exclusive split on an enumeration

  • Call a sub-microflow from a parent flow, pass an object as a parameter, and return a changed object

  • Handle an empty result from a retrieve action explicitly instead of letting the flow continue with a null object

  • Convert one repeated microflow pattern into a reusable sub-microflow and record why reuse matters for maintenance

Your checkpoint

A documented microflow library of at least five flows, each with a written description of its inputs, outputs, and error path

Week 3

Microflows and Business Logic & XPath, Validation, and Events

  • Write XPath constraints that filter on associations, attribute comparisons, and enumeration values, and test each constraint against sample data

  • Trigger a before-commit event and a custom validation message, then confirm the message appears in the UI

  • Use a microflow to enforce a business rule that the domain model alone cannot express, and explain the choice in writing

  • Debug a failing microflow using breakpoints and the debugger, and document the root cause of the failure

  • Distinguish client-side validation from server-side validation in your own notes with one example of each

Your checkpoint

A validation suite of at least four rules (XPath, event handler, and microflow-based) with a short test log showing each rule firing and being satisfied

Week 4

Pages, Layouts, and User Interface

  • Build a responsive layout with a header, navigation, and content area, and reuse it across at least three pages

  • Configure a data grid with search, sorting, and paging, and connect it to a microflow data source

  • Create a master-detail page pair that passes context through a parameter and opens the detail page from the list

  • Apply conditional visibility to a widget based on a user role or an attribute value

  • Review the app in a mobile preview and fix at least two layout problems found there

Your checkpoint

A three-page UI with a shared layout, a master-detail flow, and a written before/after note on the mobile layout fixes

Week 5

Security and Access Control & Pages, Layouts, and User Interface

  • Define at least three module roles and map them to two user roles, then verify access by logging in as each role

  • Set entity and attribute access levels so that one role can read but not write a sensitive attribute

  • Restrict a microflow and a page to specific roles and confirm the restriction blocks unauthorized access

  • Configure a page's navigation so that menu items are visible only to permitted roles

  • Document the access matrix in a table that maps every entity and page to each role

Your checkpoint

A completed access matrix plus a test log of at least six role-based checks, including two negative tests that confirm access is denied

Week 6

Integration and REST/SOAP Services

  • Publish a REST endpoint from a published service and consume it from a second app or a REST client

  • Consume an external REST service with a JSON response, map the response to a non-persistent entity, and handle a non-200 status

  • Configure authentication for an outbound REST call and explain where the credentials are stored

  • Build a simple SOAP import or export and describe how the WSDL shapes the generated model

  • Write down the failure modes you observed, such as timeouts and malformed payloads, and how the flow handles each

Your checkpoint

A working integration demo with one published REST service and one consumed external service, plus an error-handling note covering at least three failure modes

Week 7

Deployment, Version Control, and Environment Management & Agile Development, Team Server, and Feedback Management

  • Commit an app to a Git repository with meaningful commit messages and resolve one deliberate merge conflict

  • Create a branch, make a change, merge it back, and record the steps in a short runbook

  • Configure at least two environment-specific constants and explain how they differ between environments

  • Package and deploy the app to a local or cloud environment and verify it runs after deployment

  • File a feedback item in the team feedback tool and triage it through to a resolved status

  • Describe the difference between the Team Server and a plain Git repository in your own words

Your checkpoint

A version-control runbook and a deployment checklist, both validated by actually deploying the app and closing one feedback item

Week 8

Mendix Platform and Studio Pro Fundamentals & Domain Model and Data Modeling & Pages, Layouts, and User Interface & Microflows and Business Logic & Security and Access Control & Integration and REST/SOAP Services & XPath, Validation, and Events & Deployment, Version Control, and Environment Management & Agile Development, Team Server, and Feedback Management

  • Take a full-length timed practice exam and record the score per domain

  • Re-study the two weakest domains using targeted exercises rather than rereading notes

  • Rebuild one microflow and one page from memory without reference material to test retention

  • Review every flagged or uncertain item and write a one-line explanation for each

  • Complete a final mixed set of questions under exam time pressure and confirm a score above your target

Your checkpoint

A scored practice exam report with a per-domain breakdown and a short remediation log for the two weakest domains

Milestones

Week 2: You can build a multi-entity domain model and a microflow that creates and commits related objects without orphaning records, and you can explain each association's delete behavior

Week 4: You can build a reusable layout, a master-detail page pair, and a conditional-visibility widget from scratch in under 45 minutes without notes

Week 6: You can publish a REST endpoint and consume an external REST service, including handling a non-200 response, and you can state the difference between REST and SOAP in your own words

Week 7: You have committed, branched, merged, and deployed the app, and you can describe the role of the Team Server and environment-specific constants without notes

Week 8: Your timed practice score is at or above your target, and no domain falls below 60 percent on the per-domain breakdown