Studio Pro

History Pane General Availability

The non-blocking history pane, which was introduced as a public beta with Studio Pro 11.4, is now available for general use. This new pane allows you to quickly search your history and maintain context while inspecting historical documents, as the History Pane is no longer a blocking dialog. Additionally, new server-side work now displays as remote revisions, significantly simplifying how you stay updated with developments.

Through the Version Control preferences, you can still opt to use the blocking history dialog. Partial clones are not supported in the new pane and will automatically be redirected to the history dialog instead.

If you have any feedback on the pane, we’re always happy to hear about it. Meanwhile, we’ll continue building “diffing” to show historical changes at a more granular level!

Creating database objects faster

As of 11.6, Mendix OQL also has (beta) support for bulk insert statements via a Java API. This means that you can create multiple objects in your database with one OQL statement. The OQL statement does all the heavy lifting in the database, which will be much faster than moving all the required data through the Mendix runtime.

Here’s an example: Suppose you have a logistics system that registers your stock and customer orders. Every night you determine what stock is low, and what you need to order to restock. This can now be done with a single OQL command that first determines what products are low on stock and then creates new supplier order objects to order new products.

We will be adding Studio Pro support next year to simplify using this functionality, but for now a custom Java activity is the way to use this functionality.

Higher precision decimals

Mendix decimals have a precision of 20,8. This means it can store 20 digits before the decimal separator and 8 after the separator. Some industries like financials have a need for more digits after the decimal separator. As of Mendix 11.6, you can configure per project what decimal precision your project needs. The maximum you can configure is 20 before and 18 after the decimal separator.

Lists of primitives in Consumed OData external actions

We’re adding one more enhancement to the recent series of Consumed OData Service improvements. We’re introducing support for lists of primitives within OData objects for both external action input parameters and return values. The list of primitives will be represented as an associated entity with a single attribute. Now that Studio Pro can directly handle these data structures, you can import and call such external actions from your project. This enhancement increases our coverage of OData contracts and allows you to integrate with a broader range of OData services.

Page parameters: Primitive Types and Optional Types

Pages now support primitive parameters like strings and Booleans, enabling direct transfer of simple values between pages. Instead of creating entities and objects to pass a single value, you can now use expressions to set primitive values as arguments when opening pages with Show Page actions. This allows passing local variables, using functions, or following associations without the overhead of domain model objects.

Parameters can also be marked as optional with default values, eliminating the need to update existing page calls when adding new parameters. This improves page reusability since logic is not tied to specific domain model structures and accelerates modeling by removing unnecessary entity creation for simple data passing.

Workflows Groups: Targeting groups instead of individual users now General Available

After the introduction in the 11.2, the Workflow Groups functionality is now General Available (GA). This addition empowers you to dynamically target user tasks to groups, meaning task assignments automatically adjust as users are added to or removed from a group. Say goodbye to manual reassignments; now, when “John” joins the “Managers” group, he instantly sees all relevant tasks, ensuring your processes remain flexible and always up to date. As always, the optional Workflow Commons module has been extended to accommodate this new functionality as well.

Streamline your workflows: Introducing multiple End activities

Have you ever found yourself trying to funnel several distinct workflow paths into a single, somewhat overloaded End activity?  Crafting elegant workflows for complex business processes can sometimes feel like solving a puzzle – especially when different outcomes need different final steps. That’s why we’ve added support for multiple workflow endpoints, which makes workflow termination more flexible and easier to understand at a glance. By allowing different paths to conclude independently, without requiring an End activity at the end of the main workflow, your workflow models will become significantly clearer.

Imagine a User Task where an approval leads to one final action, but a rejection requires a completely different termination. With multiple end activities, you can now have each outcome directly leading to its own dedicated End activity. This makes your workflow logic immediately apparent and much easier to follow.

Governance

Avoiding double user counts in metering

We’re improving user metering to make it transparent and accurate, ensuring trust and smooth contract renewals. Identifiers stored insystem.user.namemay lead to double counting of internal multiple users or external users. To fix this, we’re introducing a Named User Identifier (typically an email address) so Mendix metering can “de-duplicate” multi-app users. This change is included in the latest version of UserCommons, which is used with SAML, OIDC SSO, and SCIM starting with Mendix 10 LTS.

React and React Native update

This release introduces two major technology upgrades: React 19 and React Native 0.78.
We’ve elevated all applications to React 19, delivering enhanced performance and smarter hooks that give developers greater flexibility when building widgets. By adopting the latest stable version, your applications remain modern and future-ready.

For native mobile apps, we’ve upgraded to React Native 0.78, the first release fully aligned with the new architecture. This shift unlocks superior performance and stability, ensuring a faster, more reliable experience for your users.

Reminder: It’s recommended to update native mobile apps annually. Most native mobile developers have already updated to 10.24 on time. Now, you can choose to move to 11.6 or wait for 11.12, scheduled for release in June 2026. You can read more about our support guidelines for native mobile apps in our documentation.

Smart and agentic apps

Mendix Cloud GenAI: New models, at your preference

Would you like to try out the best coding model in the world? Anthropic Claude Sonnet 4.5 is now available for text generation with Mendix Cloud GenAI. And there’s news for embeddings resources, too: With Cohere Embed 4, Cohere’s most performant embeddings model is now available and offers enhanced retrieval across 100+ languages. To use Cohere Embed 4 in a Mendix project, Mendix Cloud GenAI Connector v5.3.0+ is required.

You can provision new resources with either of these models as a Company Admin in Control Center as a self-service capability. In addition, developers can now also upgrade existing text generation resources or switch their model versions anytime in the Mendix Cloud GenAI portal.

Try out the new models in our GenAI Showcase app or use them for your next project starting from the Blank GenAI App template.

Marketplace

Component Deprecation feature

To keep the Marketplace clean and reliable, a new deprecation feature is being rolled out that allows component suppliers to:

• Mark a component as deprecated.
• Recommend an alternative component (optional, but very helpful!).
• Add a brief explanation for the deprecation.
• Notify subscribers of the change.
• Lower the search ranking of deprecated components.
• Show in Software Composition if a deprecated component is in use.

This feature provides clear guidance: developers will know which components to avoid, what to use instead, and when action is needed in their projects. This saves time, reduces risk, and helps in building more robust applications.

We’ve also rolled out some improvements to the Components page to make managing your owned components even easier! The page now features a datagrid view, replacing the previous card layout, which provides a clearer overview of all your components, including details like the latest version.

Furthermore, for components you own, you can now initiate the edit flow or add a new release directly from that component’s detail page via a context menu.

Siemens Xcelerator

Teamcenter

We are pleased to announce the release of Teamcenter Connector version v2512, featuring several significant enhancements to elevate your user experience. One of the most notable updates is the removal of the OIDC module dependency, allowing you to provision connections to both Teamcenter On-Premise SSO and Teamcenter X with greater ease. There is no longer a need to download OIDC or its associated modules, which translates to considerable time savings.

The SSO setup process has been streamlined with enhanced support for user provisioning and anonymous user authentication directly from the login page. Additionally, we have introduced request handlers that enable authentication through Teamcenter Connector, particularly for widgets related to Active Workspace.
Furthermore, we have proactively updated several Teamcenter SOAs within our Java actions that are scheduled for future deprecation. These updates ensure continued support for functionalities such as “where used” queries, executing workflow actions, and retrieving workflow templates—guaranteeing your integrations remain robust and future-proof.

Finally, we are delighted to share that Teamcenter Connector v2512 is now officially certified for use with Mendix 11.
We’re also introducing Teamcenter Extension Sample App version 5.0. This updated sample app leverages the modern Siemens UX/UI template, offering a sleek and contemporary look. It serves as an excellent showcase for the logic generated by Teamcenter Connector and Extension, fully supporting all out-of-the-box use cases provided in the Extension.

Finally, we’ve made substantial improvements to the Teamcenter Extension documentation. It has been revamped to provide clear, step-by-step guides for each integration journey, making it easier to get started and master the features.
We believe these updates will contribute to a more efficient and enjoyable Teamcenter experience for everyone

Enterprise-ready platform

Hello, Seamless Deployments! Mendix Cloud takes first steps towards zero downtime

We’re thrilled to share some exciting news that marks a significant leap forward for Mendix Cloud users! We’ve officially taken the first steps towards enabling zero downtime deployments for your applications running on Mendix Cloud. This is a moment we’ve been looking forward to, and it’s just the beginning of a more robust and resilient deployment experience.

What does this mean for you?

For applications running on Mendix Cloud, you can make changes to the application configuration, such as changing constant values or scheduled event settings, where your app remains continuously available to your end-users. That’s right – no more brief interruptions during your restarts!
How do we achieve this magic? During a zero-downtime deployment, both your existing application instances and the new instances run concurrently. We then intelligently and gradually shift user traffic from the old instances to the new. Once the new instances are stable and handle all traffic, the old instances are gracefully retired. This ensures a smooth, uninterrupted experience for your users.

When a restart without downtime is possible, you will be prompted whether you want to do this. If you’d rather do a downtime with downtime, that is also possible.

The banner will reflect the type of restart that is chosen.

When a deployment qualifies for zero-downtime, the Deploy Wizard clearly communicates this in the final step via a banner indicating that the environment will be updated with zero downtime, ensuring continuous availability during the update.

The power of Kubernetes: A foundation for the future

This exciting new capability is a direct result of our strategic move to a more modern and scalable infrastructure: Mendix Cloud is now powered by Kubernetes! This fundamental shift provides us with a powerful foundation, unlocking a world of new possibilities for enhancing performance, reliability, and developer experience. Zero downtime deployments are just one of the many innovations that Kubernetes enables.

What’s next on our journey?

We know many of you are eager for zero downtime deployments across all scenarios. While this initial release is focused on restarting applications (redeploying a new version of your application will still result in a short downtime for now), please know that this is just the first step on our journey.

We are actively working on expanding this functionality to support more scenarios and continuously improve the deployment experience. You can look forward to more updates and features that will further enhance the resilience and efficiency of your Mendix applications in the cloud.

Stay tuned for more exciting developments as we continue to evolve Mendix Cloud to bring you the best possible platform for building and running your enterprise applications!

Read more on zero downtime on Mendix Cloud in our documentation.

Are you ready to start your next app?

• Download Mendix Studio Pro.
• Take a closer look at all the features, improvements, fixes, and more in the Mendix 11.6 release notes.
• Don’t want to miss future updates? Subscribe to our blog to catch the latest news