As part of the Workflow Commons module we have added a new Conflict Resolution feature. Due to the changes you make over time to your Workflow models, the actual corresponding (running) instances may become incompatible. Instead of resolving instances one by one, administrators can now manage multiple workflow instances directly in one go. This is done using an overview that allows for grouping conflicted instances based on factors such as: conflict reason, the current activities, and/or the execution path. The administrator can then choose a resolution action for the whole group, such as Continue, Jump to Activity, Restart, or Abort.
To improve performance when updating, deleting or inserting large number of objects, OQL is being extended with DELETE, UPDATE and INSERT functionality. This month’s release adds UPDATE support in OQL. Currently it is only available through a Java runtime API (learn more), Studio Pro modeling support will follow in the next months. The Java API enables you to handle bulk update using a custom Java Action as illustrated in the screenshot below. The OQL query finds all WorkOrders with a planned start date in the next week, and sets their status to Delayed.
We’ve added support for STRING_AGG to OQL. This allows you to concatenate multiple strings from multiple objects into one string value. The example below returns one string AssignedEmployees for every work order listing all the employees working on the order.
We’ve added the option to modify SQL queries when running an external database query in a microflow. In the activity you’ll be able to change the SQL query. This can be useful if you need to make changes that cannot be handled by parameters, e.g., change the group by expression.
In the example below, the group by clause in the SQL query is extended by the $RollupBy microflow parameter. This is a common use case for drill down dashboard charts, where you first want to group by year, then by quarter, by month, and finally by week or day.
The Azure Blob Storage Connector can be used to get and store data in the Azure Blob Storage service, which is an object storage service offering industry-leading scalability, data availability, security, and performance. It supports two credential types, the standard Azure Bearer tokens and SAS tokens. The Azure Bearer token can be an application Bearer token as well as a user Bearer token, which is also used for SSO. The SAS tokens are Azure Blob Storage specific.
Two versions have been released:
Since our last blog update, we’ve had two releases of Teamcenter Extension. In version 4.1.x, you can now connect directly to your Teamcenter X instance from within Teamcenter Extension—with Single Sign-On (SSO)!
In version 4.2.x, we’ve added capabilities that allow you to effortlessly generate microflows to retrieve properties of Teamcenter Workspace objects. One example where this could be beneficial is optimizing object searches, allowing you to quickly view essential details and then seamlessly load more comprehensive properties when an object is opened.
We’ve also given the home page a fresh look with updated icons and implemented improved error handling in Java actions for a smoother experience.
Like before, we’ve released two versions, each of 4.1.x and 4.2.x, to support a smooth transition to Mx11 without disrupting existing customer setups. Both versions offer the same feature set—just pick the one that fits your Studio Pro environment.
The Microflow Model is now accessible through an extensibility web API, marking a significant leap forward for Mendix development. This change fundamentally transforms how developers build and interact with the platform by offering programmatic access to Mendix’s visual application logic. To make getting started easier, the API includes helpful defaults, ensuring that new microflows automatically feature essential elements like connected start and end events, just as they would in the editor. This powerful new capability enables the creation of sophisticated tools for automated microflow generation, analysis, refactoring, and integration, which will greatly boost developer productivity and expand the platform’s overall extensibility.
A new option to enable Extension Developer Mode in Studio Pro is now available, making it significantly easier for developers to build extensions. With this update, there’s no need to remember feature flags. Once enabled through the preferences, Extension Development Mode automatically persists regardless of how Studio Pro is started, streamlining the entire extension development workflow.
No more wrestling with invalid Git branch names! We’ll automatically tidy up those tricky characters, so you can create valid branches with smooth, confident clarity.
We understand that navigating a new platform can sometimes feel overwhelming, with choices to make and new terminology to learn. Our goal? To help you quickly discover the platform features you need and ensure you feel right at home from the moment you log in. New users will now be greeted with personalized homepages designed to immediately connect you with the features and information most relevant to your role and needs. This means less searching and more doing!
We’ve redesigned the project homepage to be your ultimate productivity launchpad! Now, from the moment you open a project, you’ll see key insights and development updates tailored to your projects. This means you’ll instantly know what to prioritize, helping you focus on critical tasks and boost your productivity.
We’re introducing a new setting within the Project Settings to give you more control over AI providing help in your projects. You can now opt out of using AI in Epics and App Insights, directly through Maia settings. This update provides greater flexibility, allowing you to customize where and when AI assistance is applied to your work.
With Community Events 2.0, we’ve given organizers the tools to host and scale local and online gatherings directly in our platform. Event creation now comes with integrated RSVP management, notifications, and community features – making it easier for developers to discover, join, and engage. This release lowers barriers for participation and helps connect developers worldwide to the knowledge and peers they seek.
Your agent built with Agent Commons can now be empowered with more tools in a much shorter time – by introducing the option to add tools available via MCP. Agent builders can choose to either add a whole MCP server and thus all tools published by it or select specific tools from it and enable or disable them per version at their preference. Knowledge bases can be enabled and disabled per version, too – rounding up complete control over the information and tools available to an agent.
Last month, we announced that our Mendix Cloud GenAI resource packs are now generally available and can be purchased with cloud tokens – now, the GenAI Resource Portal landing page got a facelift to help you get started with all the right materials from the beginning: find links to supporting blogs, required marketplace content and extensive how-to guides. For example, you can learn how to build your first agent – powered by Mendix Cloud GenAI Resources, of course!
Support for Claude Sonnet 4 is now live in Mendix GenAI Resource Packs, bringing enhanced reasoning, speed, and extended context capabilities directly to your GenAI powered apps! With the addition of Claude Sonnet 4, Mendix developers can leverage one of the most advanced and efficient AI models on the market, offering superior document processing, precise text generation, and dramatically expanded context windows for handling complex business use cases
Some Mendix admins were unaware they could add and remove Mendix admins themselves, because you had to go through Company Settings to find the admin management page. So, we gave it a fresh new home! You’ll now find your company admins right in the Company section of Control Center.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。