Mendix Intermediate Developer case studies
Mendix Intermediate Developer · Put your knowledge to work in context.
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 case studies are 5 cases and about 3,890 words.
1Recreating the rental order model after go-live
A rental company's Mendix app stores orders in an Order entity. Each Order carries CustomerName and CustomerEmail as strings copied from the selected Customer at creation, plus NetTotal, which a microflow recalculates by looping the order's OrderLines every time the order is saved.
728 words, about 4 min2The nightly price import that melts the container
A nightly scheduled event imports a supplier price file. The microflow retrieves a FileDocument, parses roughly 90,000 CSV lines into PriceRow objects, and for every line creates the object and runs a Commit with events enabled.
809 words, about 4 min3A 70,000-row ticket overview that takes twelve seconds
An internal service desk app has a ticket overview page. Its list view uses a microflow data source that retrieves all Tickets (about 70,000), sorts them with a List Operation activity, and returns the list; the page takes 12 seconds in acceptance.
764 words, about 4 min4The partner REST service that shipped without authentication
A customer portal runs on Mendix Cloud with production security. Module roles are Employee and Customer.
794 words, about 4 min5NoClassDefFoundError after deploying the PDF Java action
A Java action wraps a third-party PDF library to merge invoice PDFs. The developer dropped the JAR into the project's userlib folder and wrote the action with a list of FileDocuments as parameter and String as return type.
795 words, about 4 min