Mendix Rapid Developer flashcards
Mendix Rapid Developer · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Studio Pro vs Developer Portal
- Studio Pro is the desktop IDE for building the app model; the Developer Portal is the web platform for team, environment, and app management. Both are needed across the app lifecycle.
- Consistency errors
- Model errors reported in the Errors pane that block running and deploying the app, such as a microflow with a missing return path or an unassigned page parameter.
- Module
- The unit of organization in a Mendix project; each module contains its own domain model, pages, microflows, nanoflows, and can be exported for reuse in other apps.
- Non-persistent entity
- An entity whose objects exist only in memory and are not stored in the database; used for transient form state or computed objects that do not need persistence.
- Association ownership
- The side of an association that stores the foreign key in the database; only the owner persists the link, and delete behavior is configured on the association.
- Delete vs Remove
- Delete cascades deletion of the referenced object when the owner is deleted; Remove only clears the reference and leaves the referenced object intact in the database.
- Calculated attribute
- An entity attribute whose value is computed by an expression or microflow rather than stored in the database; it is evaluated when the object is read.
- Generalization
- An inheritance relationship where a child entity inherits attributes and associations from a parent entity; the child can be retrieved and treated as the parent.
- Snippet
- A reusable UI fragment embedded in pages; changes to a snippet propagate to every page that uses it, reducing duplicated layout work across the app.
- Data view widget
- A page widget that displays a single object from a data source such as a microflow, XPath, or page parameter; input widgets inside it edit that object's attributes.
- Page parameter
- A typed input to a page passed when the page is opened, typically an entity object that provides the data context for widgets on that page.
- Pluggable widget
- A custom widget built with the Mendix Web Widget framework and added to the project; it must be compatible with the Studio Pro version in use.
- Microflow transaction
- Microflows run in a database transaction; objects are only persisted when committed, and an unhandled error rolls back the entire transaction.
- Nanoflow
- Client-side logic that runs in the browser or native app; it cannot use Java actions or commit to the database directly, but can call microflows on the server.
- Java action
- A microflow activity backed by custom Java code compiled into the app; it can access the Mendix Runtime API for logic not expressible in microflow activities.
- Error event
- A microflow element that catches errors and defines handling behavior, such as continuing, rolling back, or raising a custom error message to the user.
- Module role
- A permission set defined inside a module; it is mapped to user roles and controls entity, page, and microflow access for the users who receive it.
- Entity access rule
- A per-module-role rule granting create, read, write, or delete on an entity; an optional XPath constraint limits which objects the role can access.
- Anonymous user
- A user who accesses the app without logging in, enabled by allowing anonymous users in Project Security; the user receives the Anonymous user role.
- Production security level
- The security setting that enforces login and role-based access; Prototype/Demo does not enforce login and is intended only for early testing.
- Consumed REST call
- A microflow activity that calls an external REST endpoint with a URL, method, headers, and body, and maps the JSON response to Mendix entities or variables.
- Published REST operation
- A REST endpoint exposed by the app, backed by a microflow with a defined path, HTTP method, and request/response mapping; authentication is configurable.
- Import mapping
- A model element that translates JSON or XML into Mendix entities, supporting nested structures and inheritance; used with REST and SOAP integrations.
- Consumed SOAP service
- A service generated by importing a WSDL; the generated operations are called from microflows and the response is mapped to entities or variables.
- XPath association path
- A constraint segment of the form [Module.Association/Module.Target/Attribute = 'value'] that filters objects by a related object's attribute value.
- Validation rule
- An attribute-level rule such as required, unique, or range that is checked when an object is committed; a violation blocks the commit and raises an error.
- Event handler
- A microflow attached to an entity that runs before or after create, commit, or delete; it can raise an error to block the operation or modify related data.
- Validation feedback
- A microflow activity that displays a validation message on a bound input widget, informing the user which field failed validation and why.
- Environment
- An isolated deployment target with its own database and configuration; Mendix cloud offers Development, Acceptance, and Production environments with separate settings.
- Team Server branch
- A Git-based line of development on the Team Server; feature branches isolate work and must be merged into the main line before production deployment.
- Environment constant
- A named value used in the model whose actual value can be overridden per environment in the Developer Portal, keeping secrets and URLs out of the model.
- Feedback item
- A report submitted from the running app through the feedback widget, including page context and a screenshot; it appears in the Developer Portal for triage and conversion to a story.