I85PREP
⌘ K
Mendix Expert Developer study materials
Mendix Expert Developer study resources

Mendix Expert Developer practice questions

One question at a time. Build your Mendix Expert Developer understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Domain Modeling and Data Architecture

In a Mendix domain model, which element is used to persist data in the underlying database?

  1. A microflow variable
  2. A persistent entity Correct answer.
  3. A non-persistent entity
  4. An association

Explanation

Only persistent entities are mapped to database tables and survive application restarts. Non-persistent entities exist only in memory, and associations and variables are not tables themselves.

Question 2Domain Modeling and Data Architecture

Which attribute data type in Mendix is best suited for storing a monetary amount that requires exact arithmetic?

  1. Decimal Correct answer.
  2. Long
  3. Float
  4. Integer

Explanation

Decimal is backed by a precise decimal type and is recommended for currency and other values where rounding errors are unacceptable. Float uses floating-point representation and can introduce rounding drift.

Question 3Domain Modeling and Data Architecture

What does the owner side of an association determine in a Mendix domain model?

  1. Which module the association is exported to
  2. Which entity is always the parent in a generalization
  3. Which entity stores the reference to the other entity in the database Correct answer.
  4. Which user role may read the associated object

Explanation

The owner side is the entity whose table holds the foreign key referencing the other entity. In a one-to-many association the 'one' side owns the reference, which is why the direction matters for queries and database structure.

Question 4Domain Modeling and Data Architecture

A developer needs to model a relationship where one Order can contain many OrderLines and each OrderLine belongs to exactly one Order. Which association configuration expresses this?

  1. A one-to-many association from Order to OrderLine Correct answer.
  2. A one-to-one association from Order to OrderLine
  3. A generalization from OrderLine to Order
  4. A many-to-many association between Order and OrderLine

Explanation

A one-to-many association with multiplicity one on Order and many on OrderLine exactly matches the requirement. Many-to-many would allow a line to belong to multiple orders, and one-to-one would restrict each order to a single line.

Question 5Domain Modeling and Data Architecture

Which statement about a generalization relationship in the Mendix domain model is correct?

  1. An entity can generalize from multiple parent entities at once
  2. A generalization can only be created between entities in different modules
  3. A specialized entity must redeclare all attributes of its generalization
  4. A specialized entity inherits the attributes and associations of its generalization Correct answer.

Explanation

Generalization in Mendix is single inheritance: the child entity inherits attributes, associations, and access rules from its parent. Multiple inheritance is not supported, and entities in the same module can generalize each other.

Question 6Domain Modeling and Data Architecture

What is the primary purpose of a non-persistent entity in a Mendix domain model?

  1. To enforce referential integrity between two tables
  2. To hold data in memory for calculations or temporary UI state without database storage Correct answer.
  3. To store system attributes such as createdAt automatically
  4. To create a database view that joins two persistent entities

Explanation

Non-persistent entities are useful for transient objects such as search criteria, calculation results, or helper objects passed between microflows. They are never written to the database and have no table.

Question 7Domain Modeling and Data Architecture

An entity has an attribute named 'Email' of type String with a validation rule requiring a valid email format. Where is this validation rule configured?

  1. In the project settings runtime tab
  2. In the navigation profile settings
  3. In the module security access rules
  4. On the attribute in the domain model properties Correct answer.

Explanation

Attribute validation rules such as required, unique, and regular expression patterns are configured in the attribute properties in the domain model. These rules are enforced by the runtime when objects are committed.

Question 8Domain Modeling and Data Architecture

A developer marks an attribute as 'unique' in the domain model. What behavior does the Mendix runtime enforce?

  1. The attribute value is automatically generated for each new object
  2. The attribute is excluded from the database and stored in memory
  3. Committing an object whose value duplicates an existing value in that attribute fails Correct answer.
  4. The attribute becomes the primary key of the entity table

Explanation

The unique constraint is enforced at commit time by the runtime, which raises an error if a duplicate value already exists. It does not replace the internal ID as primary key, nor does it auto-generate values.

Question 9Domain Modeling and Data Architecture

Which attribute type should be used to store a value that is automatically incremented for each new object, such as an invoice number?

  1. Integer
  2. String
  3. Long
  4. AutoNumber Correct answer.

Explanation

AutoNumber is a Mendix-specific type that assigns a unique, increasing number when an object is created. Integer, Long, and String require the developer to compute and assign values manually.

Question 10Domain Modeling and Data Architecture

Which statement describes the difference between an association and an entity in the Mendix domain model?

  1. An association is always persistent, while an entity is always non-persistent
  2. An association can have attributes, while an entity cannot
  3. An association represents a relationship between entities, while an entity represents a data object Correct answer.
  4. An association stores attributes, while an entity stores only references

Explanation

Entities are the nouns of the domain model and hold attributes; associations are the verbs connecting entities and hold the reference. Neither can swap these roles, though associations may themselves carry attributes in Mendix.

Question 11Domain Modeling and Data Architecture

What happens to the underlying database column when an attribute is deleted from a persistent entity in the domain model?

  1. The column is moved to a backup table automatically
  2. The column is dropped during the next deployment synchronization Correct answer.
  3. The column is renamed to a system default name
  4. The column remains and is reused by the next attribute created

Explanation

Mendix synchronizes the database schema with the domain model at deployment, removing columns for deleted attributes. Data in that column is lost, so developers should migrate data before removing attributes in production.

Question 12Domain Modeling and Data Architecture

Which entity access setting allows a user role to create new objects of an entity but not read existing ones?

  1. Create rights granted without read rights Correct answer.
  2. Write rights granted without create rights
  3. Read rights granted without create rights
  4. Delete rights granted without read rights

Explanation

Entity access rules separate create, read, write, and delete rights, so a role can be allowed to create objects while being denied read access. This pattern is used for anonymous submissions such as contact forms.

Question 13Domain Modeling and Data Architecture

A developer wants to restrict which objects a user can retrieve based on an XPath constraint tied to the user's identity. Where is this configured?

  1. In the page's data source properties
  2. In the module's dependencies list
  3. In the microflow's error handling settings
  4. In the XPath constraint of the entity access rule Correct answer.

Explanation

Entity access rules support an XPath constraint that filters which objects a role may access, and it can reference the current user via tokens such as [%CurrentUser%]. This enforces row-level security at the runtime level.

Question 14Domain Modeling and Data Architecture

Which statement about many-to-many associations in Mendix is correct?

  1. They require the developer to create an explicit intermediate entity
  2. They store the relationship as a comma-separated list in one column
  3. They cannot be used with persistent entities
  4. They are implemented with a separate join table managed by the runtime Correct answer.

Explanation

Mendix implements a many-to-many association using an internal join table, so no explicit intermediate entity is needed. If the relationship itself needs attributes, the developer may instead model an explicit entity.

Question 15Domain Modeling and Data Architecture

What is the effect of setting an association's delete behavior to 'cascade'?

  1. Deleting the owning object also deletes the associated objects Correct answer.
  2. Deleting the associated object also deletes the owning object
  3. The association is removed from the domain model at runtime
  4. The associated objects are moved to a recycle bin

Explanation

Cascade delete removes the child objects when the parent is deleted, which prevents orphaned records. The reverse direction is not implied and must be modeled separately if needed.

Question 16Domain Modeling and Data Architecture

A developer needs to enforce that every Order object has a non-null reference to a Customer. Which construct provides this?

  1. A one-to-many association with multiplicity one on the Order side Correct answer.
  2. A generalization from Order to Customer
  3. A many-to-many association between Order and Customer
  4. A non-persistent entity for Customer

Explanation

Setting the association multiplicity so that each Order references exactly one Customer enforces the cardinality at the model level. Many-to-many would allow zero or many customers, and generalization models inheritance, not references.

Question 17Domain Modeling and Data Architecture

Which statement about system attributes such as createdAt and changedBy is correct?

  1. They are maintained automatically by the runtime when an object is committed Correct answer.
  2. They exist only on non-persistent entities
  3. They must be updated manually in every microflow that commits an object
  4. They can be edited by end users through the default form

Explanation

Mendix system attributes are populated by the runtime at commit time, recording creation and modification metadata. Developers do not need to set them and should not rely on users editing them.

Question 18Domain Modeling and Data Architecture

A developer wants to calculate a derived value that depends on several attributes of the same entity without storing it. Which approach fits the Mendix domain model?

  1. Create a non-persistent entity for each calculation
  2. Define a calculated attribute using an expression or microflow Correct answer.
  3. Create a persistent attribute and populate it in every microflow
  4. Add a system attribute for the derived value

Explanation

Calculated attributes compute a value on retrieval using an expression or microflow, so the result is never stored. This avoids redundant data and keeps the derived value consistent with its inputs.

Question 19Domain Modeling and Data Architecture

What is the purpose of the 'owner' property on an association when the association itself has attributes?

  1. It determines which entity is displayed first in the form
  2. It controls which module the association belongs to
  3. It determines which side stores the association attributes in the join table Correct answer.
  4. It decides whether the association is persistent

Explanation

When an association carries attributes, the owner determines where those attribute values are stored, typically in the join table or on the owning entity. This affects queries and how the data is retrieved.

Question 20Domain Modeling and Data Architecture

A developer creates a generalization where both parent and child are persistent. How is the data stored in the database?

  1. The parent table stores a copy of every child attribute
  2. The child entity is stored only in memory until explicitly committed to the parent
  3. All attributes of parent and child are stored in a single table
  4. The child entity has its own table containing only its own attributes, joined to the parent table Correct answer.

Explanation

Mendix uses a table-per-entity strategy for generalization, so the child table holds its own attributes and references the parent table via the inherited ID. Retrieving a child joins the parent to assemble the full object.

Question 21Domain Modeling and Data Architecture

Which statement about indexing in the Mendix domain model is correct?

  1. Indexes can be defined on attributes to improve retrieval performance for frequent queries Correct answer.
  2. Indexes can only be defined on associations
  3. Indexes are managed solely by the database administrator outside Mendix
  4. Indexes are created automatically for every attribute

Explanation

Developers can mark attributes as indexed in the domain model, and the runtime creates the corresponding database index. This is useful for attributes frequently used in XPath constraints and sorting.

Question 22Domain Modeling and Data Architecture

What does the 'event' property on a persistent entity allow a developer to do?

  1. Schedule a recurring microflow at a fixed interval
  2. Trigger a microflow before or after an object is committed or deleted Correct answer.
  3. Define a database trigger that runs on every query
  4. Attach a custom Java action to a page

Explanation

Entity events let you bind a microflow to commit, create, or delete operations, enabling logic such as auditing or validation. They run as part of the runtime's persistence lifecycle.

Question 23Domain Modeling and Data Architecture

A developer needs to share an entity across several modules while keeping a single definition. Which approach is appropriate?

  1. Copy the entity into each module and synchronize manually
  2. Define the entity once in a module and reference it from other modules via module dependencies Correct answer.
  3. Create a separate non-persistent entity in each module
  4. Use a generalization from each module to a local copy

Explanation

Mendix modules can depend on each other, allowing entities defined in one module to be used elsewhere without duplication. This keeps a single source of truth and avoids schema divergence.

Question 24Domain Modeling and Data Architecture

Which statement about the relationship between domain model entities and database tables is accurate?

  1. Each persistent entity maps to its own table, with columns for its attributes Correct answer.
  2. Entities map to tables only when they have associations
  3. Non-persistent entities also create tables for caching
  4. All persistent entities in a module share one table

Explanation

Mendix creates one table per persistent entity, with a column per attribute plus the internal ID. Associations add foreign keys or join tables, and non-persistent entities have no table at all.

Question 25Domain Modeling and Data Architecture

A developer wants to prevent orphaned child objects when a parent is removed but does not want the deletion to cascade automatically. Which delete behavior should be configured?

  1. Set the association to a many-to-many multiplicity
  2. Set the association to prevent deletion of the parent while children exist Correct answer.
  3. Set the association to no delete behavior at all
  4. Set the association to cascade delete

Explanation

Mendix allows an association to block deletion of the parent when associated objects exist, forcing the developer to handle children explicitly. This avoids silent data loss while preserving referential integrity.

Question 26Domain Modeling and Data Architecture

A domain model contains entity Customer with a specialization named PremiumCustomer. PremiumCustomer adds an attribute Discount of type Decimal. A developer writes a microflow that retrieves Customer objects. Which objects does the retrieve return?

  1. All Customer objects including PremiumCustomer objects, since a specialization inherits the parent's identity Correct answer.
  2. Only objects of exactly Customer, because specializations are stored in separate tables
  3. Only PremiumCustomer objects, because the specialization overrides the parent's retrieval behavior
  4. Neither, because an abstract parent cannot be retrieved directly in a microflow

Explanation

A specialization in Mendix extends the parent entity, so every PremiumCustomer is also a Customer and is returned when the parent is retrieved. The runtime treats the specialization as a subtype of the generalized entity, which is why inherited attributes and associations are available on those objects.

Question 27Domain Modeling and Data Architecture

A domain model has entity Invoice with a calculated attribute Total that sums the Amount values of its associated InvoiceLine objects. The developer wants Total to appear in the client without storing it in the database. Which Mendix construct should be used?

  1. An auto-number attribute that is recalculated whenever the object is committed
  2. A persistent attribute with a default value expression
  3. A calculated attribute defined with an expression over the associated objects Correct answer.
  4. A non-persistent entity that mirrors the Invoice and is refreshed on every page load

Explanation

Calculated attributes are defined in the domain model with an expression and are evaluated at runtime, so the value is derived from associated data without occupying a database column. Persistent attributes persist values, and auto-number attributes generate identifiers rather than computing sums.

Question 28Domain Modeling and Data Architecture

A developer wants to validate that a Customer's DateOfBirth is in the past before any object is committed, and the rule must apply regardless of which page or microflow creates the object. Assuming every Customer commit has events enabled, where should the rule be implemented?

  1. As a client-side condition on the input widget in each page
  2. As a before-commit event handler that compares DateOfBirth with the current time and returns false for invalid values Correct answer.
  3. As an access rule on the Customer entity for the relevant module roles
  4. As a validation rule on the DateOfBirth attribute in the domain model

Explanation

A before-commit handler can compare DateOfBirth with the current date and time and return false when the value is not in the past, preventing the commit. With events enabled on every Customer commit, the same check runs regardless of the page or microflow creating the object.

Question 29Domain Modeling and Data Architecture

Two modules each define a different entity named Address. A microflow in module Sales needs to use the Address entity defined in module Common. What is the correct way to reference it?

  1. Import the entity into Sales so a duplicate definition is created locally
  2. Use the unqualified name Address, because entity names are resolved globally
  3. Qualify the reference with the module name, for example Common.Address Correct answer.
  4. Rename the Sales entity so both modules share the same name

Explanation

Entities are scoped to their module, so a reference from another module must use the fully qualified Module.Entity name. Creating a duplicate or renaming does not point to the original definition and breaks the single source of truth.

Question 30Domain Modeling and Data Architecture

A persistent entity Order has a one-to-many association to OrderLine with delete behavior set to cascade. A developer deletes an Order through an object activity in a microflow. Which outcome occurs?

  1. The Order is marked deleted while the OrderLines are committed unchanged
  2. The Order is deleted and the associated OrderLine objects are deleted as well Correct answer.
  3. The Order is deleted and each OrderLine is retained with a null reference to the Order
  4. The deletion fails because child objects still reference the parent

Explanation

Cascade delete behavior means the runtime removes the child objects when the parent is deleted, preventing orphaned records. This is enforced by the runtime during the delete, so the associated lines do not survive the parent.

Question 31Microflows and Application Logic

In a Mendix microflow, which activity type allows you to pause execution at a defined point and continue later after an external event, while keeping the microflow's state persisted?

  1. A decision activity with an expression
  2. A call activity configured with a Java action
  3. A loop with a break condition
  4. A wait activity Correct answer.

Explanation

Wait activities suspend a running microflow and persist its state, so execution can resume later when a timer expires or when a signal is sent to the waiting microflow. Decisions, loops, and call activities all execute synchronously within the same run and never suspend the flow.

Question 32Microflows and Application Logic

A developer wants a microflow to run automatically when an object of entity Order is committed to the database. Which Mendix mechanism should be configured?

  1. A database synchronization rule
  2. A microflow timer widget placed on the Order page
  3. An event handler on the entity with a before-commit microflow Correct answer.
  4. A scheduled event on the Order entity

Explanation

Entity event handlers in the domain model let you attach a microflow to before-commit, after-commit, before-create, or before-delete events for that entity. Scheduled events run on a time schedule rather than on object commits, and widgets are UI-scoped.

Question 33Microflows and Application Logic

In a microflow, an object is changed and then passed to a sub-microflow that only reads its attributes. The sub-microflow does not commit. What happens to the changed values when the parent microflow finishes without committing?

  1. The changes are automatically persisted when the parent microflow completes.
  2. The changes are discarded immediately when the sub-microflow ends.
  3. The changes are rolled back to the last committed state at the end of the request. Correct answer.
  4. The changes persist in memory for the session but are never written to the database.

Explanation

Mendix only writes to the database on an explicit commit; uncommitted changes exist in the runtime's object state and are rolled back at the end of the request or when the object is garbage-collected. Passing an object to a sub-microflow does not implicitly commit it.

Question 34Microflows and Application Logic

Which expression correctly tests whether the string attribute Name is empty or contains only whitespace in a Mendix microflow expression?

  1. length($Order/Name) = 0
  2. $Order/Name = empty
  3. $Order/Name = null
  4. trim($Order/Name) = '' Correct answer.

Explanation

The trim() function strips leading and trailing whitespace, so comparing the trimmed value to an empty string catches both null-free empty strings and whitespace-only values. A plain length check misses whitespace-only strings, and 'empty' is not a Mendix expression keyword.

Question 35Microflows and Application Logic

A microflow must iterate over a list of OrderLine objects and accumulate the sum of their LineTotal attributes. Which construct is the idiomatic Mendix approach?

  1. A retrieve activity with an XPath sum constraint
  2. A wait activity combined with a timer
  3. A loop activity with a total variable updated by a change-variable activity Correct answer.
  4. A decision activity nested inside a call activity

Explanation

A loop activity iterates over the list, and a change-variable activity inside the loop increments an accumulator each iteration. XPath cannot compute sums, and decisions or wait activities do not iterate collections.

Question 36Microflows and Application Logic

When a microflow retrieves a list of Customer objects using an XPath constraint, which statement about the result is accurate?

  1. The retrieve activity always returns a single object even if multiple match.
  2. The XPath constraint is evaluated only after all objects are loaded into memory.
  3. The list is a copy of the objects and changes to it do not affect the database until committed.
  4. The retrieved list is a reference to the objects in the runtime cache, so attribute changes are visible to other microflows in the same request. Correct answer.

Explanation

Mendix retrieves references to objects held in the runtime's object state, so changes made to those objects are visible to other logic in the same request before commit. Persistence to the database still requires an explicit commit.

Question 37Microflows and Application Logic

A developer needs to return a value from a microflow to its caller. Which microflow property must be configured?

  1. The microflow's scheduled event interval
  2. The return type set in the microflow's properties Correct answer.
  3. The 'apply entity access' setting
  4. The 'commit' option in the end event

Explanation

A microflow's return type is defined in its properties, and the end event must supply an expression matching that type. Apply-entity-access and commit settings do not define return values.

Question 38Microflows and Application Logic

In a microflow, a variable named $Count is declared as an Integer. A developer assigns the result of a division expression 7/2 to it. What is the resulting value in Mendix expressions?

  1. 4
  2. An error is raised because division of integers is not allowed
  3. 3.5
  4. 3 Correct answer.

Explanation

Mendix integer division truncates toward zero, so 7/2 evaluates to 3 when assigned to an Integer variable. To obtain 3.5 the operands must be decimals, for example 7.0/2.

Question 39Microflows and Application Logic

Which activity should be used to deliberately raise a validation error that stops microflow execution and surfaces a message to the user?

  1. A change-variable activity setting an error flag
  2. A log activity at the info level
  3. A validation feedback activity Correct answer.
  4. A continue event

Explanation

Validation feedback activities attach a message to an object's attribute or association and mark the object as invalid, halting the flow and showing the message in the client. Log activities record information but do not stop execution.

Question 40Microflows and Application Logic

A microflow calls a Java action that throws an exception. How should the calling microflow handle this to present a friendly message to the user?

  1. Wrap the call in a loop that retries until it succeeds
  2. Set the microflow's return type to String and return the exception text
  3. Rely on the default behavior, which automatically shows the exception message to the user
  4. Configure error handling on the call activity with a custom error handler and show a message activity Correct answer.

Explanation

Call activities can be configured with custom error handling that routes to an error handler path, where a show-message or validation activity can present a friendly message. Default behavior shows a generic error page, not a tailored message.

Question 41Microflows and Application Logic

A microflow needs to create a new object of entity Invoice and set its Number attribute before committing. Which sequence of activities is correct?

  1. Commit Invoice, create Invoice, change Number
  2. Create Invoice, change Number, commit Invoice Correct answer.
  3. Change Number, create Invoice, retrieve Invoice
  4. Retrieve Invoice, change Number, commit Invoice

Explanation

Creating an object produces an in-memory instance; the change activity then sets its attributes, and a commit activity persists it. Committing before creating is impossible because no object exists yet.

Question 42Microflows and Application Logic

What distinguishes a microflow from a nanoflow in Mendix?

  1. Nanoflows run client-side and cannot use certain activities such as commit or call-web-service. Correct answer.
  2. Microflows run client-side while nanoflows run server-side.
  3. Microflows cannot call sub-microflows.
  4. Nanoflows can only contain decision activities.

Explanation

Nanoflows execute in the browser (client-side) and therefore cannot perform server-only operations like committing objects or calling web services. Microflows run server-side and support the full activity set.

Question 43Microflows and Application Logic

A developer wants a microflow to execute asynchronously so that the user interface is not blocked. Which configuration achieves this?

  1. Set the microflow's 'Asynchronous' property to true Correct answer.
  2. Add a wait activity at the start of the microflow
  3. Call the microflow from a nanoflow
  4. Place the microflow in a scheduled event

Explanation

Microflows expose an 'Asynchronous' property; when enabled, the microflow runs in the background and the caller is not blocked. Wait activities suspend execution but do not make the call asynchronous from the caller's perspective.

Question 44Microflows and Application Logic

Which statement about the 'apply entity access' setting on a microflow is correct?

  1. It enforces entity access rules for objects retrieved and changed by the microflow. Correct answer.
  2. It disables XPath constraints in retrieve activities.
  3. It grants all users full access to entities used in the microflow.
  4. It only affects nanoflows, not microflows.

Explanation

When 'apply entity access' is enabled, the microflow is subject to the entity access rules defined in the domain model, restricting what it can read or write. Disabling it allows the microflow to bypass those rules, typically for system-level logic.

Question 45Microflows and Application Logic

A microflow iterates over a list and, under a certain condition, must skip the remaining activities in the current iteration and proceed to the next item. Which activity accomplishes this?

  1. A return activity
  2. A break event
  3. A continue event Correct answer.
  4. An end event

Explanation

A continue event inside a loop skips the rest of the current iteration and moves to the next item. A break event exits the loop entirely, and an end event terminates the microflow.

Question 46Microflows and Application Logic

Which Mendix expression function is appropriate for formatting a date attribute into a readable string using a specified pattern?

  1. formatDateTime() Correct answer.
  2. toStringDate()
  3. dateFormat()
  4. parseDateTime()

Explanation

formatDateTime() converts a date/time value into a string using a format pattern such as 'dd MMM yyyy'. parseDateTime() performs the reverse conversion from string to date.

Question 47Microflows and Application Logic

A developer needs to retrieve objects from an association rather than by a database query. Which retrieve source should be selected in the retrieve activity?

  1. From database with an XPath constraint
  2. By association Correct answer.
  3. By a microflow return value
  4. From a Java action

Explanation

The 'by association' retrieve source follows an association from a known object to its related objects, avoiding a database query. XPath retrieval queries the database directly.

Question 48Microflows and Application Logic

When a microflow commits an object with the 'with events' option enabled, what is the effect?

  1. The object is deleted after commit.
  2. The object is committed without validation.
  3. The commit is performed asynchronously.
  4. Event handlers configured on the entity are triggered during the commit. Correct answer.

Explanation

Committing 'with events' triggers the entity's before-commit and after-commit event handler microflows. Committing without events skips those handlers, which is useful when events would cause recursion.

Question 49Microflows and Application Logic

A microflow must call a REST service and process the JSON response. Which activity type is used to invoke the REST call within the microflow?

  1. A validation feedback activity
  2. A retrieve activity with an XPath constraint
  3. A call REST activity configured with a request and response mapping Correct answer.
  4. A change-variable activity

Explanation

The call REST activity sends an HTTP request and maps the response into Mendix objects or variables. Retrieve activities operate on the local database, not external REST endpoints.

Question 50Microflows and Application Logic

In a microflow, what is the effect of the 'refresh in client' option on a change activity?

  1. It instructs the client to refresh widgets bound to the changed object so the UI reflects the new value. Correct answer.
  2. It reloads the microflow's variables from the database.
  3. It immediately commits the changed object to the database.
  4. It triggers all event handlers on the entity.

Explanation

'Refresh in client' tells the browser to update widgets bound to the changed object, so users see the new value without a manual refresh. It does not commit the object or trigger event handlers.