Agentische Anwendungen und Orchestrierung

Erhöhen Sie Ihre Mendix workflows: introducing the Notification Event

Get ready to unlock a new level of responsiveness and flexibility in your Mendix applications! From the BPMN standard we are adding the Intermediate Message Events to our workflow capabilities in the form of the Notification Event. This new functionality is the way to build even more dynamic, event-driven processes with ease.

Have you ever wished your workflow could pause and wait for a specific event before moving forward, or react to an external message or event while an activity is still running, without having to build complex workarounds? With the Notification Event, both are now possible!

Here’s how it will transform your workflow design:

• As a normal/inline event: Embed it directly within your workflow path to introduce intelligent waiting points as a lighter, alternative to the Wait for Notification Activity. This ensures your process only advances when a specific notification is received, perfect for orchestrating complex sequences that depend on external system confirmations, user actions, or data updates.
  • For example: waiting for a payment gateway’s success, or holding until a third-party API callback is received before proceeding.
• As a Boundary Event: Attach it directly to an activity to create robust exception handling or dynamic process steering. Depending on your needs, it can be configured as interrupting (cancelling the current activity and redirecting the flow) or non-interrupting (branching off into a parallel path while the original activity continues). This gives you precise control over how your workflow reacts to an incoming external trigger mid-task.
  • For example: catching a cancellation request while an approval task is still in progress, immediately redirecting the flow.

The Notification Event opens up many new possibilities for creating truly reactive and resilient applications that respond intelligently to real-world events.

Ready to discover how the Notification Event can elevate your Mendix solutions? Read more in our Dokumentation.

Introducing Build and Playground views in the Agent Editor

The latest release of the Agent Editor brings a cleaner, more focused experience by splitting the editor into two dedicated views: Bauen , Spielplatz. The Build view keeps you focused on what matters when designing your agent — configuring its type, model, prompts, and tools, without the distraction of test controls.

When you’re ready to test, switch to the Playground view, where everything you need to run and evaluate your agent is right at hand. The Playground now also replaces your system and user prompts with your configured variable values, so you can see exactly what the agent will receive.

Fast reloads for agents

Agents now support instant reloads, significantly reducing the app startup time after modifying an agent document. This translates to a much smoother and faster development process, making it easier than ever to iterate on your agents.
Bam! Your agent just reloaded faster than it took to read this section!

Agentische Entwicklung

AI-powered theming with Maia

Transforming your app’s entire look and feel is now as simple as having a conversation. Maia can now read and modify your application’s theme, turning design specifications into working CSS.

From design to theme in seconds

Upload a PDF with brand guidelines, connect to your Figma design tokens, or simply describe the vibe you’re going for, and Maia translates it into a complete theme. It intelligently modifies CSS variables for colors, typography, spacing, and border radius, understands the entire Atlas structure to make changes that cascade properly, and includes built-in WCAG contrast checks to ensure accessibility from the start. Upgrading to Atlas 4? Maia can help guide you through migrating from SASS variables to CSS variables.

Design properties made easy

Beyond global theming, Maia can now create and manage design properties: the reusable styling variants that appear in Studio Pro’s properties panel. Want to add a new button style or a “compact” container variant for cards? Just ask. Maia handles the JSON configuration, ensures backward compatibility, and automatically syncs changes so they’re immediately available in your toolbox.

This opens up frontend customization to everyone on your team, eliminating the bottleneck of needing a frontend specialist for every design tweak or brand update.

AI-powered navigation management with Maia

Setting up navigation just got effortless. Maia can now create and manage your app’s navigation profiles and menu, making the journey from generating pages to a fully integrated menu seamless.

Just created a new page with Maia? Ask it to add the page to your menu, and it handles the rest. Need different navigation for mobile users? Maia can create device-specific navigation profiles for phone, tablet, or responsive web and configure properties like Progressive Web App settings. It intelligently handles page parameters by asking how you want to pass values, ensures you don’t accidentally create duplicate profiles, and protects critical configurations from accidental deletion. Navigation setup now flows naturally as part of your development conversation.

Diffing files and long values

Do you remember those times where you wanted to see what changed in a file on disk, or what exactly changed in an XPath constraint, but you didn’t have the third-party tool configured? No more!

From now on, you can directly view textual differences inside Studio Pro, by double-clicking a property or changed file from the Änderungen Feld.

New look and feel for Domain Model editor

Mit Mendix 11.11 you now have the option to use the new refreshed domain model. This not only gives it a fresh new look, but also provides a better way to visualize entities so it’s easier for you to understand and review your domain models. You can enable the new look and feel using the toggle in the toolbar of the domain model document.

Optimistic Locking is now generally available

In multi-user applications, two users editing the same record simultaneously creates a silent but serious problem: the last save wins, and whoever saved first loses their changes without any warning. Until now, developers who wanted to protect against this had to build their own solutions — custom version attributes, manual conflict checks, or complex retry logic.

Mit Mendix 11.11, Optimistisches Sperren is now generally available. First introduced as a public beta in Mendix 11.5, the feature has been hardened through real-world testing and is ready for production. It works by adding a MxObjectVersion system attribute to your entities. At commit time, Mendix compares the in-memory version with the database. If another user has modified the object in between, the commit is blocked and a ConcurrentModificationRuntimeException is raised — giving your app the chance to inform the user and handle the conflict gracefully.

Enabling it is a single toggle in the Registerkarte „Laufzeit“ of your application settings. We strongly encourage teams building collaborative or multi-user apps to turn it on now — starting with Mendix 11.13 it will be the default for new projects. Get ahead of that change and start benefiting from built-in data integrity today. See our Dokumentation for configuration details and conflict handling patterns.

Rspack Client Bundler is now generally available

As Mendix applications grow, build times tend to grow with them. The React Client requires a bundling step that, while essential for runtime performance, can slow down the development feedback loop — especially for large apps.

Rspack is now generally available in Mendix 11.11, after a successful beta in 11.9. The numbers tell the story: in our benchmarks, Rspack completes client bundling up to six-times faster while using up to 70% less memory compared to the previous Rollup-based setup. That directly translates into shorter feedback loops, faster CI/CD pipelines, and a smoother experience for every developer on your team.

If you were already using Rspack in beta — thank you, your feedback helped get it here. If you haven’t yet, you can enable it in the Registerkarte „Laufzeit“ of your application settings today. Rspack will also be backported to Mendix 10.24 LTS, so you won’t have to wait for a major upgrade to benefit. And this is just the beginning — we are actively looking into further build performance improvements in upcoming releases.

Plattform der Enterprise-Klasse

Central Audit Log: one place for auditability and control

Audit data is essential for security, compliance, and operational oversight. Until now, that data was spread across different parts of the Mendix platform. Audit logs existed, but they were distributed and could not be accessed by API—making it harder for administrators, security teams, and auditors to get a complete and timely picture of what was happening.

Mit Central Audit Logs, Mendix brings all audit activity together in Control Center. Enterprises now have a single, authoritative record of user and administrative changes across the platform. Recent activity can be searched directly in the UI, enabling faster reviews and quicker responses to issues. For longer‑term analysis and compliance needs, audit logs can be exported in CSV format or even streamed to enterprise SIEM solutions via the Audit Log API.

By centralizing audit logs, organizations reduce effort, improve traceability, and strengthen governance without adding new tools or processes. Security and compliance teams gain consistent access to the data they need, while platform administrators spend less time collecting information and more time acting on it. The result is better control, clearer accountability, and a Mendix landscape that is easier to manage at enterprise scale.

Centralized Certificates is now generally available

A few months ago, we introduced Centralized Certificates to simplify how you handle SSL certificates across your Mendix Cloud landscape. Now, we’re excited to announce that Central Certificate Management is generally available!

Managing certificates across multiple applications should not slow you down. With Centralized Certificates, you can upload a certificate once and use it across all your custom domains, eliminating repetitive work and reducing the risk of inconsistencies.
Replacing expiring certificates is now effortless. Update a certificate in one place, and all associated custom domains are automatically refreshed. No more manual updates across individual apps. This is especially powerful when working with wildcard certificates or large application landscapes.

You also gain full visibility into your certificates. See where they are used, track expiration dates, and stay ahead of renewals with a clear, landscape-wide overview.

Centralized Certificates reduces operational overhead and gives you control at scale, so you can focus on what matters most: building and running your applications.

This is only the first iteration of Centralized Certificates. We will be adding APIs soon, so that you can automate your certificate management.

POST and GET calls in Mendix Pipelines

Whenever you want to bring a new version of your application live, you want to be sure it’s actually ready. That usually means checking things like quality, tests, or security using tools that sit outside of Mendix. Those checks are often manual, or run in separate systems, which leads to more context switching and less consistency between deployments.

To solve that, we’re thrilled to announce the release of jetzt lesen , STARTE tritt ein Mendix Pipelines. These new pipeline steps let your pipeline securely call external systems as part of the deployment process. A POST call lets your pipeline trigger an action, like starting a scan, running a system, creating a change ticket, or sending a notification. A GET step then uses those variables to poll the external system. You can configure the polling behavior and define success or failure conditions, so the pipeline can determine when to continue or stop the deployment process according to your company standards.

The result is an automated release flow where quality, security, and governance checks are enforced consistently, without manual steps or external orchestration. Want to get started? We recommend following the instructions on the Mendix Docs to get a good grip on this advanced functionality.

Data Transformer beta

We are excited to announce the beta release of Datentransformator: a new capability inside Studio Pro that lets you define and apply data transformations within your integration workflow. Built on the JSLT language, Data Transformer gives you the ability to shape data as it’s consumed in your Mendix app or passed on to other systems without having to write custom Java codes or string manipulation.

With Data Transformer, you can simplify API responses, rename and filter fields, and map complex nested structures into the format that your app or other downstream systems expect. Use Data Transformer to preprocess incoming API responses before mapping them into Mendix Objekte.

You can also use it to do message-to-message transformations without the overhead of creating NPEs. The Test Transformation feature lets you validate at design time that the transformation produces the correct output, saving you time during debugging and development.

Marketplace Content API improvements

Over the past year, we’ve made the Marketplace easier to govern and safer to use: Company-Approved content helps organizations guide developers to the right components, security fix indicators make it clear when a release addresses vulnerabilities, and the deprecation feature helps teams avoid outdated components and move to recommended alternatives.

Now, those same Marketplace signals are also available through the Mendix Inhalts-API. Alongside existing version and component metadata, you can now retrieve company-approved status, detailed vulnerability and security-fix information, and you can download a specific component version directly via the API.

For example, a platform or governance team can build an internal catalog or approval workflow that pulls Marketplace component details, shows whether a component is company-approved, highlights versions marked as vulnerable (including CVE/CWE Identifikatoren when available), points to the security-fix versions that resolve them, and then downloads the chosen version package via the API for controlled distribution.

On the technical side (light details)

• Company approval: Content responses can include isCompanyApproved when your company has enabled Company-Approved functionality.
• Security details: Vulnerable versions can list CVE/CWE identifiers and reference security-fix versions. Security-fix versions indicate what they resolve and which versions are affected. Version types distinguish regular releases vs. vulnerable versions vs. security fixes.
• Direct downloads: The downloadURL attribute provides an endpoint to retrieve a specific component package version programmatically.

Siemens Xcelerator

Siemens UI Module

Der Siemens UI Module for Mendix is now available in the public Marketplace, enabling design and development teams to accelerate the design-to-development journey and deliver consistent, enterprise-grade applications with built-in Siemens design and accessibility patterns.

Sind Sie bereit, Ihre nächste Idee in eine App umzusetzen?

• Starten Sie Ihr Projekt, indem Sie Ihre Vision strukturieren mit Maia Hallenplan.
• Herunterladen Mendix Studio Pro Und verwenden Maia Mach es so, dass du deinen Plan in eine App umwandelst.
• Sehen Sie sich alle Funktionen, Verbesserungen, Fehlerbehebungen und mehr im Mendix 11.11 Versionshinweise.
• Sie möchten zukünftige Updates nicht verpassen? Abonnieren Sie unseren Blog um die neuesten Nachrichten zu erhalten