<?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 Gurumoorthy J on Medium]]></title>
        <description><![CDATA[Stories by Gurumoorthy J on Medium]]></description>
        <link>https://medium.com/@gurumoorthysutha?source=rss-61211e67918d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Cbdkrjmv6_Jg3Vcv5AtACQ.jpeg</url>
            <title>Stories by Gurumoorthy J on Medium</title>
            <link>https://medium.com/@gurumoorthysutha?source=rss-61211e67918d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 00:02:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gurumoorthysutha/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[Quick Hack Series Part 5: Custom File Dropper — Drag, Drop, Scan, Watermark, Done]]></title>
            <link>https://medium.com/@gurumoorthysutha/quick-hack-series-part-5-custom-file-dropper-drag-drop-scan-watermark-done-b43183366c2e?source=rss-61211e67918d------2</link>
            <guid isPermaLink="false">https://medium.com/p/b43183366c2e</guid>
            <dc:creator><![CDATA[Gurumoorthy J]]></dc:creator>
            <pubDate>Sat, 14 Nov 2026 22:11:04 GMT</pubDate>
            <atom:updated>2026-11-14T22:11:04.851Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XamoSpS3Gx6vagYVDVOO0A.png" /></figure><h3>Introduction</h3><p>Every Mendix app ends up needing file uploads somewhere — a profile picture, a signed contract, an invoice. The default file upload widget works, but it stops at “upload a file.” It doesn’t scan PDFs for hidden scripts, doesn’t watermark documents, doesn’t crop images, and doesn’t give you a clean way to reject a file before or after it lands in the database.</p><p>I built <strong>Custom File Dropper</strong> to cover all of that in one widget. This Quick Hack walks through setting it up on a page, tab by tab, in the order you’d actually configure it.</p><p>The widget covers:</p><ul><li>Drag-and-drop uploads, linked to any entity that inherits System.FileDocument</li><li>Verification hooks both before and after a file is saved</li><li>File size, count, and MIME-type restrictions</li><li>A built-in security scan for malicious PDFs</li><li>Automatic PDF watermarking</li><li>Optional image cropping before upload</li><li>Fully customizable look, feel, and user-facing text</li></ul><p><strong>Step 1: Download the widget from Marketplace</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/934/1*Io73vp5dDXzgQAvxz5Ocjw.png" /></figure><p><strong>Step 2: Drop it on the page</strong></p><p>Drag <strong>Custom File Dropper</strong> from the widget toolbox onto your page, just like any other widget. Double-click it to open its properties you’ll see the tabs : Common, General, Verification before upload, Verification after upload, Restrictions, Security scan, Watermark, Crop, UI, Texts.</p><p>The <strong>Common</strong> tab is the same on every Mendix widget Editable, Name, Tab index, Visible — nothing File-Dropper-specific here. Rename the widget if you’ll have more than one on the page, and move on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/883/1*X3GEfpNOXEB8QfSlf3QeuA.png" /></figure><p><strong>Step 3: Point it at your data the General tab</strong></p><p>This is the one tab you can’t skip. It has three parts:</p><ul><li><strong>Data</strong> — set <strong>File entity</strong> to your entity (e.g. MyModule.FileDocument). Turn on <strong>Auto save</strong> if you want uploads to start the moment a file is dropped, rather than waiting for a per-file upload button.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vKnSoc6agwh-E2C8m2Qv8Q.png" /></figure><ul><li><strong>Context</strong> — if you want uploaded files linked to the object the page is showing, set <strong>File objects</strong> to a data source over your file entity, and <strong>Association to files</strong> to the reference connecting them. Turn on <strong>Show existing files</strong> if files already linked to the object should appear in the list when the page opens. <strong>Delete mode</strong> decides whether the “x” button permanently deletes a file or just unlinks it.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/676/1*svMsEX003X4TBvt0SRbyQQ.png" /></figure><ul><li><strong>Events</strong> — wire up <strong>On file uploaded</strong> and <strong>On file removed</strong> if you want a microflow to run at those moments.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SstEB2QFzkaaPadxN47FWQ.png" /></figure><h4>Step 4: Catch bad files before they’re saved Verification before upload</h4><p>Set <strong>Before commit action</strong> to a microflow, and the widget will run it for every file just before it becomes a Mendix object. Inside that microflow, read <strong>Pending file name / size / type</strong> to inspect the file, and fill <strong>Rejection reason</strong> if you want to reject it — the widget shows that text to the user and drops the file.</p><h4>Step 5: Catch bad files after they’re saved Verification after upload</h4><p>Set <strong>On accept action</strong> to a microflow that receives the actual uploaded file object. If your logic decides the file shouldn’t exist (virus scan integration, content check, whatever your business rule is), delete the file object inside that microflow — the widget notices and shows a rejection message. Fill <strong>Rejection reason (after upload)</strong> for a specific message.</p><h4>Step 6: Set the guardrails Restrictions</h4><p>Three simple settings: <strong>Max. file size</strong> (MB, 0 = unlimited), <strong>Max. files</strong>, and <strong>Mime types</strong> (e.g. image/* or .pdf,.docx) to restrict what’s accepted in the first place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gVyoFj63G9wR6JgjrNYs5Q.png" /></figure><h4>Step 7: Turn on the PDF security scan</h4><p>Flip on <strong>Scan PDF files</strong> under the <strong>Security scan</strong> tab, and the widget checks every PDF for active content — JavaScript, embedded scripts, auto-launch actions, embedded files, XFA forms, rich media before it’s uploaded. A file named .pdf that isn’t actually a valid PDF gets rejected too. Hook <strong>On unsafe file rejected</strong> to a microflow if you want to log the attempt.</p><blockquote><em>This scan runs in the browser. For full protection, also validate files on the server — treat this as your first line of defense, not your only one.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u1dpTyZXxw8jQBv6cZOdBw.png" /></figure><h4>Step 8: Watermark PDFs automatically</h4><p>Turn on <strong>Watermark PDF files</strong> under the <strong>Watermark</strong> tab, set your <strong>Watermark text</strong> (supports placeholders like %%FILENAME%% and %%DATETIME%%), and pick a <strong>Position</strong> — Center, Tiled, or Footer. Adjust font size, color, opacity, and rotation to taste. Password-protected PDFs can’t be watermarked and are rejected automatically while this is on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gDMFe_G364Jkq7tNpHJjZg.png" /></figure><h4>Step 9: Let users crop images before upload</h4><p>If you’re collecting profile pictures or anything similar, turn on <strong>Enable image cropping</strong> under the <strong>Crop</strong> tab, pick an <strong>Aspect ratio</strong> (1:1, 16:9, etc.), and choose <strong>Rectangle</strong> or <strong>Circle</strong> as the crop shape. Non-image files are untouched by this setting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*43npkCbVMmLS6uXrPT1nVQ.png" /></figure><h4>Step 10: Polish the look and the wording</h4><p>The <strong>UI</strong> tab controls appearance — preview panel, type labels, image thumbnails, file size display, toast-style vs. inline alerts, and the progress bar’s four colors. The <strong>Texts</strong> tab lets you override every message the widget shows — the dropzone prompt, the “maximum files reached” message, delete confirmation, and every rejection message — all translatable.</p><h4>Step 11: Try it end to end</h4><ol><li>Drop a normal file — confirm it uploads and shows up in your list.</li><li>Drop a file over your size/type limit — confirm the rejection message appears.</li><li>Drop a PDF with embedded JavaScript (or any PDF, if the scan is just for testing) — confirm it’s caught by the security scan.</li><li>Upload a PDF with watermarking on — open it and confirm the watermark text appears.</li><li>Delete a file — confirm it behaves the way your <strong>Delete mode</strong> setting says it should.</li></ol><h4>Conclusion</h4><p>One widget, ten settings groups, and no custom code — from a plain drag-and-drop uploader to one that validates, scans, watermarks, and crops, with full control over every message the user sees.</p><p>That’s it for this quick hack!</p><p>Drag, drop, scan, watermark — done. A single well-built widget can absorb a surprising amount of complexity so your app doesn’t have to.</p><p>Until the next hack, keep building, keep securing, and keep shipping faster!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b43183366c2e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quick Hack Series Part 4: Stop Session Hijacking in Mendix(Under 10 Minutes)]]></title>
            <link>https://medium.com/mendix/quick-hack-series-part-4-stop-session-hijacking-in-mendix-under-10-minutes-a719cab45f6b?source=rss-61211e67918d------2</link>
            <guid isPermaLink="false">https://medium.com/p/a719cab45f6b</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[Gurumoorthy J]]></dc:creator>
            <pubDate>Sat, 14 Nov 2026 19:22:06 GMT</pubDate>
            <atom:updated>2026-11-14T19:22:06.485Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gE7HEIhh4WbTBEsF8s4d6A.png" /></figure><h3><strong>Introduction</strong></h3><p>Mendix takes care of logging users in and keeping them logged in that’s session management, and the platform handles it reliably out of the box, the same way any serious web framework does. What no platform does automatically, by design, is decide whether a <em>valid</em> session cookie is still being used by the same person it was issued to. That’s not a gap specific to Mendix. it’s true of Java, .NET, Node, everything. It’s extra logic you choose to add on top, based on how sensitive your app is.</p><p>In this Quick Hack, I’ll walk through a small module that adds exactly that layer it notes a “fingerprint” of the device at login, and quietly double-checks it on later requests. If you’re new to Mendix, no prior security background needed.I’ll explain every concept in plain terms and point to where to click in Studio Pro.</p><h4>What this module adds, in one sentence</h4><p>Every time a user logs in, it notes down a fingerprint of their device. Every time they do something afterward, it quietly double-checks that fingerprint and if it suddenly doesn’t match, it logs that session out, on the assumption the cookie ended up somewhere it shouldn’t be.</p><p><strong>Step 1:Download the module from the marketplace</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3RfdycvabDXLxFtYQHLpzw.png" /></figure><p>After importing the module, open <strong>App Explorer</strong> on the left and expand <strong>SessionSecurity</strong>. You’ll see One new data table (called an <strong>entity</strong> in Mendix) named DeviceSessionthis is where the device fingerprint gets stored for each login.</p><p><strong><em>Note: Assign module-level security permissions to the appropriate user roles.</em></strong></p><p><strong>Step 2: Setup the login flow</strong></p><p>On your login page, you should have an NP (non-persistable) object to collect the username and password from the user. From the login page, wire the Login button to call a nanoflow(ACT_SimpleFlow), and map the username and password into it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mAHXC33RUKKOOzCjIVty2A.png" /></figure><p><strong>Step 3: Verify the device after login</strong></p><p>Once login is done, the next part is verification. In Mendix, each role typically has its own home page after login. On that role-based home page’s microflow, call MF_ValidateDeviceFingerprint as a sub-microflow to verify the user against their fingerprint and cookie.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TNqzCDtx74uLSpu60yERSg.png" /></figure><h4>Note: SSO users and continuous verification</h4><p>For SSO users, Step 3 alone is enough there’s no separate login flow to wire up. On top of that, this same sub-microflow can be set up as a microflow timer, running on a set interval, so it keeps checking the session like a heartbeat rather than only once at login.</p><p><strong>Stage 4: Slow down anyone guessing passwords</strong></p><p>Open your login microflow again. Right before the part that actually checks the password, drag in <strong>SUB_RateLimitation_Session</strong> (or SUB_RateLimitation_fingerprint for a stricter version that also tracks IP address).</p><p>Set three simple numbers:</p><ul><li><strong>RateCount</strong> — how many attempts to allow (e.g. 5)</li><li><strong>TimeGap</strong> — within how many seconds (e.g. 60)</li><li><strong>BlockTime</strong> — how long to lock them out after that (e.g. 300 seconds = 5 minutes)</li></ul><p>That’s it no database table to build, no extra logic. Someone trying to guess passwords gets automatically slowed to a crawl.</p><p><strong>Step 5: Confirm it’s working</strong></p><ol><li>Log in normally in one browser.</li><li>Open the same app in a different browser (or change the “User-Agent” in developer tools) and copy over the session cookie.</li><li>Try to click around using that copied session.</li><li>You should get bounced back to the login page — and if you check your app’s logs, you’ll see a line clearly stating the fingerprint didn’t match</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/933/1*6z0Xwg8K7GTwF7_2bY7Okw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/937/1*l2-0ndhnHCDxapBVOIEI9Q.png" /></figure><p><strong>Conclusion</strong></p><p>This is an added layer, not a fix for something broken.Mendix’s session handling works exactly as it should. This just gives you a bit more confidence that a copied cookie doesn’t stay useful forever.</p><p>That’s it for this quick hack!</p><p>Until the next hack, keep building, keep learning, and keep shipping safely!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a719cab45f6b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mendix/quick-hack-series-part-4-stop-session-hijacking-in-mendix-under-10-minutes-a719cab45f6b">Quick Hack Series Part 4: Stop Session Hijacking in Mendix(Under 10 Minutes)</a> was originally published in <a href="https://medium.com/mendix">Mendix Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building the Subscriber Side of Mendix Business Events]]></title>
            <link>https://medium.com/mendix/quick-hack-series-part-7-building-the-subscriber-side-of-mendix-business-events-part-3-cd7159d6a944?source=rss-61211e67918d------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd7159d6a944</guid>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[low-code]]></category>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[apache-kafka]]></category>
            <dc:creator><![CDATA[Gurumoorthy J]]></dc:creator>
            <pubDate>Sat, 22 Aug 2026 07:33:02 GMT</pubDate>
            <atom:updated>2026-10-21T13:26:18.567Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Building the Subscriber Side of Mendix Business Events : Quick Hack Series Part 7 (Banner Image)" src="https://cdn-images-1.medium.com/max/1024/1*gVlf4no6l421hfGUlqj35A.png" /><figcaption>Building the Subscriber Side of Mendix Business Events : Quick Hack Series Part 7</figcaption></figure><h4>Quick Hack Series Part 7</h4><h4><strong>In this part, we take the event we published in </strong><a href="https://medium.com/@gurumoorthysutha/quick-hack-series-part-5-getting-started-with-mendix-business-events-publishing-part-1-cdf1985eafef"><strong>Part 1</strong></a><strong> and actually consume it in a second app. We import the AsyncAPI contract, let Studio Pro auto-generate the consumer entity and </strong><strong>Handle_BE microflow, and wire up real logic that reacts when the event arrives. By the end, you&#39;ll have a full publish-to-consume round trip running locally against the Docker broker from </strong><a href="#"><strong>Part 2</strong></a><strong>.</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cjdUpeswf5FAAdeOwEH5rQ.png" /></figure><h3>Where We Left Off</h3><ul><li><strong>Part 1</strong>: Modeled a Business Event Service, defined the event contract, and published it from a microflow.</li><li><strong>Part 2</strong>: Stood up a local Kafka broker with Docker and pointed Studio Pro at it via ChannelName/ServerUrl constants.</li></ul><p>Now it’s time to close the loop — build an app that actually <em>listens</em> for that event and does something useful with it.</p><h3>Step 1: Get the AsyncAPI Contract from the Publisher</h3><p>Back in your publishing app’s Business Event Service document, click <strong>Export AsyncAPI Document</strong>. This generates a YAML file describing the event’s name, attributes, and channel; this is the contract your subscriber app will import.</p><p>Copy this YAML file somewhere your subscriber app project can access it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xUv8jCqa5yeHfLJDiXWWWw.png" /></figure><h3>Step 2: Import the Event Service in the Subscriber App</h3><ol><li>In the consuming app, right-click the target module → <strong>Add other</strong> → <strong>Business Event Service</strong>.</li><li>Select <strong>Use an existing business event service</strong>.</li><li>Click <strong>Browse</strong>, select the YAML file you exported in Step 1.</li><li>Give the document a name (e.g. BE_LoanApplicationSubmitted_Consumer) → <strong>OK</strong>.</li></ol><p>Studio Pro reads the contract and shows you the event’s structure — same attributes the publisher defined, ready to consume.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/947/1*p-4lQHnZvRtrGYQj_6i4Gg.png" /></figure><h3>Step 3: Subscribe to the Event</h3><p>After importing the AsyncAPI document, Mendix displays a panel where you can configure the subscription implementation. Navigate to the <strong>Subscribe</strong> section, click <strong>Add</strong>, and specify your <strong>Business Entity Name</strong> and <strong>Handler Microflow Name</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1015/1*E02_IidhC6LQkcWxvh05dg.png" /></figure><p>Studio Pro auto-generates two things for you:</p><ul><li>A <strong>persistable consumer entity</strong> in your domain model, mirroring the event’s attributes</li><li>A <strong>Handle_BE microflow</strong>, placed in the same folder as the service document</li></ul><p>This is the key difference from the publisher side: you don’t write the “receive” plumbing yourself. Studio Pro wires the entity and the trigger microflow automatically. Your job is just to fill in what happens <em>after</em> the event lands.</p><h3>Step 4: Build Your Handle_BE Logic</h3><p>Open the generated Handle_BE microflow. It already receives the consumed event object as an input parameter — from here, treat it like any other microflow trigger.</p><p>Typical patterns worth knowing:</p><ul><li><strong>Simple record-and-store</strong>: commit the consumed entity as-is for audit/history purposes.</li><li><strong>Trigger downstream logic</strong>: read the event’s attributes and kick off your own business process — e.g., update a related record, send a notification, or call a REST action.</li><li><strong>Fan-out to multiple actions</strong>: split into decision branches based on event attribute values (e.g. status = “Approved” vs “Rejected”).</li></ul><h3>Step 5: Test the Full Round Trip Locally</h3><p>With both apps configured to point at the same local broker (ChannelName=local, ServerUrl=localhost:9092 from Part 2):</p><ol><li>Run the <strong>publisher app</strong> in Studio Pro, trigger the microflow that commits the published entity.</li><li>Run the <strong>subscriber app</strong> in Studio Pro (or have it already running).</li><li>Watch the subscriber app’s logs — you should see Handle_BE fire automatically once the event lands.</li></ol><p>If you want to verify the message is actually flowing through Kafka before it even reaches your subscriber app, use the same console consumer command from Part 2:</p><pre>docker exec kafka /bin/kafka-console-consumer --topic local --from-beginning --bootstrap-server kafka:19092</pre><p><strong>If you build this out yourself, I’d love to hear where you land; drop a comment with your use case!</strong></p><p><strong>Until next time, keep building and keep hacking!</strong></p><h4>Read more</h4><p><a href="https://docs.mendix.com/appstore/services/event-broker/">Mendix Event Broker</a></p><p><strong><em>From the Publisher -</em></strong></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=cd7159d6a944" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mendix/quick-hack-series-part-7-building-the-subscriber-side-of-mendix-business-events-part-3-cd7159d6a944">Building the Subscriber Side of Mendix Business Events</a> was originally published in <a href="https://medium.com/mendix">Mendix Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setting Up the Event Broker for Mendix Business Events]]></title>
            <link>https://medium.com/mendix/quick-hack-series-part-6-setting-up-the-event-broker-for-mendix-business-events-part-2-6004f5736ca0?source=rss-61211e67918d------2</link>
            <guid isPermaLink="false">https://medium.com/p/6004f5736ca0</guid>
            <category><![CDATA[low-code]]></category>
            <category><![CDATA[tips]]></category>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[event-broker]]></category>
            <dc:creator><![CDATA[Gurumoorthy J]]></dc:creator>
            <pubDate>Fri, 14 Aug 2026 10:35:54 GMT</pubDate>
            <atom:updated>2026-10-08T11:18:58.319Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Setting Up the Event Broker for Mendix Business Events : Quick Hack Series Part 6 (Continued) —( Banner Image)" src="https://cdn-images-1.medium.com/max/1024/1*X3wxfmu7UrCRYkeV-Ru03w.png" /><figcaption>Setting Up the Event Broker for Mendix Business Events : Quick Hack Series Part 6 (Continued)</figcaption></figure><h4>Quick Hack Series Part 6 (Continued)</h4><h4>In my <a href="https://medium.com/@gurumoorthysutha/quick-hack-series-part-5-getting-started-with-mendix-business-events-publishing-part-1-cdf1985eafef">previous post</a> on Business Events, we created a Business Event Service and published our first event from a microflow. But an event with nowhere to go isn’t very useful; that’s where the <strong>Event Broker</strong> comes in.</h4><p>The Event Broker is the piece that actually moves your events between apps. It sits in the middle, receives what gets published, and delivers it to anyone subscribed. In this part, we’ll set up a <strong>local Event Broker using Docker</strong>, so you can model, publish, and test the full round trip entirely on your own workstation before touching Mendix Cloud or a licensed broker.</p><blockquote>Note: you can still get your own Kafka cluster and use it for on-prem also.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v_n8_WuPefp2wDphzqA1ww.png" /></figure><h3>Why You Need This Before You Can Test Anything</h3><p>Studio Pro lets you define publishers and subscribers without a broker running — the modeling works fine. But the moment you actually <strong>run</strong> your app and hit that Publish Event activity, it needs somewhere to send the message. Locally, that “somewhere” is a Kafka broker running in Docker.</p><h4>Prerequisites</h4><ul><li>Docker Desktop installed and running</li><li>Git (to clone the setup repo)</li><li>A Mendix app with at least one Business Event Service already modeled (see Part 1 if you haven’t done this yet)</li></ul><h4>Step 1: Clone the Event Broker Tools Repository</h4><p>Mendix publishes an official helper repo that spins up Kafka and Zookeeper locally with a single command:</p><pre>git clone https://github.com/mendix/event-broker-tools.git</pre><p>This gives you a local-setup folder containing a docker-compose.yml that&#39;s pre-configured for Mendix Business Events modeling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s6x8bF_J2MDAxYFeY1e7mA.png" /></figure><h4>Step 2: Start the Local Broker</h4><p>Navigate into the local-setup folder and run:</p><pre>docker-compose up</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QZZtZioOmF6HXOqM3UP9xQ.png" /></figure><p>Docker will pull the required images (Zookeeper and Kafka) and start both containers. You should see something like this in your terminal once it’s up:</p><pre>[+] Running 2/2<br> ✔ Container zk     Running<br> ✔ Container kafka   Running</pre><p>Leave this terminal open — this is your local broker running in the foreground. You’ll see periodic controller log lines (leader election checks) every few minutes; that’s completely normal steady-state Kafka behavior, not an error.</p><blockquote><strong><em>Tip:</em></strong><em> If you see </em><em>InvalidReceiveException warnings early on referencing a Docker network IP, don&#39;t worry — that&#39;s typically just Kafka rejecting a malformed probe against the port, not something from your Mendix app.</em></blockquote><h4>Step 3: Point Studio Pro at the Local Broker</h4><p>Back in Studio Pro, the Business Events module reads two constants to know where to send and receive events:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/665/1*p-49dFK5KtgB_ew9Qj4OFw.png" /></figure><ol><li>Open the BusinessEvents module and open the UseMe folder -&gt; Local; there you will see a constant called ChannelName. Set it to ‘local’.</li><li>Open the Security module and set the ServerUrl to localhost:9092</li></ol><p>This is the default when Docker Desktop runs natively on Windows or macOS — no VM IP lookup needed for most setups)</p><h4>Step 4: Run and Test</h4><p>Start your Mendix app in Studio Pro using this configuration, then trigger the microflow that publishes your event (from Part 1’s PBE_LDMScript example, or whatever entity you&#39;ve modeled).</p><p>To confirm the event actually landed on the broker, you can watch the topic directly from your terminal:</p><pre>docker exec kafka /bin/kafka-console-consumer --topic local --from-beginning --bootstrap-server kafka:19092</pre><p>Note the port here is different from what you set in Studio Pro — 9092 is the listener exposed to your host machine, while 19092 is Kafka&#39;s internal listener used for container-to-container traffic (in this case, the console consumer running inside the same Docker network).</p><p>If everything’s wired up correctly, you’ll see your event’s JSON payload — including the CloudEvents-standard headers we touched on in Part 1 — show up in this terminal the moment your microflow commits the published entity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/493/1*4wv5KU_q-5C1rB7aMxvFtQ.png" /></figure><h4>What’s Next</h4><p>With the broker running locally, you’re set up to test publishing end-to-end. In <strong>Part 3</strong>, we’ll build the subscriber side — importing the AsyncAPI contract exported from your publishing app, and wiring up the auto-generated Handle_BE microflow to actually react to the event.</p><p><strong>Give this a try, and let me know how it goes — drop a comment if you hit any snags getting your local broker running!</strong></p><p><strong>Until next time, keep building and keep hacking!</strong></p><h4>Read more</h4><ul><li><a href="https://docs.mendix.com/appstore/services/event-broker/">Mendix Event Broker</a></li><li><a href="https://docs.mendix.com/appstore/services/business-events/">Mendix Business Events</a></li></ul><p><strong><em>From the Publisher -</em></strong></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=6004f5736ca0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mendix/quick-hack-series-part-6-setting-up-the-event-broker-for-mendix-business-events-part-2-6004f5736ca0">Setting Up the Event Broker for Mendix Business Events</a> was originally published in <a href="https://medium.com/mendix">Mendix Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting Started with Mendix Business Events Publishing]]></title>
            <link>https://medium.com/mendix/quick-hack-series-part-5-getting-started-with-mendix-business-events-publishing-part-1-cdf1985eafef?source=rss-61211e67918d------2</link>
            <guid isPermaLink="false">https://medium.com/p/cdf1985eafef</guid>
            <category><![CDATA[low-code]]></category>
            <category><![CDATA[tips]]></category>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[Gurumoorthy J]]></dc:creator>
            <pubDate>Fri, 03 Jul 2026 11:45:43 GMT</pubDate>
            <atom:updated>2026-09-22T12:31:18.507Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Getting Started with Mendix Business Events Publishing: Quick Hack Series Part 5 (Banner Image)" src="https://cdn-images-1.medium.com/max/1024/1*OwiTevIuJGgzo0AjnizGIQ.png" /><figcaption>Getting Started with Mendix Business Events Publishing: Quick Hack Series Part 5</figcaption></figure><h4>Quick Hack Series Part 5</h4><h4>If you’ve ever needed two Mendix apps to talk to each other without tightly coupling them together, Business Events might be exactly what you’re looking for.</h4><p>Think of it as a mailing list for your apps: one app publishes an event when something important happens, and any number of other apps can subscribe and react, all without a single direct API call between them.</p><p>In this guide, we’ll walk through what Business Events are, when to use them, and how to implement a publisher and subscriber in Studio Pro from scratch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*23obGmBj987vxPiIuIUX7g.png" /></figure><h3>What Are Business Events?</h3><p>Business events are like a mailing list to share event notifications between apps. The key difference between business events and traditional communication between apps, such as REST or web services, is that there is no direct communication between the apps. An event broker sits in between and handles delivery.</p><p>A classic example: one app uploads a payment receipt while another app processes the outgoing payment in the company’s ledger. Or, a customer places an order, and separately, apps handle shipment scheduling, invoicing, and stock reordering, all triggered off the same event, with zero coupling between those apps.</p><p>Let&#39;s dive into the implementation!</p><h3><strong>Step 1: Install the Mendix Business Events Module</strong></h3><p>To work with business events, import the Mendix Business Events service into your app from the Marketplace.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cWYvwadQDARmJsMBTj4eew.png" /></figure><h3><strong>Step 2: Create a Business Event Service (Publisher Side)</strong></h3><p>In the app that will <strong>publish</strong> the event:</p><ol><li>Right-click a module in your app tree.</li><li>Go to <strong>Add other → Business event service → Create a new business event service</strong>.</li><li>Give your service document a clear name (e.gBE_OrderStatusUpdateService).</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sk8Rc7rOfcG51hK2dPoYZQ.png" /></figure><p>This opens the Business Event Service document, where you’ll define:</p><ol><li><strong>General</strong> — the Service name and Event name prefix.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1021/1*-wGoQYuQuVm437y44JSOAg.png" /></figure><p>2. <strong>In Business Event Definitions</strong> — click <strong>Add</strong> to add a new event where the Event name and Description will be there, so other teams/apps know what this service is about. Then <strong>Attributes-&gt;</strong>click Add to define what data the event carries. Keep in mind: changes here later could lead to breaking changes if the entity is already consumed elsewhere by other apps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/967/1*aVkaJv4FA2EKSYNO0RIRtg.png" /></figure><p>3.<strong> Other apps can</strong> — decide whether other apps can subscribe, publish, or both to this service. Select Publish events and subscribe to events, then click <strong>Done</strong> to create the event.</p><p>Under <strong>This business event service implements</strong>, Studio Pro shows you two panels side by side — <strong>Publish</strong> and <strong>Subscribe</strong>:</p><ul><li>On the <strong>Publish</strong> side, the LDMScript event maps to a published entity, PBE_LDMScript — this is the object your microflow will fill in and hand off to the Publish Event activity.</li><li>On the <strong>Subscribe</strong> side, the same LDMScript event maps to a consumed entity, CBE_LDMScript, with an auto-generated handler microflow, HandleBE_LDMS.Note: when the event is received, this auto-generated microflow will be triggered.</li></ul><p>It’s entirely possible, as in this example, for one service document to define both a publish and a subscribe side for the same event, which is handy when you want to test the full round trip within a single app before splitting publisher and subscriber across separate apps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/961/1*4eZacYq_fIkMXsNe7gpAmw.png" /></figure><p>Under the hood, this service document generates an AsyncAPI 2.2.0 contract. A few things worth noting if you ever inspect or hand off the YAML:</p><ul><li>The channel is identified by a generated GUID (e.g., c11743e61aca4bfda14eb1c4b92549f0), with both a publish and subscribe operation defined against it.</li><li>The message payload schema (LDMScriptPayload) is exactly what you defined in the Attributes tab — in this case, just StatusString: string, maxLength 200.</li><li>Every message carries a set of <strong>CloudEvents-standard headers</strong> (ce_specversion, ce_id, ce_source, ce_type, ce_time, etc.) — this is what lets Business Events interoperate with other CloudEvents-compatible tooling, including the AWS/Azure bridges mentioned later.</li></ul><h3>Step 3: Publish the Event from a Microflow</h3><p>Once your service is defined, drop a <strong>Publish Event</strong> activity into the microflow where the business action happens.</p><p>For our LDMScript example, the flow typically looks like this:</p><ol><li><strong>Create/retrieve</strong> a PBE_LDMScript object (this is the published entity Studio Pro generated for you in Step 2).</li><li><strong>Change Object</strong> — set StatusString to whatever status you want to broadcast (e.g., &quot;Script started&quot;, &quot;Script completed&quot;, &quot;Script failed: timeout&quot;).</li><li>Add the <strong>Publish Event</strong> activity, passing in the PBE_LDMScript object.</li></ol><p>A key benefit here: publishing is part of the same transaction as your other database changes. If your microflow fails and rolls back, the event is not sent — so if your script-handling logic errors out before reaching the Publish Event activity, you don’t end up with a stray “in progress” status floating around with no corresponding real state.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/961/1*0HBDuEebVSXFhq79AzBllg.png" /></figure><p>We have successfully created and published a Business Event. Since this is a broad topic, I’ve split this series into three parts:</p><ul><li><strong>Part 1:</strong> Creating and Publishing a Business Event <em>(this article)</em></li><li><strong>Part 2:</strong> Setting up the Event Broker in both <strong>Mendix Cloud</strong> and <strong>on-premises</strong> environments.</li><li><strong>Part 3:</strong> Creating subscribers to consume the published Business Events.</li></ul><p><strong>I hope this helps. Give this feature a try and let me know what you think! Drop a comment below and share whether you found this feature useful and worth trying.</strong></p><p><strong>Until next time, keep building and keep hacking!</strong></p><h4>Read more</h4><ul><li><a href="http://docs.mendix.com/appstore/services/business-events/">Mendix Business Events</a></li><li><a href="https://docs.mendix.com/refguide/business-event-services/">Business Event Services</a></li></ul><p><strong><em>From the Publisher -</em></strong></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=cdf1985eafef" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mendix/quick-hack-series-part-5-getting-started-with-mendix-business-events-publishing-part-1-cdf1985eafef">Getting Started with Mendix Business Events Publishing</a> was originally published in <a href="https://medium.com/mendix">Mendix Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mendix PWA Wrapper-Native Packaging Without Going Native]]></title>
            <link>https://medium.com/mendix/quick-hack-series-part-5-mendix-pwa-wrapper-native-packaging-without-going-native-e58c9754d201?source=rss-61211e67918d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e58c9754d201</guid>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[low-code]]></category>
            <dc:creator><![CDATA[Gurumoorthy J]]></dc:creator>
            <pubDate>Tue, 30 Jun 2026 10:23:49 GMT</pubDate>
            <atom:updated>2026-09-18T13:38:17.157Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Mendix PWA Wrapper-Native Packaging Without Going Native : Quick Hack Series Part 5 (Banner Image)" src="https://cdn-images-1.medium.com/max/1024/1*s0EPRXY5IFmB7ISdoKjY_g.png" /><figcaption>Mendix PWA Wrapper-Native Packaging Without Going Native : Quick Hack Series Part 5</figcaption></figure><h4>Quick Hack Series Part 5</h4><h4>Mendix just dropped a feature that splits the difference between PWA and full native mobile, and it’s worth a look if you don’t want to commit to React Native for every app.</h4><h4><strong>What does it actually do?</strong></h4><p>PWA Wrapper takes your existing Mendix PWA and wraps it in a native shell for Android/iOS. You get app store distribution, MDM install ability, and a curated set of hardware hooks: barcode/QR scanning, biometric auth, geolocation, local notifications, media upload without rebuilding your UI in React Native.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uu1NB7iDDkbnNJOe72SmCQ.png" /></figure><h4><strong>Where it fits</strong></h4><ul><li>Full native UI + deep device access → stick with Native Mobile</li><li>Web architecture + app-store packaging + light hardware access → PWA Wrapper</li><li>Just a browser URL → plain PWA</li></ul><h3><strong>How to implement it</strong></h3><h4><strong>Step1</strong>— <strong>Check Prerequisites</strong></h4><p>Make sure you’re on Mendix Studio Pro 10.24 or later. You can start this while your app is still in development. You don’t need a finished PWA first.</p><h4><strong>Step 2 — Install PWA Wrapper</strong></h4><ol><li>Open your app in Studio Pro</li><li>Go to the Marketplace</li><li>Search for “PWA Wrapper” and install it</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vgh90rOMzPhIgehsz86_Og.png" /></figure><p>4. When prompted to enable the extension, click Trust module and enable extension.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*pYdEjPUOYKQpev9hxVVigw.png" /></figure><p>5. The installed module gives you two things: App Builder (the build tool) and PWA Wrapper Actions (JS actions for nanoflows)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/467/1*fi6g0n8_n5r3GRg-PxKgmw.png" /></figure><h4><strong>Step 3 — Open the Builder</strong></h4><p>Go to the Extensions menu → Open App Builder</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*COQFCFT45vlyLDy8t2pmEQ.png" /></figure><h4><strong>Step 4 — Choose Your Platform</strong></h4><p>Select Android or iOS depending on what you’re packaging.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/649/1*RtXBcG6g_dyxkOqpOBboVw.png" /></figure><h4><strong>Step 5 — Enter App Metadata</strong></h4><p>Fill in:</p><ul><li>App name</li><li>App version</li><li>Package name/bundle identifier in reverse-domain format (e.g., com.domain.myapp)</li><li>App icon</li><li>Runtime URL of your Mendix app</li><li>Supported devices</li><li>Screen orientation</li><li>(iOS only) Supported device type if asked</li></ul><h4><strong>Step 6 — Configure Permissions</strong></h4><p>Review the permissions list and enable only the ones your app actually uses (e.g., camera for barcode scanning, location for geolocation). Don’t enable everything it slows app store review and adds unnecessary prompts.</p><h4><strong>Step 7 — Set Up Signing</strong></h4><p>For Android:</p><ul><li>Choose an existing signing config, or create a new one if this is your first build</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/596/1*3E-DrShB7qnazHhz_OabNw.png" /></figure><ul><li>Unsigned = OK for internal testing only</li><li>Signed = required for installing on real devices or distribution</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/604/1*m7AQDRryuW3iOLDVHG1fvw.png" /></figure><p>For iOS on macOS:</p><ul><li>You’ll need Xcode (or Xcode Command Line Tools), a .p12 certificate, and a .mobileprovision profile[There is documentation on how to create certs for iOS]</li><li>Create or select your iOS signing configuration</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*tLAUCHC1hZBPIhUH1OcsTw.png" /></figure><h4><strong>Step 8 — Generate the Package</strong></h4><p>Click <strong>Generate Package</strong> and wait for the build to finish.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/618/1*gDVAmjt_nD7xWKWcdHSWAQ.png" /></figure><h4><strong>Step 9 — Retrieve the Output</strong></h4><ul><li>Android: open the output directory and grab the APK</li><li>iOS (macOS): grab the signed .ipa (for physical devices) or .app (for simulator)</li></ul><h4><strong>Step 10 — Install and Test (Optional, via Builder)</strong></h4><p>For Android:</p><ol><li>Connect your Android device (or start an emulator)</li><li>Select the target device in the builder</li><li>Click Install to Device</li><li>Open the app from the device launcher</li></ol><p>For iOS (macOS only):</p><ol><li>Connect your device or start the simulator</li><li>Make sure you have the right artifact (.ipa for device, .app for simulator)</li><li>Select the target device</li><li>Click Install to Device</li><li>Launch from the device/simulator</li></ol><p>If install fails, check the builder’s error message first. Common causes are missing signing, bad provisioning, no device detected, or a conflicting older build already installed.</p><h4><strong>Step 11 — Wire Up the JS Actions</strong></h4><p>In your nanoflows, use the bundled PWA Wrapper actions for biometric auth, barcode/QR scanning, camera/gallery media upload, geolocation, local notifications, sharing, file download, printing, network info, URL opening, and permission requests.</p><h4><strong>Step 12— Distribute</strong></h4><p>Once tested, push the APK/IPA through your normal distribution pipeline (app stores, MDM, internal channels) the same way you’d do for any native build.</p><p><strong>I hope this helps. Give this feature a try and let me know what you think! Drop a comment below and share whether you found this feature useful and worth trying.</strong></p><p><strong>Until next time, keep building and keep hacking!</strong></p><h4>Read more</h4><ul><li><a href="https://docs.mendix.com/refguide/mobile/distributing-mobile-apps/pwa-wrapper/">PWA Wrapper</a></li><li><a href="https://docs.mendix.com/refguide/mobile/distributing-mobile-apps/pwa-wrapper/pwa-wrapper-capabilities/">PWA Wrapper Capabilities</a></li></ul><p><strong><em>From the Publisher -</em></strong></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=e58c9754d201" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mendix/quick-hack-series-part-5-mendix-pwa-wrapper-native-packaging-without-going-native-e58c9754d201">Mendix PWA Wrapper-Native Packaging Without Going Native</a> was originally published in <a href="https://medium.com/mendix">Mendix Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Running Mendix Portable Runtime on Windows]]></title>
            <link>https://medium.com/mendix/running-mendix-portable-app-distribution-pad-on-windows-a-quick-guide-57b5c91cf249?source=rss-61211e67918d------2</link>
            <guid isPermaLink="false">https://medium.com/p/57b5c91cf249</guid>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[jenkins]]></category>
            <category><![CDATA[low-code]]></category>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <category><![CDATA[how-to]]></category>
            <dc:creator><![CDATA[Gurumoorthy J]]></dc:creator>
            <pubDate>Sun, 28 Jun 2026 12:32:02 GMT</pubDate>
            <atom:updated>2026-08-26T12:40:48.275Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Running Mendix Portable Runtime on Windows — A Quick Guide (Banner Image)" src="https://cdn-images-1.medium.com/max/1024/1*_-atyrrpXohHFMNNOe0QqQ.png" /><figcaption>Running Mendix Portable Runtime on Windows — A Quick Guide</figcaption></figure><h4>A Quick Guide</h4><h4>Mendix recently introduced Mendix Portable Runtime<strong> (formerly known as </strong>Portable App Distribution<strong>)</strong> as a deployment method. The idea is simple: bundle your entire Mendix app into a .zip file and run it anywhere without complex installation. No Mendix Cloud, no Kubernetes, just Java and your app.</h4><p>I tried it on Windows and here’s exactly how to get it running.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WyzRKsFAtnypUfOzNOV3Cg.png" /></figure><h3>What is Portable Runtime?</h3><p><strong>Portable Runtime</strong> lets you create a portable .zip file from Studio Pro via <strong>App → Create Deployment Package → Enable Portable</strong>. Extract it anywhere and run bin\start.ps1. It&#39;s a self-contained deployable artifact with all its dependencies bundled in.</p><p><strong>Supported from:</strong> Studio Pro 10.24.19 LTS, 11.6.5 MTS, 11.9+</p><p><strong>Requires:</strong> Java 21</p><p>Let&#39;s cook this up with 3 quick steps.</p><h4><strong>Step 1 — Create the Package in Studio Pro</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fv-KygBjzV7Boj_kuq7OIA.png" /></figure><p>Go to <strong>App → Create Deployment Package</strong>, toggle <strong>Portable package</strong>, and toggle <strong>Export secrets.</strong></p><blockquote><strong>Note: </strong>when this setting is enabled all the constants ,passwords will be written to configuration file so, make sure to keep that file secure</blockquote><p>To finish it off, click <strong>Create</strong>. The .zip lands in your app&#39;s releases folder.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZLRprfikD3PIQXsjAeQV-g.png" /></figure><h4><strong>Step 2 — Extract .zip to a folder</strong></h4><p>Once the portable package has been created, navigate to mendixproject &gt; releases and locate the generated .zip file. Extract the contents of the ZIP file to proceed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SCkyG13PFj-J_cE3ABSIrw.png" /></figure><h4><strong>Step 3 — Run via PowerShell</strong></h4><p>Now open PowerShell from the file’s directory and then set <strong>M2EE_ADMIN_PASS </strong>with the command below:</p><pre>$env:M2EE_ADMIN_PASS = &quot;YourPassword&quot;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2-bUFRFn8DflyA2oSGZH3g.png" /></figure><p>Once done, navigate to the .bin folder and start the process by executing the start.ps1 file.</p><pre>&amp; .\start.ps1</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oc0txgk_VTkqD72VMyjCGg.png" /></figure><p>Your Mendix application is now running locally! To verify that it’s working, open your web browser and navigate to <strong>http://localhost:8080</strong> to access the application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-FW7aCO1tXQTNMibVEiUWg.png" /></figure><h4><strong>Congratulations! Your application is now up and running.</strong></h4><p>One of the best features of Mendix is how quickly you can package and deploy an application with minimal effort.</p><blockquote><strong>Note:</strong> You can take this a step further by automating the deployment process using Jenkins, making your CI/CD pipeline even more efficient.</blockquote><p>Give this feature a try and let me know what you think! Drop a comment below and share whether you found this feature useful and worth trying.</p><p>Until next time, keep building and keep hacking!</p><h4>Read more</h4><p><a href="https://docs.mendix.com/developerportal/deploy/portable-app-distribution-deploy/">Mendix Portable Runtime</a></p><p><strong><em>From the Publisher -</em></strong></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=57b5c91cf249" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mendix/running-mendix-portable-app-distribution-pad-on-windows-a-quick-guide-57b5c91cf249">Running Mendix Portable Runtime on Windows</a> was originally published in <a href="https://medium.com/mendix">Mendix Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Make Any Website Feel Like a Native Mobile App]]></title>
            <link>https://medium.com/mendix/quick-hack-series-part-4-make-any-website-feel-like-a-native-mobile-app-40829bda6e59?source=rss-61211e67918d------2</link>
            <guid isPermaLink="false">https://medium.com/p/40829bda6e59</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[tips]]></category>
            <category><![CDATA[low-code]]></category>
            <category><![CDATA[pwa]]></category>
            <dc:creator><![CDATA[Gurumoorthy J]]></dc:creator>
            <pubDate>Thu, 11 Jun 2026 21:11:33 GMT</pubDate>
            <atom:updated>2026-09-11T11:41:24.376Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Make Any Website Feel Like a Native Mobile App:Quick Hack Series Part 4 (Banner Image)" src="https://cdn-images-1.medium.com/max/1024/1*VbVJ14YNYvgnrMimxMRZgw.png" /><figcaption>Make Any Website Feel Like a Native Mobile App:Quick Hack Series Part 4</figcaption></figure><h4>Quick Hack Series Part 4</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*11r3OX4wYWoiT69vqvSFBA.png" /></figure><h3>Introduction</h3><p>In many projects, the web application and mobile application offer exactly the same functionality. If that’s the case, why maintain two separate teams and two separate development pipelines to build and manage them independently? If you’re planning to build something similar, this blog is for you.</p><p>You might be thinking, <em>“Why not just build a Progressive Web App (PWA)?”</em> And honestly, that’s a valid question. In fact, you’re almost right we absolutely can build a PWA.</p><p>But then another question comes up? how do we distribute it through app stores and make it feel like any other native mobile application? That’s where things start to get a little more interesting, and there are multiple approaches you can take.</p><p>Let’s dive in and explore how we can bridge the gap between web and native experiences while keeping development simple and efficient.</p><h3>Approaches</h3><p>As mentioned earlier, there are multiple ways to convert a website into a mobile application. Let’s take a look at some of the common approaches.</p><h3>Solution 1: Mendix PWA Wrapper</h3><p>If you’re using Mendix, you can leverage the PWA Wrapper to package your Progressive Web App as a mobile application for both iOS and Android. This allows you to reuse your existing web application while making it available through mobile platforms.</p><h3>Solution 2: Third-Party Platforms</h3><p>Another option is to use third-party services such as Median. These platforms simplify the process by generating the mobile application source code for you. They also provide application previews, simulators, and build services, making it easy to test and package your app for distribution.</p><h3>Solution 3: Native App with WebView</h3><p>The third approach is to create a native mobile application and load your website inside a WebView. This is one of the simplest and fastest methods for turning an existing website into a mobile app while still benefiting from native app deployment and distribution.</p><p>In this blog, we’ll focus on <strong>Solution 3</strong> and walk through how to build a native mobile app that loads your website using a WebView.</p><h3>How to Do It</h3><h3>Step 1: Create a Native Navigation Profile</h3><p>Navigate to <strong>App Navigation</strong> and select <strong>Add Navigation Profile</strong>. Create a new <strong>Native Mobile</strong> profile that will be used for your mobile application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bDefsvTdYrvtoRv4G-C5Ng.png" /></figure><h3>Step 2: Configure a Custom Home Page</h3><p>Set the default home page to execute a <strong>Nanoflow</strong> instead of directly opening a page. This Nanoflow will be responsible for preparing and rendering the website inside a WebView.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KEel2H-97OGWl5BDRTojXA.png" /></figure><h3>Step 3: Pass the Website URL</h3><p>Within the Nanoflow, retrieve the remote website URL and pass it as a parameter to the page that contains the WebView widget.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/889/1*t29WgEZrh46OLChy2b4QPQ.png" /></figure><h3>Step 4: Configure the WebView</h3><p>Place a <strong>WebView</strong> widget on the page and bind it to the URL parameter received from the Nanoflow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/1*KfRqkln163DSHuuLMTUttw.png" /></figure><p>For additional security, consider protecting the endpoint through a <strong>Web Application Firewall (WAF)</strong>. If you need to distinguish requests originating from the mobile application, you can also append an encoded token or identifier to the URL and validate it on the server side.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bi9c9qBeWWR1ZKEZxWInKQ.png" /></figure><h3>Step 5: Build and Run the Application</h3><p>Build the native application using the native template and generate the APK (or iOS build). Ensure that the web application is already deployed and accessible before launching the mobile app.</p><p>Once installed, the application will render your website within a native mobile container, giving users an app-like experience while allowing you to maintain a single web codebase.</p><h3>As Usual, Guru’s Hack</h3><h3>UI</h3><p>I recommend using a responsive UI if the page layout and design patterns are exactly the same across web and mobile. In such cases, a responsive design fits perfectly and saves a lot of effort.</p><p>However, if the pages need to be different for web and mobile, there’s a simple hack you can use. Open the page, copy the container, and paste it below the original one. Then modify the duplicated container and apply your mobile-specific design changes. Once you’re done, select the container and navigate to <strong>Properties → Styling</strong>. Under <strong>Design Properties</strong>, you’ll find the <strong>Hide On</strong> option. Simply hide the original container for mobile devices and hide the duplicated container for web and tablet views. This way, Mendix will automatically render the appropriate version based on the screen size, allowing you to maintain different experiences for web and mobile within the same page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nWfF30IjX5sIWhwr1x-0Jw.png" /></figure><h3>Screen Hack</h3><p>Even though we’ve managed to get the application running as a mobile app, there’s still one common issue. When users zoom in, the entire page scales just like it would in a browser. Does that really provide a native app experience? Not quite.</p><p>But don’t worry I have a hack for that too.</p><p>Simply open your index.html file and modify the viewport settings. By adjusting the viewport configuration, you can allow zoom functionality to work normally in the web version while preventing unwanted page zooming in the mobile app. This helps create a more native-like experience and keeps the UI consistent for mobile users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bsCL7FQfWo4WVCVYaSD06w.png" /></figure><pre> &lt;!-- Default viewport --&gt;<br>    &lt;meta name=&quot;viewport&quot; content=&quot;width=device-width, initial-scale=1.0&quot;&gt;<br>    <br>    &lt;!-- Disable zoom on mobile only --&gt;<br>    &lt;script&gt;<br>        (function () {<br>            var viewport = document.querySelector(&#39;meta[name=&quot;viewport&quot;]&#39;);<br>            function setViewport() {<br>                if (window.innerWidth &lt;= 768) {<br>                    viewport.setAttribute(&#39;content&#39;, &#39;width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no&#39;);<br>                } else {<br>                    viewport.setAttribute(&#39;content&#39;, &#39;width=device-width, initial-scale=1.0&#39;);<br>                }<br>            }<br>            setViewport();<br>            window.addEventListener(&#39;resize&#39;, setViewport);<br>        })();<br>    &lt;/script&gt;</pre><p>That’s it for this quick hack!</p><p><strong>Until the next hack, keep building, keep automating, and keep shipping faster!</strong></p><h4>Read more</h4><ul><li><a href="https://docs.mendix.com/refguide/mobile/distributing-mobile-apps/pwa-wrapper/">PWA Wrapper</a></li><li><a href="https://docs.mendix.com/howto/front-end/customize-styling-new/">Customize Styling</a></li></ul><p><strong><em>From the Publisher -</em></strong></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=40829bda6e59" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mendix/quick-hack-series-part-4-make-any-website-feel-like-a-native-mobile-app-40829bda6e59">Make Any Website Feel Like a Native Mobile App</a> was originally published in <a href="https://medium.com/mendix">Mendix Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quick Hack Series Part 3:Native Mobile Build Automated with Jenkins(Under 2 Minutes)]]></title>
            <link>https://medium.com/mendix/quick-hack-series-part-3-native-mobile-build-automated-with-jenkins-under-2-minutes-931f22a36f80?source=rss-61211e67918d------2</link>
            <guid isPermaLink="false">https://medium.com/p/931f22a36f80</guid>
            <category><![CDATA[jenkins]]></category>
            <category><![CDATA[android-studio]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[medium]]></category>
            <dc:creator><![CDATA[Gurumoorthy J]]></dc:creator>
            <pubDate>Tue, 09 Jun 2026 16:33:25 GMT</pubDate>
            <atom:updated>2026-09-03T16:34:37.288Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZOvF0a0eELOb7-2dwwXAYQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gU9JfPo17LxFhEZM32ddww.png" /></figure><h3>Introduction</h3><p>Building native mobile apps manually every time a change is made can be time consuming and repetitive. In this Quick Hack Series, I’ll demonstrate how to automated the complete Mendix Native Mobile build process using Jenkins, reducing the effort to a single button click and generating APKs in under two minutes.</p><p>The automation covers:</p><ul><li>Pulling the latest Mendix project from Git</li><li>Building the Mendix deployment package (.mda)</li><li>Extracting application resources</li><li>Updating the Native Template assets automatically</li><li>Building Android APKs</li><li>Archiving build artifacts in Jenkins</li></ul><p>By the end of this setup, anyone in the team can generate a fresh Native Mobile APK without opening Mendix Studio Pro.</p><h4>Prerequisites</h4><ol><li>Should have a Mendix project</li><li>Java JDK and andriod studio</li><li>Native template</li><li>Jenkins</li></ol><h3><strong>Jenkins environment variables</strong></h3><p>Inside the pipeline, define the required environment paths:</p><pre>environment {<br>    JAVA_HOME = &#39;C:\\Program Files\\Java\\jdk-21&#39;<br>    ANDROID_HOME = &#39;C:\\Users\\username\\AppData\\Local\\Android\\Sdk&#39;<br>    MXBUILD_PATH = &#39;C:\\Program Files\\Mendix\\10.24.14\\modeler\\mxbuild.exe&#39;<br>    NATIVE_TEMPLATE_DIR = &#39;D:\\KMS&#39;<br>}</pre><p>These variables allow Jenkins to locate:</p><ul><li>Java</li><li>Android SDK</li><li>Mendix Build Tool</li><li>Native Template</li></ul><h3>Stage 1: Pull latest code</h3><p>The first stage ensures Jenkins always builds the latest code from Git.</p><pre>stage(&#39;Git Pull&#39;)</pre><p>If the repository does not exist, Jenkins performs a clone.</p><p>Otherwise:</p><ul><li>Reset local changes</li><li>Clean workspace</li><li>Pull latest commits</li></ul><p>Benefits:</p><ul><li>Always builds fresh code</li><li>Prevents workspace corruption</li></ul><h3>Stage 2: Build Mendix deployment package</h3><p>The second stage uses mxbuild to generate an MDA package.</p><pre>stage(&#39;Mendix Build&#39;)</pre><p>Command executed:</p><pre>mxbuild --target=package</pre><p>Output:</p><pre>app.mda</pre><p>This step eliminates the need to open Studio Pro.</p><h3>Stage 3: Extract the MDA</h3><p>A Mendix deployment package is essentially a compressed archive.</p><p>Using PowerShell:</p><pre>Expand-Archive</pre><p>The pipeline extracts:</p><pre>app.mda</pre><p>into:</p><pre>workspace/extracted</pre><p>This exposes:</p><ul><li>Deployment resources</li><li>Application bundles</li><li>Native assets</li></ul><p>Required by the Native Template.</p><h3>Stage 4: Update Native Template assets</h3><p>The extracted content is copied into:</p><pre>android/app/src/main/assets</pre><p>using:</p><pre>xcopy /E /Y</pre><p>This replaces the previous application bundle with the newly built version.</p><p>No manual copy-paste required.</p><h3>Stage 5: Build Android APK</h3><p>Now Jenkins enters the Android project directory and executes:</p><pre>gradlew assembleDebug</pre><p>This generates APKs for configured flavors.</p><p>Example:</p><pre>app-appstore-debug.apk<br>app-dev-debug.apk</pre><h3>Stage 6: Archive APKs</h3><p>Once generated, APKs are copied to a dedicated output folder.</p><pre>archiveArtifacts</pre><p>Benefits:</p><ul><li>APKs stored with build history</li><li>Easy download from Jenkins UI</li><li>Versioned by build number</li></ul><p>Example:</p><pre>KMS_101_appstore.apk<br>KMS_101_dev.apk</pre><h3>Conclusion</h3><p>With a relatively small Jenkins pipeline, we automated the complete Mendix Native Mobile build lifecycle. The process pulls the latest code, builds the Mendix package, updates the Native Template, generates Android APKs, and archives them all in under two minutes.</p><p>Below is the sample pipeline block:</p><pre><br>pipeline {<br>    agent any<br><br>    environment {<br>        JAVA_HOME           = &#39;C:\\Program Files\\Java\\jdk-21&#39;<br>        ANDROID_HOME        = &#39;C:\\Android\\Sdk&#39;<br>        MXBUILD_PATH        = &#39;C:\\Program Files\\Mendix\\&lt;VERSION&gt;\\modeler\\mxbuild.exe&#39;<br>        NATIVE_TEMPLATE_DIR = &#39;D:\\NativeTemplate&#39;<br>    }<br><br>    stages {<br><br>        stage(&#39;Git Pull&#39;) {<br>            steps {<br>                bat &quot;&quot;&quot;<br>                    if not exist &quot;%WORKSPACE%\\ProjectRepo&quot; (<br>                        git clone -b &lt;BRANCH_NAME&gt; https://&lt;TOKEN&gt;@git.api.mendix.com/&lt;REPOSITORY_ID&gt;.git ProjectRepo --depth 1<br>                    ) else (<br>                        cd &quot;%WORKSPACE%\\ProjectRepo&quot; &amp;&amp; git reset --hard HEAD &amp;&amp; git clean -fd &amp;&amp; git pull origin &lt;BRANCH_NAME&gt;<br>                    )<br>                &quot;&quot;&quot;<br>            }<br>        }<br><br>        stage(&#39;Mendix Build&#39;) {<br>            steps {<br>                bat &quot;&quot;&quot;<br>                    if not exist &quot;%WORKSPACE%\\output&quot; mkdir &quot;%WORKSPACE%\\output&quot;<br><br>                    &quot;%MXBUILD_PATH%&quot; ^<br>                      --target=package ^<br>                      --java-home=&quot;%JAVA_HOME%&quot; ^<br>                      --java-exe-path=&quot;%JAVA_HOME%\\bin\\java.exe&quot; ^<br>                      --output=&quot;%WORKSPACE%\\output\\app.mda&quot; ^<br>                      &quot;%WORKSPACE%\\ProjectRepo\\App.mpr&quot;<br>                &quot;&quot;&quot;<br>            }<br>        }<br><br>        stage(&#39;Extract Bundle&#39;) {<br>            steps {<br>                bat &quot;&quot;&quot;<br>                    if exist &quot;%WORKSPACE%\\extracted&quot; rmdir /s /q &quot;%WORKSPACE%\\extracted&quot;<br><br>                    mkdir &quot;%WORKSPACE%\\extracted&quot;<br><br>                    powershell -Command &quot;Expand-Archive -Path &#39;%WORKSPACE%\\output\\app.mda&#39; -DestinationPath &#39;%WORKSPACE%\\extracted&#39; -Force&quot;<br><br>                    echo ===== Extracted Contents =====<br>                    dir &quot;%WORKSPACE%\\extracted&quot;<br>                &quot;&quot;&quot;<br>            }<br>        }<br><br>        stage(&#39;Replace Files&#39;) {<br>            steps {<br>                bat &quot;&quot;&quot;<br>                    if not exist &quot;%NATIVE_TEMPLATE_DIR%\\android\\app\\src\\main\\assets&quot; (<br>                        mkdir &quot;%NATIVE_TEMPLATE_DIR%\\android\\app\\src\\main\\assets&quot;<br>                    )<br><br>                    xcopy /E /Y &quot;%WORKSPACE%\\extracted\\*&quot; &quot;%NATIVE_TEMPLATE_DIR%\\android\\app\\src\\main\\assets\\&quot;<br>                &quot;&quot;&quot;<br>            }<br>        }<br><br>        stage(&#39;Build APK&#39;) {<br>            steps {<br>                dir(&quot;${NATIVE_TEMPLATE_DIR}\\android&quot;) {<br>                    bat &#39;gradlew.bat assembleDebug&#39;<br>                }<br>            }<br>        }<br><br>        stage(&#39;Archive&#39;) {<br>            steps {<br>                bat &quot;&quot;&quot;<br>                    if not exist &quot;%WORKSPACE%\\apk-output&quot; mkdir &quot;%WORKSPACE%\\apk-output&quot;<br><br>                    copy &quot;${NATIVE_TEMPLATE_DIR}\\android\\app\\build\\outputs\\apk\\appstore\\debug\\app-appstore-debug.apk&quot; &quot;%WORKSPACE%\\apk-output\\App_%BUILD_NUMBER%_appstore.apk&quot;<br><br>                    copy &quot;${NATIVE_TEMPLATE_DIR}\\android\\app\\build\\outputs\\apk\\dev\\debug\\app-dev-debug.apk&quot; &quot;%WORKSPACE%\\apk-output\\App_%BUILD_NUMBER%_dev.apk&quot;<br>                &quot;&quot;&quot;<br><br>                archiveArtifacts artifacts: &#39;apk-output/*.apk&#39;, fingerprint: true<br>            }<br>        }<br>    }<br><br>    post {<br>        success {<br>            echo &#39;APK build succeeded! Check archived artifacts.&#39;<br>        }<br><br>        failure {<br>            echo &#39;Build failed — check logs above.&#39;<br>        }<br>    }<br>}<br></pre><p>That’s it for this quick hack!</p><p>With just a few Jenkins stages, we’ve transformed a manual build process into a one-click automated pipeline. Small automations like these can make a huge difference in day-to-day development.</p><p><strong>Until the next hack, keep building, keep automating, and keep shipping faster!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=931f22a36f80" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mendix/quick-hack-series-part-3-native-mobile-build-automated-with-jenkins-under-2-minutes-931f22a36f80">Quick Hack Series Part 3:Native Mobile Build Automated with Jenkins(Under 2 Minutes)</a> was originally published in <a href="https://medium.com/mendix">Mendix Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quick Hack Series Part 2:Google Analytics 4 in Mendix]]></title>
            <link>https://medium.com/mendix/quick-hack-series-part-2-google-analytics-4-in-mendix-94ec16b050fa?source=rss-61211e67918d------2</link>
            <guid isPermaLink="false">https://medium.com/p/94ec16b050fa</guid>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[tips]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[low-code]]></category>
            <dc:creator><![CDATA[Gurumoorthy J]]></dc:creator>
            <pubDate>Sun, 19 Apr 2026 14:31:25 GMT</pubDate>
            <atom:updated>2026-08-19T10:34:31.141Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Google Analytics 4 in Mendix (Under 2 Minutes) : Quick Hack Series Part 2 (Banner Image)" src="https://cdn-images-1.medium.com/max/1024/1*pyar6HUW4WEnAAMZfmdW6A.png" /><figcaption>Google Analytics 4 in Mendix (Under 2 Minutes) : Quick Hack Series Part 2</figcaption></figure><h3>Google Analytics 4 in Mendix (Under 2 Minutes)</h3><h4>Quick Hack Series Part 2</h4><h4>Track your users. Understand behavior. Improve your app.</h4><p>What if you could see <strong>what users are doing inside your Mendix app</strong> in just a few minutes?</p><p>In this quick guide, I’ll show you the <strong>simplest way</strong> to add Google Analytics 4 (GA4) to your Mendix app.</p><p>There’s no complex setup, just follow along.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*YC7MmCl_SGERIvA90BszXw.png" /></figure><h3>What You’ll Get</h3><p>After this setup, you can:</p><ul><li>Track <strong>page visits automatically</strong></li><li>Track <strong>button clicks, and form submissions</strong></li><li>See data in <strong>real-time in Google Analytics (GA4)</strong></li><li>Understand how users use your app</li></ul><h3>Implementation</h3><h4>Step 1: Download the Google Analytics 4 widget</h4><ul><li>In Mendix Studio Pro, download the <a href="https://marketplace.mendix.com/link/component/200121"><strong>Google Analytics 4</strong></a> module from the Mendix Marketplace.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/1*wpr18AWxvlRS_QO_0mkgiw.png" /></figure><h4>Step 2: Get Your GA4 Measurement ID</h4><ul><li>Open Google Analytics.</li><li>Go to: <strong>Admin → Data collection and modification → Data Streams.</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zErltn31l9fX4gG_u4mgOg.png" /></figure><ul><li>Click on Add stream.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*clUAz7oZ3dAQ2Mt-QstVyg.png" /></figure><ul><li>Once’s you filled the Website URL and Stream name <strong>→ </strong>Copy your <strong>Measurement ID.</strong></li></ul><p>Example:</p><pre>G-XXXXXXXXXX</pre><h4><strong>Step 3: Enable Page Tracking</strong></h4><p>This step activates tracking.</p><ul><li>Open your <strong>Master Layout.</strong></li><li>Drag the GA4 widget into the layout.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1kOgvH9R5eNUCPabJUd_TA.png" /></figure><ul><li>Set the following properties:</li></ul><pre>Mode = Page tracker<br>Measurement ID = G-XXXXXXXXXX<br>Debug Mode = true (for testing)<br>Anonymize IP = true</pre><p>Now all page visits will be tracked automatically.</p><h3>Bonus Content</h3><h4>Step 4: Track a Button Click (Optional)</h4><p>You can track user actions like button clicks.</p><ul><li>Create a <strong>Nanoflow and call a Javascript action:</strong></li></ul><pre>export async function JavaScript_action() {<br> // BEGIN USER CODE<br>if (typeof window.mendixGA !== &#39;undefined&#39;) {<br>    window.mendixGA.trackEvent(&#39;button_click&#39;, {<br>        button_label: &#39;Submit&#39;,<br>        page_section: &#39;Checkout&#39;<br>    });<br>}<br> // END USER CODE<br>}</pre><p>This will send an event to GA4 when triggered</p><h4>Important Note (VERY IMPORTANT)</h4><p>window.mendixGA is ONLY available if:</p><ul><li>The widget is placed in <strong>Master Layout</strong></li><li>Mode = <strong>Page tracker</strong></li><li>Page has fully loaded</li></ul><h4>Step 5: Track Event on Page Load (No Code)</h4><p>If you want to trigger an event <strong>when a page opens</strong>, you don’t need a nanoflow.</p><ul><li>Drag the GA4 widget onto the page</li><li>Set:</li></ul><pre>Mode = Custom event<br>Event Name = page_open<br>Trigger = Page load</pre><p>Example parameters:</p><pre>page_name = Dashboard<br>user_type = Admin</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/964/1*aaRiVgW74XSfLBELhs888w.png" /></figure><p>This will automatically fire when the page loads.</p><blockquote>Note: You can combine this widget by adding Page Tracker mode in Layout and Custom event mode in page level also.</blockquote><h3>Done!</h3><p>You have successfully added <strong>Google Analytics 4 to your Mendix app</strong>.</p><p><em>If this helped you, give it a clap and share it with the your team. Follow for more quick hacks that make Mendix development faster and smarter!</em></p><h4>Read more</h4><ul><li><a href="https://developers.google.com/analytics">Google Analytics | Google for Developers</a></li><li><a href="https://docs.mendix.com/refguide/nanoflows/">Nanoflows</a></li><li><a href="https://docs.mendix.com/refguide/javascript-actions/">JavaScript Actions</a></li></ul><p><strong><em>From the Publisher -</em></strong></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=94ec16b050fa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mendix/quick-hack-series-part-2-google-analytics-4-in-mendix-94ec16b050fa">Quick Hack Series Part 2:Google Analytics 4 in Mendix</a> was originally published in <a href="https://medium.com/mendix">Mendix Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>