Mendix Rapid Developer study materials
Mendix Rapid Developer study resources

Mendix Rapid Developer: Mendix Platform and Studio Pro Fundamentals

Mendix Rapid Developer · Work through your exam, one topic at a time.

All guide sections

Mendix Platform and Studio Pro Fundamentals

This domain checks that you know where things live in the Mendix toolchain: the Portal, Studio Pro, the runtime, and how a project is split into modules and documents. Questions are mainly about structure, terminology, and which tool owns which responsibility.

The pieces

  • Mendix Portal – project and team management, Team Server, environments and deployment controls, Marketplace, backlog.
  • Studio Pro – the desktop IDE where you edit the domain model, pages, microflows, security and integrations. The older browser-based Mendix Studio has been retired, so modeling now happens in Studio Pro.
  • Runtime – executes the model directly. Behaviour you model is interpreted at runtime; Java actions extend it only where built-in activities fall short.
  • Marketplace – downloadable modules and widgets that you import into a project and then maintain as your own content.

Project structure

A project contains modules; a module contains documents plus exactly one domain model. Typical documents: domain model, pages, microflows, nanoflows, layouts, snippets, enumerations, scheduled events, REST services. Module roles belong to a module; project-wide items such as constants, navigation and the security level belong to the project.

Worked example

A colleague asks where to add an app-wide company logo. Reasoning: the logo appears on every page, so it is page chrome, not page content - it belongs in a layout (or in a snippet used by the layout), not copied into each page. If instead only three pages need a legal footer, a snippet referenced from those pages avoids duplicating the markup and keeps future edits in one place.

Traps

  • Documents are always added inside a module; the Project Explorer right-click menu is the normal route.
  • Constants are defined in a module but their values can be overridden per environment in the Portal.
  • Module roles are authorization objects; app roles are what an end user is actually assigned. Do not merge the two in your head.
  • Marketplace content is third-party code: review it like your own before shipping.