Mendix Intermediate Developer study guide
Mendix Intermediate Developer · Work through your exam, one topic at a time.
The Mendix Intermediate Developer credential is a vendor certification aimed at low-code developers who have moved past their first app and now build multi-module applications on their own: modelling entities and associations, wiring microflows and page logic, applying role-based security, and connecting to external systems. It sits between entry-level familiarity with Studio Pro and advanced specialisation, and employers typically read it as evidence that a developer can be trusted with a production application without constant supervision. The Mendix Intermediate Developer study guide has 8 sections and about 2,555 words.
01Domain Model and Data Structure
The domain model is the contract that pages, microflows, security and integrations all rely on. Persistable entities are stored in the database; non-persistable entities live only in memory (typical for helper objects behind a page or objects passed to a Java action).
318 words, about 2 min02Microflows and Application Logic
Microflows run on the runtime (server side); nanoflows run in the client (browser or native app), which makes them the right choice for page logic such as on-change handlers, visibility expressions and offline behaviour. Nanoflows have a deliberately reduced activity set: no Java action calls, no commit-event triggers, no scheduled events.
321 words, about 2 min03Pages, UX and Client-Side Logic
A page consists of a layout with placeholders and widgets placed inside them. Data widgets - data view, list view, data grid 2, gallery, template grid - need a context: a page parameter, a surrounding widget, or a data source (database retrieve, microflow, nanoflow, association).
354 words, about 2 min04Security and Access Control
Mendix security has three layers: module roles (defined per module, the unit of authoring), user roles (combinations of module roles assigned to end users), and the access rules attached to each modellable document. For every entity, entity access rules grant create, read, write and delete per module role, optionally with member-level read/write and an XPath constraint that limits which rows the role can see.
320 words, about 2 min05Integrations, REST and Web Services
Consuming an API in Mendix usually starts with a consumed REST service document, created from an OpenAPI/Swagger file or defined by hand, or with a Send REST request activity inside a microflow. Responses arrive as strings, or are translated through a JSON/XML structure with an import mapping; export mappings do the reverse, turning entities into a structure that is then serialized.
315 words, about 2 min06Java Actions and Extensibility
A Java action is declared in the model and implemented in a .java file under javasource/. The generated class extends UserAction, receives its parameters as instance fields assigned in the constructor, and implements executeAction(); a generated static overload lets microflows invoke it with an IContext plus the parameters.
311 words, about 2 min07Deployment, Environments and Version Control
Studio Pro stores the model in a .mpr file plus document files, tracked by version control (Git, typically on Mendix Team Server). Commit pushes your changes as a revision, update pulls others' work, and conflicts must be resolved before committing.
293 words, about 1 min08Performance and Troubleshooting
Performance work in Mendix is mostly about what reaches the database and what reaches the browser. On the server: XPath constraints on unindexed attributes, retrieves without a range that load thousands of objects into memory, retrieve-in-a-loop patterns, and microflows that commit per object instead of once.
323 words, about 2 min