Mendix Intermediate Developer key terms

A definition of a type of data the app stores, drawn in the domain model. It groups attributes that describe one object and associations that link it to other objects.

A single named property on an entity, such as a name, date, or amount. Its data type decides how values are validated, stored, and offered as widgets on pages.

A link defined between two entities that lets objects refer to each other. Its kind (reference or reference set) and owner determine how many objects can be connected and which side can change the link.

An inheritance link where a child entity inherits the attributes, associations, and access rules of a parent entity, so logic and pages written for the parent also accept the child.

Built-in attributes that Mendix adds to stored entities - created date, changed date, owner, and changed by - recording who touched an object and when, without the developer defining them.

Logic attached to an entity that runs automatically before or after objects are created, committed, or deleted, used to enforce rules and set values consistently regardless of where the change happens.

A setting on an association that decides what happens to linked objects when one side is removed: keep the related object, delete it too, or block the deletion.

Visual server-side logic that runs in the runtime, can retrieve and change data, call services and other flows, and return a value. It is the main place for business rules.

Logic that runs in the user's browser rather than on the server. It reacts quickly and can handle simple client-side tasks, but data access is limited and it often calls a microflow for real work.

A microflow that is called from another microflow to reuse a block of logic. It declares its own inputs and return value, so callers just pass data in and use the result.

A microflow element that checks one or more conditions and sends the flow down exactly one matching path, with an optional else path when nothing matches.

Per-activity settings and error events that decide what happens when an activity fails: show a message, roll back changes, or let the error travel up to the caller.

An activity that saves changed objects to the database permanently. Until an object is committed, its changes stay in memory and can be lost or rolled back.

An activity that loads objects from the database or from the current context, for example by following an association or by applying a constraint on the entity.

A filter written in XPath syntax that limits which objects a retrieve returns, comparing attributes, following associations, and calling functions such as contains or length.

The unit of the user interface, built from widgets in the page editor and shown to users through navigation or opened from logic. A page can accept parameters and be reused.

A reusable frame for pages that holds shared parts such as a header, menu, and content placeholder, so every page using it keeps the same structure.

A widget that shows one object and passes it down as context to the widgets inside it, so nested fields and buttons act on that same object.

A widget that shows a collection of objects and repeats its inner content for each item, usually with sorting, paging, and selection built in.

The object or list a widget receives from its parent and works on. Nested widgets inherit it, which is why a button inside a data view automatically knows its object.

A widget property that shows or hides the element based on an expression, a microflow, or a rule, letting one page serve different users, states, or roles.

A role defined inside one module that collects access to that module's entities, microflows, and pages. It only grants access once it is linked to an app user role.

An application-wide role given to users or to module roles. It defines which modules a person can use and, together with module roles, what they may do there.

Per-role rules that allow or deny creating, reading, updating, and deleting objects of an entity, plus an optional constraint that limits which objects the role can see.

Per-role settings on an entity attribute that mark it readable, writable, or hidden, so sensitive fields stay protected even if a page tries to display them.

An app setting that chooses between no security, prototyping security with demo users, or production security where every access check is enforced strictly at runtime.

The microflow activity that sends an HTTP request to an outside service and returns the response, with settings for method, URL, headers, body, authentication, and timeouts.

A mapping that reads an incoming JSON or XML message and creates or updates Mendix objects, stating which message elements fill which entity attributes and associations.

A mapping that builds an outgoing JSON or XML message from Mendix objects, stating how entities and attributes appear as elements in the message.

A REST API that the Mendix app offers to other systems, defined by resources, operations, and paths, with request and response handling built from microflows and mappings.

Custom logic written in Java that microflows can call like any other activity. It declares parameters and a return type and is compiled into the app when deployed.

The set of Java classes that give custom code access to the runtime, letting it read and change objects, run microflows, and work with the current context and user.

A separate running copy of the app, such as development, acceptance, or production. Each has its own database, constants, and access settings, and is fed by a deployment package.

A named setting defined in the model, like a service URL or API key, whose value can be changed per environment without rebuilding or redeploying the app.

The compiled build of the app created from a chosen version and sent to an environment, where it is started against that environment's database and constants.

The repository that stores the app model and every change made to it, letting developers commit, update, branch, and roll back. Mendix Team Server or a Git server holds it.

A database structure built on one or more attributes that makes searching and sorting faster. It speeds up reads but costs storage and slows down writes.

Messages the runtime writes with a level such as trace, debug, info, warning, or error. Setting levels per environment helps find the cause of errors and slow requests.

A marker set on a microflow activity that pauses execution in Studio Pro so the developer can inspect variables and step through the flow while the app runs.