<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Moulidharan on Medium]]></title>
        <description><![CDATA[Stories by Moulidharan on Medium]]></description>
        <link>https://medium.com/@moulidharan07?source=rss-23b3c66129e6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Moulidharan on Medium</title>
            <link>https://medium.com/@moulidharan07?source=rss-23b3c66129e6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 00:16:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@moulidharan07/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Mendix Domain Model Design: 5 Fundamentals Every Developer Should Get Right — Part 1]]></title>
            <link>https://medium.com/@moulidharan07/mendix-domain-model-design-5-fundamentals-every-developer-should-get-right-part-1-2c959c7ab8e3?source=rss-23b3c66129e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c959c7ab8e3</guid>
            <category><![CDATA[domain-model]]></category>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[performance]]></category>
            <category><![CDATA[relationships]]></category>
            <dc:creator><![CDATA[Moulidharan]]></dc:creator>
            <pubDate>Thu, 22 Oct 2026 14:07:16 GMT</pubDate>
            <atom:updated>2026-10-22T14:07:16.933Z</atom:updated>
            <content:encoded><![CDATA[<p>A well-designed domain model is one of the foundations of a maintainable Mendix application. It defines how business information is represented, how entities relate to each other, and how data moves through the application.</p><p>In the early stages of development, it is easy to create entities and associations simply to make a feature work. However, as the application grows, these initial decisions can lead to duplicated data, complicated microflows, unexpected deletion behavior, and expensive refactoring.</p><p>The real challenge is not creating a domain model that works today. It is creating one that continues to work as business requirements evolve.</p><p>In this article, we will explore five fundamental domain model design practices using a simple online café ordering application as an example.</p><h3>1. Design Entities Around Business Concepts</h3><p>One of the most common mistakes in domain modeling is creating entities based only on the screens or forms required by the application.</p><p>A screen represents a user interaction. An entity represents a business concept. These are not necessarily the same thing.</p><p>For example, an online café application may need to manage customers, products, orders, and ordered items. Each represents a distinct concept with its own attributes and responsibilities.</p><p>A basic model might include:</p><ul><li><strong>Customer:</strong> Name, email address, and contact details.</li><li><strong>Product:</strong> Product name, description, and current selling price.</li><li><strong>Order:</strong> Order number, order date, and order status.</li><li><strong>OrderLine:</strong> Quantity ordered and the price applicable to that order.</li></ul><p>An order and its individual lines should not be combined into one entity simply because they appear on the same screen. One order can contain multiple items, and each item has its own quantity and price.</p><h3>A practical example</h3><p>Imagine a customer orders two coffees and one sandwich.</p><p>If the model stores everything directly in the Order entity, you may end up with attributes such as <em>CoffeeQuantity, SandwichQuantity, CoffeePrice,</em> and <em>SandwichPrice</em>.</p><p>This approach becomes difficult to maintain when the café introduces dozens of products.</p><p>A better design separates the order header from its line items:</p><p><em>Customer -&gt; Order -&gt; OrderLine -&gt; Product</em></p><p>The relationships represent the business structure: a customer can place multiple orders, an order can contain multiple order lines, and each order line refers to a product.</p><p><strong>Best practice:</strong> Start by identifying the business concepts and their responsibilities before creating entities in Studio Pro. Avoid creating a separate entity for every screen, and avoid combining unrelated concepts into a single oversized entity.</p><p>Reference: <a href="https://docs.mendix.com/refguide10/configuring-a-domain-model/">Mendix — Configure a Domain Model</a></p><h3>2. Choose Associations Based on Business Requirements</h3><p>Associations define relationships between entities. Choosing the correct multiplicity is important, but developers should also consider whether the relationship itself contains meaningful business information.</p><p>Consider the relationship between Order and Product.</p><p>An order can contain several products, and the same product can appear in many orders. At first glance, a many-to-many association might seem sufficient.</p><p>However, consider what happens when an order contains three coffees at a price of ₹120 each.</p><p>The application needs to know:</p><ul><li>Which product was ordered?</li><li>How many units were ordered?</li><li>What price applied when the order was placed?</li><li>What was the line total?</li></ul><p>These details belong to the individual order line, not to the product or the order as a whole.</p><h3>A better domain model</h3><p>Create an Orderline entity with attributes such as,</p><p><strong><em>Quantity </em></strong><em>-&gt; Number of units ordered</em></p><p><strong><em>UnitPriceAtPurchase </em></strong><em>-&gt; Price per unit when the order was placed</em></p><p><strong><em>LineTotal </em></strong><em>-&gt; Quantity multiplied by the applicable unit price</em></p><p>Then establish these relationships:</p><ul><li>One <strong><em>order </em></strong>can have multiple <strong><em>orderline </em></strong>objects.</li><li>Each <strong><em>orderline </em></strong>belongs to one <strong><em>order</em></strong>.</li><li>One <strong><em>product </em></strong>can be referenced by multiple <strong><em>orderline </em></strong>objects.</li><li>Each <strong><em>orderline </em></strong>refers to one <strong><em>product</em></strong>.</li></ul><p>This design makes the order line an explicit business concept rather than an implicit relationship.</p><h3>Why store the purchase-time price?</h3><p>Suppose a coffee costs ₹120 today. Tomorrow, the café increases its price to ₹140.</p><p>Historical orders should generally continue to show the price that applied when they were placed. If the application relies only on the current Product.Price , historical totals could become inaccurate.</p><p>Storing <strong><em>UnitPriceAtPurchase </em></strong>on <strong><em>orderline </em></strong>preserves the historical transaction value.</p><p>The application should calculate and validate that snapshot when the order is created or confirmed, according to the business rules.</p><p><strong>Best practice:</strong> When a relationship has its own attributes, lifecycle, or business meaning, consider modeling it as a separate entity. A many-to-many association is not inherently wrong; it is simply insufficient when the relationship itself needs to store business data.</p><p>Reference: <a href="https://docs.mendix.com/refguide10/domain-model/">Mendix — Data in the Domain Model</a></p><h3>3. Understand Association Ownership and Delete Behavior</h3><p>Associations are not just lines connecting entities in the domain model. Their configuration affects how relationships are managed and what happens when associated objects are deleted.</p><p>Two concepts deserve particular attention: <strong>association ownership</strong> and <strong>on-delete behavior</strong>.</p><h3>Association ownership</h3><p>In Mendix, association ownership determines which side can edit the relationship. The owner is represented in the domain model, and the association’s configuration affects how its value can be changed.</p><p>For example, if <strong><em>order </em></strong>owns the association to <strong><em>Customer </em></strong>, the relationship can be managed from the <strong><em>order </em></strong>object.</p><p>Ownership does not mean that the other side cannot retrieve or navigate to the associated object. It is about managing the relationship, not simply about which direction data can be read.</p><p>Before changing association ownership or reversing an association, review the existing model and dependent microflows. Reversing an association can remove existing relationship links, even though the associated objects themselves remain.</p><h3>On-delete behavior</h3><p>Mendix supports different behaviors for associated objects when an object is deleted. The available choices include keeping associated objects, deleting associated objects as well, or preventing deletion while associated objects remain linked.</p><p>Consider the café example:</p><ul><li>Deleting a <strong><em>product </em></strong>should not automatically delete historical orders that reference it.</li><li>Deleting an <strong><em>order </em></strong>may require its associated <strong><em>orderline </em></strong>objects to be deleted as well.</li><li>Deleting a <strong><em>Customer </em></strong>may need to be restricted if the business requires customer records to remain available for historical transactions.</li></ul><p>The correct behavior depends on the business lifecycle and the application’s retention requirements.</p><p>For example, if an order is a financial or operational record, deleting it simply because a customer record is being removed could create audit and reporting problems. In many applications, deactivation or anonymization is more appropriate than physical deletion.</p><p><strong>Best practice:</strong> Review ownership, multiplicity, and on-delete behavior together. Do not enable cascading deletion merely because two entities appear to have a parent-child relationship.</p><p>Reference: <a href="https://docs.mendix.com/refguide/associations/">Mendix — Associations</a> <a href="https://docs.mendix.com/refguide/association-properties/">Mendix — Association Properties</a></p><h3>4. Choose Persistability and Generalization Intentionally</h3><p>Two additional design decisions can influence the structure and behavior of a Mendix application: whether an entity is persistable and whether it should use generalization.</p><h3>Persistable versus non-persistable entities</h3><p>A persistable entity is used when application data needs to be stored in the database. A non-persistable entity is intended for temporary data that exists during an interaction or processing flow.</p><p>For example, in the café application:</p><p>Persistable entities</p><ul><li><em>Customer</em></li><li><em>Product</em></li><li><em>Order</em></li><li><em>OrderLine</em></li></ul><p>These contain business information that the application needs to retain.</p><p>Potential non-persistable entities</p><ul><li><em>ProductSearchCriteria</em></li><li><em>TemporaryOrderFilter</em></li><li><em>CheckoutInput</em></li></ul><p>These may hold temporary values used to filter products or collect information before an operation is completed.</p><p>The distinction is not based on the entity’s name or size. It depends on whether the data needs to be persisted and how the application uses it.</p><p>A non-persistable entity does not have its own database table and cannot be used as a substitute for durable business records.</p><h3>Generalization versus association</h3><p>Generalization allows an entity to specialize another entity and inherit its attributes and other relevant properties. It is useful when the specialized entity genuinely represents a more specific type of the general entity.</p><p>For example, car can specialize Vehicle if a car is genuinely a type of vehicle in the business domain.</p><p>However, generalization should not be used automatically whenever two entities share a few attributes.</p><p>Suppose an application has Customer and Employee entities. Whether they should share a generalized entity depends on the actual business model, identity requirements, access rules, and lifecycle.</p><p>In some cases, a common generalization is appropriate. In others, separate entities or a one-to-one association provide a clearer design.</p><p><strong>Best practice:</strong> Choose persistability based on data lifecycle, and choose generalization based on genuine specialization. Avoid using either feature merely to reduce the number of entities or duplicate attributes.</p><p>References: <a href="https://docs.mendix.com/refguide10/persistability/">Mendix — Persistability</a> · <a href="https://docs.mendix.com/refguide/generalization-and-association/">Mendix — Generalization vs One-to-One Associations</a></p><h3>5. Validate the Domain Model Against Real Scenarios</h3><p>A domain model can look clean in Studio Pro and still fail to represent real business requirements.</p><p>The best way to validate a model is to walk through realistic business scenarios before building too many microflows and pages around it.</p><p>For the café ordering application, consider the following scenarios.</p><h3>Scenario 1: One order contains multiple products</h3><p>Can an order contain two coffees, one sandwich, and a dessert without adding product-specific attributes to the Order entity?</p><p>If not, revisit the OrderLine design.</p><h3>Scenario 2: Product prices change</h3><p>If the price of a coffee changes from ₹120 to ₹140, do previously confirmed orders still show the original price?</p><p>If not, review the historical price snapshot and the logic that creates or confirms order lines.</p><h3>Scenario 3: A product is discontinued</h3><p>Can the café stop selling a product without damaging historical order information?</p><p>If not, consider product deactivation, deletion restrictions, and historical reporting requirements.</p><h3>Scenario 4: An order is cancelled</h3><p>What happens to the order lines? Should the order be retained for reporting? Can a cancelled order be deleted, or must its history remain available?</p><p>The answers should determine the entity lifecycle and deletion rules.</p><h3>Scenario 5: A customer places another order</h3><p>Can the application associate multiple orders with the same customer without duplicating customer details on every order?</p><p>If not, revisit the customer-order relationship and the intended data ownership.</p><p>These scenarios expose weaknesses that may not be obvious when looking at the domain model alone.</p><p><strong>Best practice:</strong> Before finalizing a domain model, test the important business operations: creation, updates, deletion, historical reporting, and changes in business rules. A good domain model should represent these scenarios naturally without requiring unnecessary workarounds in microflows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I4qFnPhJDKbZyhN-2r1SWw.png" /></figure><h3>Final Thoughts</h3><p>Domain model design is not simply about creating entities and connecting them with associations. It is about translating business requirements into a structure that remains understandable, consistent, and maintainable over time.</p><p>The five fundamentals covered in this article are:</p><ol><li>Design entities around business concepts.</li><li>Choose associations based on the actual business relationship.</li><li>Understand association ownership and deletion behavior.</li><li>Choose persistability and generalization intentionally.</li><li>Validate the model against realistic business scenarios.</li></ol><p>A few minutes spent evaluating these decisions early can prevent hours of refactoring later.</p><p><strong>My recommendation:</strong> Before implementing a new feature in Mendix, ask yourself three questions:</p><ul><li>Does the domain model accurately represent the business concept?</li><li>Will the model preserve data integrity as the application evolves?</li><li>Can the model support realistic scenarios without unnecessary workarounds?</li></ul><p>If you can answer these questions confidently, you are building on a stronger foundation.</p><h3>References</h3><ol><li><a href="https://docs.mendix.com/refguide10/domain-model/">Data in the Domain Model — Mendix Documentation</a></li><li><a href="https://docs.mendix.com/refguide10/configuring-a-domain-model/">Configuring a Domain Model — Mendix Documentation</a></li><li><a href="https://docs.mendix.com/refguide/associations/">Associations — Mendix Documentation</a></li><li><a href="https://docs.mendix.com/refguide/association-properties/">Association Properties — Mendix Documentation</a></li><li><a href="https://docs.mendix.com/refguide10/persistability/">Persistability — Mendix Documentation</a></li><li><a href="https://docs.mendix.com/refguide/generalization-and-association/">Generalization vs One-to-One Associations — Mendix Documentation</a></li></ol><p><em>This article is Part 1 of a practical series on Mendix domain model design. The examples use an online café ordering application to demonstrate how modeling decisions affect maintainability and data integrity.</em></p><p><em>From the Publisher -</em></p><p><em>Inspired by this article to bring your ideas to life with Mendix? Sign up for a </em><a href="https://signup.mendix.com/?utm_medium=content_syndication&amp;utm_source=medium.com&amp;utm_id=11172331"><em>free account</em></a><em>! You’ll get instant access to the </em><a href="https://academy.mendix.com/link/home"><em>Mendix Academy,</em></a><em> where you can start building your skills.</em></p><p><em>For more articles like this one, visit our </em><a href="https://medium.com/mendix"><em>Medium page</em></a><em>. And you can find a wealth of instructional videos on our </em><a href="https://www.youtube.com/c/MendixCommunity/community"><em>community YouTube page</em></a><em>.</em></p><p><em>Speaking of our community, join us in our </em><a href="https://join.slack.com/t/mendixcommunity/shared_invite/zt-hwhwkcxu-~59ywyjqHlUHXmrw5heqpQ"><em>Slack community channel</em></a><em>. We’d love to hear your ideas and insights!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c959c7ab8e3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Mendix 9 (SVN) to Mendix 10 (Git): Real Upgrade Challenges, Errors, and Lessons Learned]]></title>
            <link>https://medium.com/@moulidharan07/from-mendix-9-svn-to-mendix-10-git-real-upgrade-challenges-errors-and-lessons-learned-499e523bca0b?source=rss-23b3c66129e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/499e523bca0b</guid>
            <category><![CDATA[challenge]]></category>
            <category><![CDATA[migration]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[version-control]]></category>
            <dc:creator><![CDATA[Moulidharan]]></dc:creator>
            <pubDate>Wed, 24 Jun 2026 06:05:35 GMT</pubDate>
            <atom:updated>2026-06-24T06:09:34.914Z</atom:updated>
            <content:encoded><![CDATA[<p>Upgrading a Mendix application is much more than clicking the “Upgrade Project” button. In our recent migration journey, we upgraded a large enterprise application from Mendix 9 LTS (SVN) to Mendix 10.24.15 LTS (Git), and along the way we encountered multiple challenges involving repository migration, deprecated modules, Gradle dependency issues, authentication changes, and marketplace compatibility.</p><p>This article summarizes the practical challenges we faced, how we resolved them, and the lessons learned that can help other Mendix developers plan a smoother upgrade.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LlMBQYbspawNlz6m.png" /></figure><h3>Project Landscape</h3><p>Before starting the upgrade, our application consisted of:</p><ul><li>Mendix 9.24.x LTS</li><li>SVN repository</li><li>Multiple marketplace modules</li><li>SAML authentication</li><li>Email Template module</li><li>Excel Importer</li><li>Custom Java actions</li><li>External integrations (REST APIs, SFTP, Snowflake)</li></ul><p><strong><em>Our target architecture was:</em></strong></p><ul><li>Mendix 10.24.15 LTS</li><li>Git repository</li><li>OIDC authentication</li><li>Email Connector</li><li>Latest marketplace modules</li><li>Gradle-based build process</li></ul><h3>Phase 1: Upgrade to the Latest Mendix 9 LTS</h3><p>One of the biggest mistakes teams make is attempting a direct jump from an older Mendix 9 version to Mendix 10.</p><p>Instead, we first upgraded to the latest Mendix 9 LTS version before starting the major migration.</p><p><strong><em>Benefits:</em></strong></p><ul><li>Reduced breaking changes</li><li>Easier troubleshooting</li><li>Better module compatibility</li><li>Cleaner migration path</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/812/0*s1l0f692TAAWS9ar.png" /></figure><h3>Phase 2: SVN to Git Migration</h3><p>Since Mendix 10 no longer supports SVN repositories, repository migration became a mandatory activity.</p><p><strong><em>Challenges: </em></strong>The technical migration itself was straightforward, but the bigger challenge was adapting development practices,</p><ul><li>Branching strategy changes</li><li>Merge conflict handling</li><li>Pull request workflows</li><li>Team onboarding to Git</li></ul><p><strong>Recommendation:</strong> Complete repository migration before beginning major feature development to avoid parallel migration complexity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/423/0*3jhd9ZwReEgKwgwA" /></figure><h3>Phase 3: Marketplace Module Compatibility</h3><p>After opening the project in Mendix 10, several modules immediately became incompatible.</p><p>Modules requiring attention included:</p><ul><li>Excel Importer</li><li>Community Commons</li><li>Charts</li><li>Authentication modules</li><li>Custom widgets</li></ul><p><strong>Resolution: </strong>upgrade all marketplace modules to Mendix 10 compatible versions before addressing application-specific issues.</p><p>This significantly reduced later troubleshooting effort.</p><h3>Phase 4: Email Template Deprecation</h3><p>One of the first functional issues encountered was email functionality. The existing application relied heavily on the Email Template module. After upgrading, we decided to migrate to Email Connector.</p><p><strong><em>Migration Activities:</em></strong></p><ul><li>Export existing templates</li><li>Reconfigure email logic</li><li>Update microflows</li><li>Retest notification flows</li></ul><p><strong>Outcome: </strong>Email Connector provided better long-term support and compatibility with Mendix 10.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/0*9q_4KpL7ctcQQfxg" /></figure><h3>Phase 5: SAML to OIDC Migration</h3><p>Authentication modernization became another major activity.</p><p>Instead of continuing with our legacy SAML implementation, we migrated to OIDC.</p><p><strong><em>Benefits:</em></strong></p><ul><li>Simpler configuration</li><li>Better cloud compatibility</li><li>Improved user provisioning</li><li>Future-proof authentication architecture</li></ul><p><strong><em>Activities Performed</em></strong></p><ul><li>Identity provider configuration</li><li>Client ID and secret setup</li><li>Redirect URI configuration</li><li>User provisioning setup</li><li>Role mapping</li></ul><p>While DEV and UAT environments worked correctly, we encountered production login issues due to user mapping inconsistencies and token validation configuration differences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*WTrZv4L5TFk4pdrI.png" /></figure><h3>Phase 6: The Gradle Dependency Challenge</h3><p>This was one of the most interesting issues during the migration.</p><p><strong><em>Symptom:</em></strong></p><p>When Gradle was disabled - Application built successfully.</p><p>When Gradle was enabled - Build failed with dependency errors such as com.mendix.replication:1.0.4, not found.</p><p><strong><em>Initial Confusion: </em></strong>At first glance, it appeared that the application itself was healthy because it compiled successfully without Gradle.</p><p>However, enabling Gradle exposed hidden dependency problems.</p><p><strong>Root Cause - </strong>Gradle performs strict dependency validation. It identified an outdated dependency reference related to Replication 1.0.4 from an older module or library.</p><h4>Resolution</h4><ul><li>Upgraded Excel Importer</li><li>Upgraded dependent marketplace modules</li><li>Removed obsolete JAR files</li><li>Cleaned the userlib directory</li><li>Executed Clean Deployment Directory</li><li>Rebuilt the application</li></ul><h4>Key Lesson</h4><p>Disabling Gradle does not fix the problem.It only hides the underlying dependency issue.</p><p>Gradle helped us discover technical debt that would eventually need resolution.</p><h3>Phase 7: Userlib Cleanup</h3><p>Over time, many enterprise applications accumulate outdated JAR files.</p><p>Our userlib contained,</p><ul><li>Legacy dependencies</li><li>Obsolete libraries</li><li>Duplicate versions</li></ul><p>These generated multiple compilation and runtime risks.</p><p><strong><em>Resolution</em></strong></p><p>We conducted a complete review of,</p><ul><li>JAR dependencies</li><li>Module requirements</li><li>Duplicate libraries</li></ul><p>The cleanup process improved build stability and reduced future upgrade risks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IMpRsfODVmwmU-Vl" /></figure><h3>Phase 8: Widget and Front-End Validation</h3><p>Several widgets required validation after migration.</p><p>Areas tested included,</p><ul><li>Data Grid 2</li><li>Charts</li><li>Responsive layouts</li><li>Navigation structures</li><li>Deeplink functionality</li></ul><p>One chart implementation generated JSON parsing issues due to version mismatches between the widget and datasource implementation.</p><p>Upgrading the Charts module and adjusting the datasource logic resolved the issue.</p><h3>Phase 9: Regression Testing</h3><p>After technical upgrades were completed, comprehensive regression testing became critical.</p><p>Testing included,</p><p><strong><em>Functional:</em></strong></p><ul><li>Login</li><li>User management</li><li>Workflows</li><li>Notifications</li><li>File uploads</li></ul><p><strong><em>Integrations:</em></strong></p><ul><li>REST APIs</li><li>SFTP</li><li>External systems</li><li>Scheduled events</li></ul><p><strong><em>Security:</em></strong></p><ul><li>Authentication</li><li>Authorization</li><li>Role-based access</li></ul><p><strong><em>Performance:</em></strong></p><ul><li>Dashboard loading</li><li>Search performance</li><li>Batch processing</li><li>Export operations</li></ul><p><strong><em>Key Lessons Learned</em></strong></p><p><em>What Worked Well</em></p><p>✅ Upgrade to the latest Mendix 9 LTS first</p><p>✅ Upgrade marketplace modules early</p><p>✅ Clean userlib before troubleshooting</p><p>✅ Embrace Gradle validation</p><p>✅ Test authentication thoroughly</p><p>✅ Allocate significant time for regression testing</p><p><em>What We Would Avoid Next Time</em></p><p>❌ Direct version jumps</p><p>❌ Ignoring deprecated modules</p><p>❌ Carrying legacy JAR files forward</p><p>❌ Delaying Git migration</p><p>❌ Assuming authentication will work identically across environments</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U8P-ltlMZP8orJrQk1xa0Q.png" /></figure><h3>Final Thoughts</h3><p>A Mendix 9 to Mendix 10 migration is not simply a platform upgrade. It is an opportunity to modernize authentication, eliminate technical debt, clean dependencies, improve maintainability, and prepare the application for future Mendix releases.</p><p>The most valuable lesson from our migration was that tools such as Gradle do more than compile code — they expose hidden issues that have accumulated over years of development. Addressing those issues during the upgrade resulted in a healthier, more maintainable application.</p><p>If you are planning a Mendix 9 to Mendix 10 migration, invest time in preparation, module upgrades, dependency cleanup, and testing. The effort pays off significantly in long-term stability and supportability.</p><p><em>From the Publisher -</em></p><p><em>Inspired by this article to bring your ideas to life with Mendix? Sign up for a </em><a href="https://signup.mendix.com/?utm_medium=content_syndication&amp;utm_source=medium.com&amp;utm_id=11172331"><em>free account</em></a><em>! You’ll get instant access to the </em><a href="https://academy.mendix.com/link/home"><em>Mendix Academy,</em></a><em> where you can start building your skills.</em></p><p><em>For more articles like this one, visit our </em><a href="https://medium.com/mendix"><em>Medium page</em></a><em>. And you can find a wealth of instructional videos on our </em><a href="https://www.youtube.com/c/MendixCommunity/community"><em>community YouTube page</em></a><em>.</em></p><p><em>Speaking of our community, join us in our </em><a href="https://join.slack.com/t/mendixcommunity/shared_invite/zt-hwhwkcxu-~59ywyjqHlUHXmrw5heqpQ"><em>Slack community channel</em></a><em>. We’d love to hear your ideas and insights!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=499e523bca0b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tracking and Fixing Performance Issues in Mendix Applications]]></title>
            <link>https://medium.com/@moulidharan07/tracking-and-fixing-performance-issues-in-mendix-applications-166c483d47af?source=rss-23b3c66129e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/166c483d47af</guid>
            <category><![CDATA[debugging]]></category>
            <category><![CDATA[performance-optimization]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[css-grid]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <dc:creator><![CDATA[Moulidharan]]></dc:creator>
            <pubDate>Tue, 17 Feb 2026 12:22:07 GMT</pubDate>
            <atom:updated>2026-02-17T12:27:04.426Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Introduction</strong></p><p>Performance issues in Mendix applications are often misunderstood. When users say:</p><ul><li>Grid feels slow</li><li>Scrolling is laggy</li><li>After login it freezes for a few seconds</li></ul><p>Most developers start guessing, but performance optimization is not about guessing , it’s about measuring.</p><p>In this blog, I’ll walk through a complete, real-world approach to tracking, analyzing, and fixing performance issues in Mendix applications from initial suspicion to production validation.</p><h3>Step 1: Understand What Actually Causes Performance Issues</h3><p>Before optimizing, you need to know where problems really come from. Common Performance Bottlenecks in Mendix</p><p><strong>Client-Side Issues</strong></p><ul><li>Loading 1000+ records without pagination</li><li>Heavy Data Grid re-rendering</li><li>Too many nested containers</li><li>Excessive dynamic classes</li><li>Expensive on-change microflows</li><li>Large DOM size</li></ul><p><strong>Server-Side Issues</strong></p><ul><li>Poor XPath queries</li><li>Missing indexes</li><li>Large object retrieval</li><li>Frequent commits</li><li>Complex OQL without optimization</li></ul><p><strong>UX Misinterpretation:</strong></p><p>Sometimes what feels like “slowness” is actually:</p><ul><li>Layout shift</li><li>Blocking UI interaction</li><li>Unoptimized client logic</li></ul><p>That’s why measurement must always come before modification.</p><h3>Step 2: Tools You Must Use (Non-Negotiable)</h3><p><strong>Chrome DevTools —&gt; Performance Tab</strong></p><p>This is your main weapon, Click:</p><pre>F12 → Performance → Record</pre><p>Then:</p><ul><li>Login to your application</li><li>Navigate to page</li><li>Scroll grid (Vertical and horizontal)</li><li>Implement the operations</li><li>Edit rows</li><li>Change dropdowns</li><li>Switch pagination</li></ul><p>Stop recording and analyze.</p><p>This gives you <strong>actual evidence</strong>, not assumptions.</p><h3>Step 3: How to Read the Performance Report</h3><p>When you open the Performance tab, focus on these:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KBWvmQwc8ow-P01T.png" /></figure><p>If these are healthy, your UI foundation is stable.</p><blockquote><strong>Color Indicators</strong></blockquote><ul><li>🟡 Yellow = JavaScript (Scripting)</li><li>🟣 Purple = Rendering</li><li>🟢 Green = Painting</li><li>🔴 Red blocks = Long tasks (danger sign)</li></ul><p>If you see large red blocks dominating the timeline , that’s a real performance issue. If you are not seeing your UI is not blocking.</p><h3>Real Case Study: Data Grid Customization</h3><p>In one of my enterprise Mendix applications:</p><ul><li>More than 25 columns</li><li>100 records per page</li><li>Editable Data Grid 2</li><li>Dropdowns + Date pickers + Toggle Editor</li><li>Horizontal and vertical scroll customization</li><li>Custom alignment CSS</li></ul><blockquote>The concern was, <em>will custom CSS impact performance?</em></blockquote><p>Instead of assuming, I measured.</p><h4>What I Did</h4><ol><li>Recorded login → full interaction session (~97 seconds)</li><li>Analyzed scripting, rendering, painting breakdown</li><li>Checked for layout recalculation spikes</li><li>Looked for red long tasks</li><li>Validated DOM(Document Object Model) size and FPS(Frames Per Second)</li></ol><h4>The Result</h4><ul><li>LCP: Excellent</li><li>CLS: 0 (Perfect stability)</li><li>Rendering time: Healthy</li><li>No long blocking tasks</li><li>No layout thrashing</li></ul><p>Basic CSS properties like,</p><pre>justify-content<br>text-align</pre><p>Have negligible performance impact.</p><h3>Step 4: Identifying Real Bottlenecks</h3><p>Performance problems usually appear as:</p><blockquote><strong>Long Red Tasks, </strong>Main thread blocking.</blockquote><blockquote><strong>Heavy “Recalculate Style”, </strong>Indicates layout thrashing.</blockquote><blockquote><strong>High Scripting Time, </strong>Heavy client-side logic or excessive rerenders.</blockquote><blockquote><strong>Large DOM Size, </strong>Too many nested elements or grid rows.</blockquote><p>If you don’t see these patterns then your UI changes are not the problem.</p><h3>Step 5: Optimization Checklist for Mendix Developers</h3><p>Here’s a practical performance checklist:</p><h4>Data Grid Optimization</h4><ul><li>Always use pagination</li><li>Avoid loading unnecessary associations</li><li>Don’t render 1000+ rows</li><li>Avoid on-change commit loops</li></ul><h4>UI Optimization</h4><ul><li>Reduce nested layout grids</li><li>Avoid excessive dynamic classes</li><li>Remove debug logging in production</li><li>Avoid unnecessary visibility conditions</li></ul><h4>Backend Optimization</h4><ul><li>Use proper indexing</li><li>Optimize XPath queries</li><li>Avoid retrieving full object graphs</li><li>Be careful with OQL joins</li></ul><h3>Why CSS Rarely Causes Real Performance Issues</h3><p>There’s a common misconception that CSS slows down apps.</p><p>In reality, Basic properties like:</p><blockquote>text-align</blockquote><blockquote>justify-content</blockquote><blockquote>color</blockquote><blockquote>padding</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*axu0cSKpNQRIgkil.png" /></figure><p>Do not block the main thread significantly.</p><p>Real performance issues come from,</p><ul><li>Data volume</li><li>Excessive JavaScript execution</li><li>Poor query design</li><li>Repeated re-render cycles</li><li>Heavy client logic</li></ul><p>Performance is rarely about “<strong><em>simple styling</em></strong>”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bEUEoanBxCPoWb0u.gif" /></figure><h3>Step 6: Stress Testing Like a Professional</h3><p>If you want to validate robustness:</p><ol><li>Temporarily increase page size to 200–500 rows</li><li>Scroll aggressively</li><li>Record performance</li><li>Check FPS and red long tasks</li></ol><p>If performance remains smooth, your architecture is strong.</p><h3>Final Thoughts</h3><p>Performance tuning in Mendix is not about randomly removing CSS or rewriting layouts.</p><p>It’s about:</p><p>✔ Measuring<br> ✔ Interpreting correctly<br> ✔ Identifying real bottlenecks<br> ✔ Validating with data</p><p>When you measure properly, you remove fear from development. When you remove fear, you build confidence in production systems.</p><p>That confidence is what separates developers from engineers.</p><p><em>From the Publisher -</em></p><p><em>Inspired by this article to bring your ideas to life with Mendix? Sign up for a </em><a href="https://signup.mendix.com/?utm_medium=content_syndication&amp;utm_source=medium.com&amp;utm_id=11172331"><em>free account</em></a><em>! You’ll get instant access to the </em><a href="https://academy.mendix.com/link/home"><em>Mendix Academy,</em></a><em> where you can start building your skills.</em></p><p><em>For more articles like this one, visit our </em><a href="https://medium.com/mendix"><em>Medium page</em></a><em>. And you can find a wealth of instructional videos on our </em><a href="https://www.youtube.com/c/MendixCommunity/community"><em>community YouTube page</em></a><em>.</em></p><p><em>Speaking of our community, join us in our </em><a href="https://join.slack.com/t/mendixcommunity/shared_invite/zt-hwhwkcxu-~59ywyjqHlUHXmrw5heqpQ"><em>Slack community channel</em></a><em>. We’d love to hear your ideas and insights!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=166c483d47af" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Migrating from Email Template to Email Connector in Mendix]]></title>
            <link>https://medium.com/@moulidharan07/migrating-from-email-template-to-email-connector-in-mendix-45362156a1de?source=rss-23b3c66129e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/45362156a1de</guid>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[email]]></category>
            <category><![CDATA[mendix-developer]]></category>
            <category><![CDATA[migration]]></category>
            <category><![CDATA[mendix-studio-pro]]></category>
            <dc:creator><![CDATA[Moulidharan]]></dc:creator>
            <pubDate>Wed, 21 Jan 2026 09:49:15 GMT</pubDate>
            <atom:updated>2026-01-21T09:49:15.752Z</atom:updated>
            <content:encoded><![CDATA[<p>Email handling is a core part of many Mendix applications for notifications, approvals, reports, alerts, and user communications all depend on it. If you’ve been using the <strong>Email Template module</strong> for years, you may have recently faced this situation.</p><p>This blog explains why the migration is necessary, what changes between <strong>Email Template and Email Connector,</strong> and how to safely migrate during Mendix version upgrades , without breaking production emails or losing historical data.</p><blockquote><strong>Why Migrate from Email Template?</strong></blockquote><p>The <strong>Email Template module</strong> served Mendix developers well for a long time, but with newer Mendix 10 &amp; above versions:</p><ul><li>It is no longer actively maintained.</li><li>Compatibility issues arise during platform upgrades.</li><li>Dependency conflicts (especially <strong>.jar files</strong>) become common.</li><li>Modern features like <strong>secure SMTP, OAuth, and extensibility</strong> are limited.</li></ul><blockquote>The <a href="https://marketplace.mendix.com/link/component/120739"><strong>Email Connector</strong></a> is the officially supported and future-proof solution.</blockquote><h4>Key reasons to migrate:</h4><ul><li>Supported in newer Mendix versions</li><li>Better maintainability and performance</li><li>Clean separation between email logic and templates</li><li>Fewer dependency conflicts during upgrades.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t6vHhNYesuW0TRdHSB4LoA.png" /></figure><h3>1️⃣ Install Email Connector</h3><ul><li>Download the <a href="https://marketplace.mendix.com/link/component/120739"><strong>Email Connector</strong></a> from Marketplace.</li><li>Ensure it matches your <strong>Mendix version.</strong></li><li>Run the application once to validate there are no conflicts.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*c9C43VOC9Cg-erm4.png" /></figure><blockquote>At this stage, <strong>do NOT remove Email Template</strong></blockquote><h3>2️⃣ Review Existing Emails</h3><ul><li>Number of email templates</li><li>Usage type (approval, alerts, reports)</li><li>Dynamic placeholders &amp; logic</li></ul><h3>3️⃣ Migrate Email Logic Incrementally</h3><p><a href="https://marketplace.mendix.com/link/component/205008"><strong>MigrationUtility</strong></a> is helpful for <strong>copying data</strong>, but <strong>it cannot fully migrate Email Template logic to Email Connector</strong>.</p><blockquote>What <a href="https://marketplace.mendix.com/link/component/205008"><strong><em>MigrationUtility</em></strong></a><em> </em>Can Do? You can use it to,</blockquote><ul><li>Copy existing Email Template records</li><li>Migrate subject and HTML body content</li><li>Store templates in a custom entity (for reuse)</li><li>Preserve historical or reusable template data</li></ul><p>This is especially useful when,</p><ul><li>You have <strong>many templates</strong></li><li>Manual copy-paste is risky</li><li>You want to keep legacy templates for reference</li></ul><blockquote>What <a href="https://marketplace.mendix.com/link/component/205008"><strong>MigrationUtility</strong></a> Cannot Do? It <strong>cannot,</strong></blockquote><ul><li>Convert Email Template logic to Email Connector</li><li>Replace tokens automatically</li><li>Migrate send-email microflows</li><li>Handle conditional logic or attachments</li></ul><p>These steps <strong>must be refactored manually</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*RwhhvWtdRBEW0A07" /></figure><h3>4️⃣Migrate Email Logic (One-by-One)</h3><p>For each email,</p><blockquote><strong><em>Old Flow (Email Template)</em></strong></blockquote><ul><li>EmailTemplate entity</li><li>Token replacement</li><li>Send email microflow</li></ul><blockquote><strong><em>New Flow (Email Connector)</em></strong></blockquote><ul><li>Prepare email subject &amp; body manually (String / HTML)</li><li>Set recipients explicitly</li><li>Use Email Connector’s send action</li></ul><p><strong>Tip:</strong> Start with <strong>low-risk emails</strong> (test notifications, internal alerts).</p><h3>5️⃣Preserve Historical Data (Very Important)</h3><p>If your app stores,</p><ul><li>Sent emails</li><li>Audit logs</li><li>Email history</li></ul><blockquote><em>Do not delete </em><strong><em>Email Template entities</em></strong><em> immediately</em></blockquote><h4><strong>Instead:</strong></h4><ul><li>Keep Email Template module <strong>only for historical reference</strong></li><li>Disable new usage</li><li>Gradually archive or migrate old records if required</li></ul><h3>6️⃣Clean Up Dependencies (Userlib Folder)</h3><p>During upgrades, Email Template often leaves behind,</p><ul><li>Duplicate mail JARs</li><li>Conflicting SMTP libraries</li></ul><blockquote><strong>Safe cleanup approach:</strong></blockquote><ol><li>Stop the app</li><li>Remove only <strong>unused / duplicate</strong> JARs</li><li>Restart locally</li><li>Validate email sending</li><li>Commit &amp; deploy application.</li></ol><p><strong><em>Never delete blindly, test every cleanup.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*j5uIiaT3q5obSrw6.png" /></figure><blockquote><strong>Testing Checklist (Must-Do), </strong>Before removing Email Template completely</blockquote><ul><li>All emails delivered successfully</li><li>HTML rendering correct</li><li>Attachments working</li><li>Special characters handled</li><li>Performance verified</li><li>No runtime warnings in logs</li></ul><blockquote><strong>Final Removal (Only When Safe) Once all emails use Email Connector,</strong></blockquote><ul><li>Remove Email Template module</li><li>Clean unused entities</li><li>Re-deploy</li><li>Monitor logs for at least one release cycle</li></ul><blockquote><strong>Common Pitfalls to Avoid,</strong></blockquote><ul><li>Removing Email Template too early</li><li>Migrating everything in one sprint</li><li>Ignoring old email records</li><li>Not testing in upgraded Mendix runtime</li><li>Cleaning userlib without testing</li></ul><h3>Final Thoughts</h3><p>Migrating from <strong>Email Template to Email Connector</strong> is not just a technical task, it’s a stability and future-readiness investment.</p><p>Handled correctly, it gives you,</p><ul><li>Cleaner architecture</li><li>Safer upgrades</li><li>Fewer production issues</li><li>Long-term maintainability</li></ul><p>If you’re planning a <strong>Mendix version upgrade</strong>, make this migration part of your upgrade checklist, not an afterthought.</p><p><em>From the Publisher -</em></p><p><em>Inspired by this article to bring your ideas to life with Mendix? Sign up for a </em><a href="https://signup.mendix.com/?utm_medium=content_syndication&amp;utm_source=medium.com&amp;utm_id=11172331"><em>free account</em></a><em>! You’ll get instant access to the </em><a href="https://academy.mendix.com/link/home"><em>Mendix Academy,</em></a><em> where you can start building your skills.</em></p><p><em>For more articles like this one, visit our </em><a href="https://medium.com/mendix"><em>Medium page</em></a><em>. And you can find a wealth of instructional videos on our </em><a href="https://www.youtube.com/c/MendixCommunity/community"><em>community YouTube page</em></a><em>.</em></p><p><em>Speaking of our community, join us in our </em><a href="https://join.slack.com/t/mendixcommunity/shared_invite/zt-hwhwkcxu-~59ywyjqHlUHXmrw5heqpQ"><em>Slack community channel</em></a><em>. We’d love to hear your ideas and insights!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45362156a1de" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Migrating from SAML to OIDC in Mendix]]></title>
            <link>https://medium.com/@moulidharan07/migrating-from-saml-to-oidc-in-mendix-5111d7f13c5a?source=rss-23b3c66129e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/5111d7f13c5a</guid>
            <category><![CDATA[sso]]></category>
            <category><![CDATA[oidc]]></category>
            <category><![CDATA[oauth]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[autologin]]></category>
            <dc:creator><![CDATA[Moulidharan]]></dc:creator>
            <pubDate>Mon, 08 Sep 2025 08:57:35 GMT</pubDate>
            <atom:updated>2025-09-08T08:57:35.377Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>With the evolution of enterprise authentication, <strong>OIDC (OpenID Connect)</strong> is quickly becoming the preferred standard over <strong>SAML</strong>. While SAML has served as the backbone for Single Sign-On (SSO) for years, OIDC provides a simpler, modern, and API-friendly approach — especially when working with Mendix apps on cloud infrastructures.</p><p>In this post, I’ll walk you through the steps, challenges, and best practices I followed when migrating <strong>Mendix 10.18.9</strong> applications from <strong>SAML SSO to OIDC SSO</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1_EKr_9sbkG5FTKI.png" /></figure><h3>Why Move from SAML to OIDC?</h3><ul><li><strong>Modern Protocol</strong>: OIDC is built on OAuth 2.0, designed for web and mobile apps.</li><li><strong>Easier Integration</strong>: Works seamlessly with Azure AD, Okta, Keycloak, and other identity providers.</li><li><strong>Better Token Support</strong>: JWT-based tokens allow more flexibility in passing claims.</li><li><strong>Future-Proofing</strong>: Many IdPs are deprecating SAML in favor of OIDC.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*WosFR_XGpNOchmBO" /></figure><h3>Step 1: Understanding the Difference</h3><ul><li><strong>SAML</strong> relies on XML-based assertions.</li><li><strong>OIDC</strong> uses lightweight JSON Web Tokens (JWTs).</li><li>Both achieve the same goal (authentication) but in different ways.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*w6OXaRgaPksjoWbX.jpeg" /></figure><h3>Step 2: Install and Configure the OIDC Module</h3><ol><li>Download the <strong>OpenID Connect (OIDC) module</strong> from Mendix Marketplace.</li><li>Configure your <strong>Identity Provider (Azure AD / Okta / etc.)</strong></li></ol><ul><li>Redirect URI → “<a href="https://yourapp/oauth/v2/callback"><em>https://yourapp/oauth/v2/callback</em></a><em>”</em></li><li>Scopes →<em> openid</em></li><li>Claims → <em>email, uat, iat and exp.</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xiyqdW63WLCP5HxnIZ0J-g.png" /></figure><h3>Step 3: Replace SAML Logic with OIDC</h3><ul><li>In SAML, you typically configure the <strong>SAML module + SP metadata</strong>.</li><li>For OIDC:</li><li>Use the microflow<em> “OIDC.DS_StartWebLogin”</em> to trigger the Auto login.</li><li>Configure claims mapping in OIDC module settings.</li><li>Ensure your <strong>Account entity</strong> in Mendix aligns with the OIDC unique identifier.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JgL57bBXmxIt6DiX" /></figure><h3>Step 4: Auto-Redirect with Deeplink (Optional)</h3><p>If you want your users to log in directly without clicking a “Login with SSO” button:</p><ol><li>Use the <strong>Deeplink module</strong>.</li><li>Configure <em>/SSO/</em> as a Deeplink that calls a microflow → “DL<em>_TriggerSSO” </em>.</li><li>Inside the microflow, call “<em>OIDC.DS_StartWebLogin”</em>.</li><li>Now, users can access the app directly at: “<a href="https://yourapp/SSO/"><em>https://yourapp/SSO/</em></a>”</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/771/0*L-bISq-DX-mS3FSE.png" /></figure><h3>Step 5: User Provisioning in OIDC</h3><p>When using <strong>SAML</strong>, user accounts are usually created (provisioned) in Mendix during login using <strong>attribute mapping</strong> (like NameID → Mendix username). With OIDC, you need to do the same but via <strong>claims</strong>.</p><h3>How User Provisioning Works in OIDC</h3><ol><li>A user logs in via OIDC.</li><li>The IdP (Azure AD, Okta, etc.) sends claims such as:</li></ol><ul><li><em>sub </em>(unique identifier for the user, never changes)</li><li><em>email</em></li><li><em>name</em></li><li><em>preferred_username</em></li></ul><ol><li>Mendix looks up the user in the <strong>Account entity</strong> (part of Administration module).</li><li>If found → updates attributes (like display name, email).</li><li>If not found → creates a new account automatically (if provisioning is enabled).</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*py1HEiVj0BCwIna9fs1HWA.png" /></figure><h3>Common Issues During Provisioning</h3><ul><li><strong>Claim mismatch:</strong> If Azure AD sends upn but you mapped email, login may fail.</li><li><strong>Duplicate users:</strong> If you don’t map sub (stable unique ID), the same user may get multiple accounts.</li><li><strong>Missing role mapping:</strong> Users log in successfully but see “No access” because they don’t get the right Mendix role.</li></ul><h3>Challenges I Faced</h3><ul><li><strong>Redirect URI mismatch</strong> → Fixed by updating Azure AD.</li><li><strong>Anonymous access</strong> → Needed to allow OIDC microflows for Anonymous role.</li><li><strong>Data migration</strong> → Ensured existing SAML users were mapped correctly to OIDC identifiers.</li></ul><h3>Key Takeaways</h3><ul><li>Migrating from SAML to OIDC in Mendix is not just a <strong>technical switch</strong>, but also an <strong>identity mapping exercise</strong>.</li><li>OIDC offers <strong>cleaner flows, modern security, and better integration</strong> with today’s cloud IdPs.</li><li>Using Deeplink, you can even create a <strong>seamless login experience</strong> <em>/sso/</em> for end-users.</li></ul><h3>Conclusion</h3><p>If you’re still on SAML, now is the time to plan your migration. OIDC is faster, lighter, and future-proof. For me, the transition in Mendix 10.18.9 was smooth after handling redirect URIs, claims mapping, and Deeplink setup.</p><p>With the right configuration, you can deliver a <strong>zero-click SSO experience</strong> for your end users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/843/0*G-omM6-F_oXwMT6G.png" /></figure><p><em>From the Publisher -</em></p><p><em>Inspired by this article to bring your ideas to life with Mendix? Sign up for a </em><a href="https://signup.mendix.com/?utm_medium=content_syndication&amp;utm_source=medium.com&amp;utm_id=11172331"><em>free account</em></a><em>! You’ll get instant access to the </em><a href="https://academy.mendix.com/link/home"><em>Mendix Academy,</em></a><em> where you can start building your skills.</em></p><p><em>For more articles like this one, visit our </em><a href="https://medium.com/mendix"><em>Medium page</em></a><em>. And you can find a wealth of instructional videos on our </em><a href="https://www.youtube.com/c/MendixCommunity/community"><em>community YouTube page</em></a><em>.</em></p><p><em>Speaking of our community, join us in our </em><a href="https://join.slack.com/t/mendixcommunity/shared_invite/zt-hwhwkcxu-~59ywyjqHlUHXmrw5heqpQ"><em>Slack community channel</em></a><em>. We’d love to hear your ideas and insights!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5111d7f13c5a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Idea to Deployment: Agile the Mendix Way]]></title>
            <link>https://medium.com/@moulidharan07/from-idea-to-deployment-agile-the-mendix-way-e9a2925d9012?source=rss-23b3c66129e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9a2925d9012</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cicd]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Moulidharan]]></dc:creator>
            <pubDate>Mon, 21 Jul 2025 04:01:54 GMT</pubDate>
            <atom:updated>2025-07-21T04:01:54.624Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s fast-paced digital landscape, agility is no longer a luxury, it’s a necessity. Businesses need to deliver applications faster, adapt to change quickly, and continuously improve based on user feedback. <strong>Agile methodologies</strong> are designed for exactly that. But traditional development platforms often struggle to keep up.</p><p>Enter <strong>Mendix</strong>, the leading <strong>low-code platform</strong> that’s purpose-built for agile success.</p><p>In this blog, we’ll explore <strong>how Mendix aligns with agile development practices</strong>, what tools and features it offers for agile teams, and how you can <strong>apply these principles practically</strong> in your development lifecycle.</p><h3>What is Agile Development?</h3><p><strong>Agile development</strong> is an iterative approach to software delivery that builds applications incrementally. Instead of delivering everything at once, agile promotes</p><ul><li>Frequent releases (sprints)</li><li>Continuous user feedback</li><li>Collaboration between cross-functional teams</li><li>Adaptability to change</li></ul><p>While agile is a methodology, Mendix acts as the <strong>engine</strong> that powers it.</p><h3>Collaborative Development Environment</h3><p>Mendix allows <strong>developers, business analysts, and end-users</strong> to collaborate in real-time.</p><ul><li><strong>Web Modeler and Studio Pro</strong> let both citizen and professional developers work together.</li><li><strong>Stories and feedback widgets</strong> allow direct input from stakeholders within the app.</li><li>Version control with <strong>branching and merging</strong> supports parallel development.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/610/0*fbU7nHwuJgSK5HhV.png" /></figure><h3>Agile Project Management with Built-in Scrum Board</h3><p>Every Mendix project includes a built-in <strong>Scrum Board</strong> with:</p><ul><li><strong>Stories</strong>, <strong>Tasks</strong>, and <strong>Sprints</strong></li><li>Drag-and-drop priority sorting</li><li>Progress tracking and team assignment</li></ul><p>Teams can manage their entire <strong>agile backlog</strong> directly within the platform — no third-party tools needed (though integration with Jira and Azure DevOps is also available).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qnV2FwaeCdNc8IJ8.gif" /></figure><h3>Rapid Iterations &amp; Feedback Loop</h3><p>Agile thrives on short feedback cycles, and Mendix delivers with:</p><ul><li><strong>One-click deployment</strong> to the Mendix Cloud or Sandbox</li><li><strong>Live preview</strong> and <strong>test environments</strong> for stakeholders to interact and give feedback</li><li>Built-in <strong>Feedback Capture widget</strong> that logs suggestions to the Stories tab</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Jxws-VeFhZgCjOQA.jpg" /></figure><h3>Modular Architecture for Scalable Change</h3><p>In agile, requirements evolve — and so should your architecture.</p><ul><li>Mendix promotes <strong>modular app design</strong> with <strong>reusable components</strong> and <strong>marketplace modules</strong>.</li><li>Easy to refactor or plug in new features without breaking the entire system.</li><li>Enables microservices and domain-model separation.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*ExzAWCOWtI-UQEAp" /></figure><h3>Built-in CI/CD Pipelines</h3><p>Continuous integration and deployment (CI/CD) is crucial for agile delivery.</p><ul><li>Mendix offers out-of-the-box <strong>CI/CD pipeline templates</strong> (via Mendix Deployment API or GitHub Actions).</li><li>Automate testing, builds, and deployment with zero manual steps.</li><li>Integrates with tools like Jenkins, GitHub, GitLab, and Azure DevOps.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hhnE7eM4kqmKPYtn" /></figure><h3>User-Centric Design with Rapid Prototyping</h3><p>Agile emphasizes <strong>user feedback</strong>, and Mendix makes it easy with:</p><ul><li>Drag-and-drop UI builder to create prototypes in hours, not weeks.</li><li><strong>WYSIWYG (What You See Is What You Get)</strong> design tools to reflect stakeholder input instantly.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*802YKBzVFchRb0th" /></figure><h3>Practical Steps to Agile with Mendix</h3><p>Here’s a <strong>simple agile workflow</strong> using Mendix:</p><ol><li><strong>Create User Stories</strong>: Define business needs in Mendix Stories.</li><li><strong>Sprint Planning</strong>: Assign tasks to sprints and developers.</li><li><strong>Build Collaboratively</strong>: Use Studio/Studio Pro to develop collaboratively.</li><li><strong>Test &amp; Demo</strong>: Deploy to the sandbox and gather real-time feedback.</li><li><strong>Iterate</strong>: Adjust based on feedback and move to production when ready.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rP4R8sll1yTVDrA0.png" /></figure><h3>Bonus: Integrate with Agile Ecosystem</h3><p>If your team uses <strong>Jira, Confluence, Trello, or Azure DevOps</strong>, Mendix allows API-based or native integration to sync stories, tasks, and updates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TYffGFBAj1_gy3Jf" /></figure><h3>Final Thoughts</h3><p>Agile isn’t a buzzword , it’s a mindset. And with Mendix, you’re not just keeping up you’re leading the way.</p><p>Whether you’re a <strong>developer</strong>, a <strong>scrum master</strong>, or a <strong>product owner</strong>, it’s time to harness Mendix for agile success.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9a2925d9012" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Transforming Legacy Applications with Mendix: A Guide to Modernization]]></title>
            <link>https://medium.com/@moulidharan07/transforming-legacy-applications-with-mendix-a-guide-to-modernization-de92d4e3d38b?source=rss-23b3c66129e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/de92d4e3d38b</guid>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[low-code]]></category>
            <category><![CDATA[academy]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[migration]]></category>
            <dc:creator><![CDATA[Moulidharan]]></dc:creator>
            <pubDate>Wed, 16 Jul 2025 05:06:56 GMT</pubDate>
            <atom:updated>2025-07-16T05:06:56.993Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s rapidly evolving digital landscape, outdated legacy systems often stand in the way of business agility and innovation. Many organizations are burdened with rigid monolithic applications that are costly to maintain and slow to adapt to changing business needs.</p><p>This is where <strong>Mendix</strong>, the leading low-code platform, becomes a game-changer. With its robust tools for application modernization, Mendix empowers organizations to transform legacy systems into modern, scalable, and future-proof solutions, faster than ever before.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gRwxdax24thW5FWqluKfag.png" /></figure><h3>Why Modernize Legacy Applications?</h3><p>Legacy systems often:<br> ✅ Are expensive to maintain<br> ✅ Limit integration with modern technologies<br> ✅ Pose security and compliance risks<br> ✅ Create data silos and manual processes<br> ✅ Hinder digital transformation initiatives</p><p>Modernizing these systems enables businesses to:<br> 🚀 Increase operational efficiency<br> 🔗 Improve system integration<br> ⚡ Accelerate time-to-market<br> 💡 Foster innovation and user-centric experiences<br> 🔒 Strengthen security and compliance</p><h3>How Mendix Supports Legacy Transformation</h3><p>Mendix provides a structured, risk-mitigated approach to modernization with tools that enable you to:</p><p>1️⃣ <strong>Assess and Prioritize:</strong><br> Start with a clear understanding of your legacy landscape. Mendix offers tools to analyze technical debt, identify pain points, and prioritize applications for transformation.</p><p>2️⃣ <strong>Extend or Rebuild:</strong><br> Depending on business needs, you can extend your legacy system with new functionality or completely rebuild applications using Mendix’s visual, model-driven development environment.</p><p>3️⃣ <strong>Leverage APIs and Microservices:</strong><br> Mendix helps break down monoliths into modular components with reusable microservices and API integrations. This ensures scalability and easier future updates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/0*8HSCOby_hawvwX-m.jpg" /></figure><p>4️⃣ <strong>Migrate Data Seamlessly:</strong><br> Data migration tools and connectors simplify transferring data from legacy databases to modern cloud environments.</p><p>5️⃣ <strong>Adopt Cloud-Native Architecture:</strong><br> With Mendix, applications can run on any cloud, supporting containerization with Kubernetes and CI/CD pipelines for continuous delivery.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/0*CACiQ6V4Ki81tOIF.jpg" /></figure><h3>Modernization Success Stories</h3><p><strong>Example 1:</strong> A global manufacturer used Mendix to modernize a 20-year-old ERP module. What once took 12 months with traditional coding was rebuilt in 4 months with Mendix integrated seamlessly with SAP.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/635/0*vHiYkgW85h8aHqyt.png" /></figure><p><strong>Example 2:</strong> A financial services provider transformed their legacy loan processing system. Using Mendix, they now deliver new features 5x faster, with a modern user experience for both employees and customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9Eh9t1DZrhhLUbBf.jpg" /></figure><h3>Best Practices for a Successful Modernization</h3><p>✅ <strong>Start Small, Scale Fast:</strong> Begin with a pilot project to demonstrate quick wins.</p><p>✅ <strong>Engage Business &amp; IT:</strong> Bring together domain experts and developers using Mendix’s collaborative tools.</p><p>✅ <strong>Automate Where Possible:</strong> Use Mendix’s AI-powered development assistance and reusable components.</p><p>✅ <strong>Plan for Change Management:</strong> Modernization is not just about technology — align people, processes, and culture.</p><h3>Future-Proof Your Business</h3><p>Legacy applications may have been the backbone of your operations, but they shouldn’t hold you back. Mendix empowers you to reimagine what’s possible, delivering modern digital solutions with the speed and agility today’s market demands.</p><p>Start your modernization journey today unlock innovation, reduce costs, and stay ahead of the competition. Ready to Modernize?</p><p>Visit <a href="https://www.mendix.com/">Mendix.com</a> to learn how leading enterprises are modernizing legacy systems with the #1 low-code platform.</p><p><em>From the Publisher -</em></p><p><em>Inspired by this article to bring your ideas to life with Mendix? Sign up for a </em><a href="https://signup.mendix.com/?utm_medium=content_syndication&amp;utm_source=medium.com&amp;utm_id=11172331"><em>free account</em></a><em>! You’ll get instant access to the </em><a href="https://academy.mendix.com/link/home"><em>Mendix Academy,</em></a><em> where you can start building your skills.</em></p><p><em>For more articles like this one, visit our </em><a href="https://medium.com/mendix"><em>Medium page</em></a><em>. And you can find a wealth of instructional videos on our </em><a href="https://www.youtube.com/c/MendixCommunity/community"><em>community YouTube page</em></a><em>.</em></p><p><em>Speaking of our community, join us in our </em><a href="https://join.slack.com/t/mendixcommunity/shared_invite/zt-hwhwkcxu-~59ywyjqHlUHXmrw5heqpQ"><em>Slack community channel</em></a><em>. We’d love to hear your ideas and insights!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de92d4e3d38b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Optimizing Mendix Applications for Global Deployment: Localization and Internationalization Best…]]></title>
            <link>https://medium.com/@moulidharan07/optimizing-mendix-applications-for-global-deployment-localization-and-internationalization-best-2e7423c6a4f0?source=rss-23b3c66129e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e7423c6a4f0</guid>
            <category><![CDATA[localization]]></category>
            <category><![CDATA[optimization]]></category>
            <category><![CDATA[language]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[conversations]]></category>
            <dc:creator><![CDATA[Moulidharan]]></dc:creator>
            <pubDate>Mon, 14 Jul 2025 06:59:02 GMT</pubDate>
            <atom:updated>2025-07-14T06:59:02.843Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Optimizing Mendix Applications for Global Deployment: Localization and Internationalization Best Practices</strong></h3><p><strong>In today’s connected world, building applications for a global audience is no longer optional, it’s essential.</strong><br>As a Mendix developer, ensuring your applications are ready for multiple languages, cultures, and regions can make or break user adoption across borders.</p><p>In this blog, I’ll share <strong>practical, field-tested best practices</strong> for <strong>localization and internationalization</strong> in Mendix, so you can deliver applications that feel native to every user, no matter where they are.</p><h3>Why Localization and Internationalization Matter in Mendix</h3><p>Imagine you’ve built an amazing app, but your users can’t understand the language, the date formats confuse them, and currencies aren’t familiar. Poor localization leads to poor user experience and lost business opportunities.</p><p>In Mendix, properly setting up I18N and L10N means you can:<br> ✅ Expand to new markets faster<br> ✅ Comply with local regulations<br> ✅ Offer a seamless, culturally relevant user experience<br> ✅ Build trust with diverse users</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/0*pLnycN_jXpMzG1UG.jpg" /></figure><p><strong>Understand the Difference: Internationalization vs Localization</strong></p><ul><li><strong>Internationalization (I18N)</strong> is the process of designing and building your app so it can easily be adapted to different languages and regions, without needing code changes.</li><li><strong>Localization (L10N)</strong> is the actual adaptation: translating text, adjusting formats, currencies, images, and other elements to suit a specific market.</li></ul><p>Mendix provides built-in tools to help you with both, but using them effectively takes planning.</p><h3>Set Up Multiple Languages in Your Mendix App</h3><p><strong>How to do it:</strong></p><ol><li>Go to <strong>Project Settings &gt; Languages</strong></li><li>Add all languages your app will support</li><li>Set a default language</li><li>Translate system texts (e.g., validation messages)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1016/1*utn48tMpVQdEwskpOchc4g.png" /></figure><h3>Use Language Keys and Tokens Effectively</h3><ul><li>Avoid hardcoding text directly into pages or microflows.</li><li>Use text templates with <strong>language tokens</strong> — these automatically display the right translation based on the user’s language preference.</li><li>Keep your <strong>language files</strong> organized and up to date. Consider creating naming conventions for consistency.</li></ul><p><strong><em>Pro Tip:</em></strong> Use the Mendix <strong>Batch Translate</strong> tool or export language files as Excel for easier translation management.</p><h3>Format Dates, Times, and Numbers Properly</h3><p>Formatting must align with local conventions. For example:</p><ul><li>US date: 07/14/2025</li><li>EU date: 14/07/2025</li><li>Japanese date: 2025/07/14</li></ul><p><strong>How to handle this in Mendix:</strong><br> ✅ Use built-in tokens like <strong>DateTimeFormat</strong> with user locale<br> ✅ Always test formatting for all languages you support</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*aNO57Uep6-WoUhME.png" /></figure><h3>Handle Currencies and Units</h3><ul><li>Store monetary values in a base currency, then convert for display.</li><li>Use dynamic currency symbols and decimal separators.</li><li>Consider unit conversions (e.g., miles vs. kilometers, Celsius vs. Fahrenheit) for different regions.</li></ul><p><strong><em>Pro Tip:</em> </strong>Store conversion rates in a configuration entity or retrieve them from a reliable API.</p><h3>Automate and Maintain Your Translations</h3><ul><li>Integrate with translation services via API (e.g., Google Translate for initial drafts, then human review).</li><li>Use version control for your language files.</li><li>Schedule regular translation reviews during your release cycles.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/389/0*OASVOpXsXlNmRXHq" /></figure><h3>Pro Checklist for Global-Ready Mendix Apps</h3><p>✅ Define target languages and locales early<br> ✅ Set up all languages in Project Settings<br> ✅ Never hardcode text — use tokens<br> ✅ Localize images and icons when needed<br> ✅ Format dates, times, and numbers with locale settings<br> ✅ Test with real regional users<br> ✅ Automate translation workflows</p><h3>Final Thoughts: Build Once, Deploy Globally</h3><p>Getting localization and internationalization right in Mendix is an investment that pays off.<br><strong>Build once — and delight users everywhere.</strong></p><p>If you found these tips helpful, share your own best practices in the comments!<br>Let’s make Mendix apps better for everyone, everywhere.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e7423c6a4f0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Future of Mendix: What’s Next for Low-Code Platforms in the Enterprise Space?]]></title>
            <link>https://medium.com/@moulidharan07/future-of-mendix-whats-next-for-low-code-platforms-in-the-enterprise-space-db2e3caee30e?source=rss-23b3c66129e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/db2e3caee30e</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[low-code]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[Moulidharan]]></dc:creator>
            <pubDate>Wed, 09 Jul 2025 16:11:06 GMT</pubDate>
            <atom:updated>2025-07-09T16:11:06.573Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s digital-first economy, speed and adaptability are non-negotiable. Enterprises need to deliver solutions faster, integrate complex systems seamlessly, and meet ever-changing customer expectations, all while managing limited development resources. This is exactly where Mendix, as a leading low-code platform, has made its mark. But what does the future hold? Let’s explore where Mendix and the low-code movement are heading next.</p><h3>Rise of Hyperautomation</h3><p>Low-code is no longer just about faster app delivery, it’s becoming the backbone of <strong>Hyperautomation</strong>. Enterprises increasingly combine Mendix’s visual development with advanced workflows, AI, and robotic process automation (RPA). The future will see Mendix doubling down on out-of-the-box connectors, process mining, and intelligent bots to empower business users to automate repetitive tasks end-to-end, freeing developers for more complex challenges.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gl4QIIfyqtgqgtQKuLB6-A.jpeg" /></figure><h3>Fusion Teams and Citizen Development at Scale</h3><p>The future of enterprise development will be shaped by <strong>fusion teams, </strong>cross-functional teams where IT and business users co-create applications. Mendix’s robust governance, reusable components, and role-based access will continue to evolve, enabling organizations to safely scale citizen development without sacrificing security or quality. Expect more AI-driven suggestions and guardrails that help business users build confidently while IT retains control.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lsm6ezlFqUjxqTepURzqYQ.jpeg" /></figure><h3>Deeper AI and Machine Learning Integration</h3><p>AI is becoming deeply embedded in low-code. Beyond smart app suggestions, Mendix’s future will likely focus on <strong>embedded AI services.</strong> drag-and-drop ML models, no-code predictive analytics, and integrations with major AI/ML platforms. This means enterprises can create intelligent apps like predictive maintenance or customer churn models without heavy data science lift.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*IzDZwyvaKwmwNZ3Q.jpeg" /></figure><h3>Enterprise-Grade Flexibility</h3><p>Today’s large organizations have complex IT landscapes. The next evolution of Mendix will focus on even greater <strong>openness and extensibility</strong> seamless integration with cloud-native services, legacy systems, and emerging tech like IoT and edge computing. Expect expanded support for multi-cloud and hybrid deployments, ensuring applications run securely and efficiently anywhere.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/0*GRmZXFjAcbHNvNvI.jpeg" /></figure><h3>Focus on Composability</h3><p>As Gartner predicts, composable business is the future. Mendix’s commitment to modular development reusable microflows, templates, and pluggable widgets aligns perfectly. Going forward, the marketplace will expand further, empowering teams to compose new apps quickly from pre-built, enterprise-grade building blocks.</p><h3>Strengthening Governance and Security</h3><p>With low-code adoption growing exponentially, robust <strong>governance and compliance</strong> features are critical. Future Mendix releases will likely emphasize advanced monitoring, fine-grained access controls, audit trails, and automated security scans to keep up with global data privacy and cybersecurity standards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-MNSyr_ZdIJxX305X-mPMQ.jpeg" /></figure><h3>Community-Driven Innovation</h3><p>Finally, the Mendix community developers, partners, and ISVs will continue to drive the platform forward. Expect more community contributed modules, industry accelerators, and best practices that help enterprises innovate faster while minimizing reinventing the wheel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*kNQSRZar1wM8qxDE.jpg" /></figure><h3>In Closing</h3><p>The future of Mendix is not just about faster development — it’s about enabling enterprises to adapt, innovate, and stay resilient. As low-code platforms mature, they will increasingly become the strategic backbone of digital transformation, empowering everyone — from seasoned developers to domain experts — to build solutions that matter.</p><p><em>From the Publisher -</em></p><p><em>Inspired by this article to bring your ideas to life with Mendix? Sign up for a </em><a href="https://signup.mendix.com/?utm_medium=content_syndication&amp;utm_source=medium.com&amp;utm_id=11172331"><em>free account</em></a><em>! You’ll get instant access to the </em><a href="https://academy.mendix.com/link/home"><em>Mendix Academy,</em></a><em> where you can start building your skills.</em></p><p><em>For more articles like this one, visit our </em><a href="https://medium.com/mendix"><em>Medium page</em></a><em>. And you can find a wealth of instructional videos on our </em><a href="https://www.youtube.com/c/MendixCommunity/community"><em>community YouTube page</em></a><em>.</em></p><p><em>Speaking of our community, join us in our </em><a href="https://join.slack.com/t/mendixcommunity/shared_invite/zt-hwhwkcxu-~59ywyjqHlUHXmrw5heqpQ"><em>Slack community channel</em></a><em>. We’d love to hear your ideas and insights!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db2e3caee30e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>