Mendix Intermediate Developer study materials
Mendix Intermediate Developer study resources

Mendix Intermediate Developer study plan

Mendix Intermediate Developer · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Domain Model and Data Structure

  • Model a normalized entity structure with one-to-many and many-to-many associations for a sample ordering app

  • Choose between entity generalization and duplicate attributes, and justify the tradeoff in a written note

  • Configure system attributes (createdDate, changedBy) and a non-persistent entity for a calculation helper

  • Apply delete behavior and association ownership rules so cascading deletes do not orphan records

Your checkpoint

A published module containing 8+ related entities, 2 generalization hierarchies and a one-page rationale document explaining each modeling decision

Week 2

Microflows and Application Logic

  • Build a multi-branch microflow that uses decisions, merges and error events to validate input and roll back on failure

  • Replace duplicated logic with sub-microflows and pass parameters across at least two levels

  • Iterate a list with a loop and aggregate results using list operations instead of looping where a list operation exists

  • Implement before-commit and after-commit event handlers that enforce a business rule

  • Trace a failing microflow with the debugger and fix the defect

Your checkpoint

A microflow library of 5 reusable sub-microflows plus a validation flow that blocks invalid saves, demonstrated with 3 passing test cases

Week 3

Microflows and Application Logic & Pages, UX and Client-Side Logic

  • Convert a repetitive microflow into a reusable Java-free pattern using microflow expressions and conditional visibility

  • Bind page widgets to microflow return values and control data source refresh behavior

  • Build a page with conditional visibility, dynamic classes and a snippet reused in two contexts

  • Implement client-side navigation actions and explain when a microflow must run server-side

Your checkpoint

A working master-detail page pair driven entirely by microflows, with a written list of every widget-to-microflow binding and why it was chosen

Week 4

Integrations, REST and Web Services & Pages, UX and Client-Side Logic

  • Consume a public REST service with a published/external call microflow, mapping JSON to entities and handling non-200 responses

  • Expose an entity as a REST endpoint with authentication and a custom response mapping

  • Handle error responses and timeouts by branching on the response status rather than assuming success

  • Design a page that displays integration errors to end users without exposing raw payloads

Your checkpoint

A module that both consumes and publishes a REST endpoint, with a documented error-handling matrix and a demo page showing success and failure states

Week 5

Security and Access Control

  • Configure module roles, entity access rules and attribute-level read/write rights and verify each with two test users

  • Apply the principle of least privilege by narrowing an existing broad role and confirm nothing breaks

  • Set up entity access that depends on an association with an XPath constraint

  • Prove that a restricted user cannot reach an unauthorized page via direct URL or microflow

Your checkpoint

A security matrix spreadsheet plus two demo user accounts whose behavior matches the matrix in a live test walkthrough

Week 6

Performance and Troubleshooting

  • Diagnose an N+1 style retrieval problem and fix it with an association-based retrieve or batched list operation

  • Add indexes and a denormalized field where justified, then measure the before/after of a list view

  • Deploy the debugger and logs to isolate a runtime error in a production-like environment

  • Reduce a page's client-side work by switching to pagination or a lazily loaded data source

Your checkpoint

A performance report with three measured before/after timings, the change made for each, and the client/server memory notes behind them

Week 7

Java Actions and Extensibility & Deployment, Environments and Version Control

  • Write a Java action that accepts an entity, returns a list and logs through the Mendix logging API

  • Handle exceptions in a Java action so failures surface as microflow errors instead of silent nulls

  • Manage a branch-and-merge cycle in version control, resolving a deliberate conflict

  • Configure environment constants and scheduled events, then promote a build to a second environment

Your checkpoint

A reusable Java action module plus a documented branch-merge-promote runbook validated by one real deployment to a test environment

Week 8

Domain Model and Data Structure & Microflows and Application Logic & Pages, UX and Client-Side Logic & Security and Access Control & Integrations, REST and Web Services & Java Actions and Extensibility & Deployment, Environments and Version Control & Performance and Troubleshooting

  • Retake a timed practice assessment and log every missed question by domain

  • Rebuild the two weakest topics from scratch without reference material

  • Refactor the week-2 microflow library to remove the technical debt identified during the course

  • Explain aloud the security and performance implications of your own app's design

Your checkpoint

A scored practice exam with a domain-by-domain gap list and a remediation note for every remaining weak area

Milestones

Week 2: You can build and debug a three-level microflow from a blank module in under 30 minutes without documentation

Week 4: A REST endpoint you published is consumed successfully by an outside tool, and your app handles a forced 500 response gracefully

Week 6: You have a measured performance improvement on a page or microflow, with before/after numbers recorded

Week 8: Practice exam score is at or above 80% with no single domain below 70%