<?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 Narendran Jaganathan on Medium]]></title>
        <description><![CDATA[Stories by Narendran Jaganathan on Medium]]></description>
        <link>https://medium.com/@Narendran30?source=rss-8b6202c491ce------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*D9vr5EnmsR4P6THOFGpQyA@2x.jpeg</url>
            <title>Stories by Narendran Jaganathan on Medium</title>
            <link>https://medium.com/@Narendran30?source=rss-8b6202c491ce------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 00:15:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Narendran30/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[A Late-Night Security Mystery: A Mendix Story]]></title>
            <link>https://medium.com/mendix/a-late-night-security-mystery-a-mendix-story-17fe1e643260?source=rss-8b6202c491ce------2</link>
            <guid isPermaLink="false">https://medium.com/p/17fe1e643260</guid>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[low-code]]></category>
            <category><![CDATA[security-audit]]></category>
            <dc:creator><![CDATA[Narendran Jaganathan]]></dc:creator>
            <pubDate>Thu, 15 Jan 2026 13:47:13 GMT</pubDate>
            <atom:updated>2026-01-15T13:47:13.147Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A Late-Night Security Mystery: A Mendix Story (banner Image)" src="https://cdn-images-1.medium.com/max/1024/1*_VOTJqWEfO8-PSlHvDB0MQ.png" /><figcaption>A Late-Night Security Mystery: A Mendix Story</figcaption></figure><h4>You’ve seen this before.</h4><h4>A field is hidden.<br>A page is read-only.<br>The user <em>shouldn’t</em> be able to change anything.</h4><p>Yet somehow… data changes.</p><p>This is a short story about why that happens — and how to verify Mendix security in <strong>5 minutes</strong>, using nothing but your browser.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jms36MbQ4AK7QqMStayrzg.png" /><figcaption>Late night security debugging</figcaption></figure><h3>The Problem: UI ≠ Security</h3><p>In Mendix, we often trust the UI:</p><ul><li>No edit button → “safe.”</li><li>Field hidden → “safe.”</li><li>Page read-only → “safe.”</li></ul><p>However, Mendix apps don’t only live in pages.</p><p>They also live in:</p><ul><li>Client APIs</li><li>REST calls</li><li>Browser memory</li></ul><p>So the real question is:</p><blockquote><strong><em>What can the logged-in users actually read or write at runtime?</em></strong></blockquote><h3>The Shortcut: Ask the Browser</h3><p>Instead of guessing, we let the browser answer.</p><h3>How to Run the Check (30 seconds)</h3><ol><li>Open your Mendix app in <strong>Chrome</strong></li><li>Press <strong>F12</strong></li><li>Go to <strong>Sources → Snippets → New snippet</strong></li><li>Paste the script below</li><li>Press <strong>Ctrl + Enter<br></strong>Make sure pop-ups are allowed</li></ol><p>A new window opens.</p><p>That’s where the truth lives.</p><h3>What You’ll See</h3><p>At the top: A dropdown with <strong>all entities accessible</strong> to the current user.</p><p>Select one.</p><p>A table appears:</p><ul><li>Rows = objects</li><li>Columns = attributes</li></ul><h3>Color code (this is the key part):</h3><p>🟩 <strong>Green</strong> = writable<br>⬜ <strong>Normal</strong> = read-only</p><p>No UI logic.<br>No assumptions.<br>Just runtime access.</p><h3>The “Oh…” Moment</h3><p>This is usually where it clicks.</p><p>You’ll notice:</p><ul><li>Attributes you <em>thought</em> were protected</li><li>Entities accessible via client calls</li><li>Fields are writable even though the UI blocks them</li></ul><p>That’s how:</p><ul><li>REST updates happen “by accident.”</li><li>Data changes without UI actions</li><li>Security bugs survive testing</li></ul><p>The UI wasn’t lying. It just wasn’t telling the whole story.</p><h3>The Script</h3><pre>function addCellText(d,r,t,h,ro){<br> var c=r.insertCell();<br> c.appendChild(d.createTextNode(t));<br> c.style.border=&#39;1px solid #000&#39;;<br> if(h) c.style.background=&#39;#ddd&#39;;<br> if(!ro) c.style.background=&#39;#00ff00&#39;;<br>}<br><br>var w=window.open(), m=mx.meta.getMap(), d=w.document, b=d.body;<br>var s=d.createElement(&quot;select&quot;); b.appendChild(s);<br>s.add(new Option(&quot;&quot;,&quot;&quot;));<br><br>Object.keys(m).sort().forEach(e=&gt;s.add(new Option(e,e)));<br><br>s.onchange=function(){<br> mx.data.get({ xpath:&quot;//&quot;+this.value, callback:function(data){<br>  var t=d.getElementById(&quot;tab&quot;); if(t) t.remove();<br>  if(!data.length) return;<br>  var a=mx.meta.getEntity(s.value).getAttributes();<br>  t=d.createElement(&quot;table&quot;); t.id=&quot;tab&quot;; b.appendChild(t);<br>  var r=t.insertRow(); addCellText(d,r,&quot;guid&quot;,1,1);<br>  a.forEach(x=&gt;addCellText(d,r,x,1,1));<br>  data.forEach(o=&gt;{<br>   r=t.insertRow(); addCellText(d,r,o.getGuid(),0,1);<br>   a.forEach(x=&gt;{<br>    var v=o.jsonData.attributes[x]||{};<br>    addCellText(d,r,v.value||&quot;&quot;,0,v.readonly);<br>   });<br>  });<br> }});<br>}</pre><h3>When Should You Use This?</h3><p>Use it when:</p><ul><li>Auditing an app</li><li>Debugging “impossible” data changes</li><li>Reviewing security before go-live</li><li>Validating REST exposure</li></ul><p>Think of it as a <strong>runtime security X-ray</strong>.</p><h3>Final Takeaway</h3><p>If you remember one thing:</p><blockquote><strong><em>Pages hide data.<br>Security decides access.<br>The browser reveals the truth.</em></strong></blockquote><p>Five minutes. One script. No more guessing. Happy securing!</p><h4>Read more</h4><p><a href="https://docs.mendix.com/refguide/security/">Security</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=17fe1e643260" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mendix/a-late-night-security-mystery-a-mendix-story-17fe1e643260">A Late-Night Security Mystery: A Mendix Story</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[How to Securely Upgrade Mendix Apps and the SAML Module]]></title>
            <link>https://medium.com/mendix/how-to-securely-upgrade-mendix-apps-and-the-saml-module-fd402e2f430f?source=rss-8b6202c491ce------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd402e2f430f</guid>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[saml2]]></category>
            <category><![CDATA[saml]]></category>
            <category><![CDATA[low-code]]></category>
            <dc:creator><![CDATA[Narendran Jaganathan]]></dc:creator>
            <pubDate>Tue, 25 Mar 2025 14:55:05 GMT</pubDate>
            <atom:updated>2025-03-25T14:55:05.688Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="How to Securely Upgrade Mendix Apps and the SAML Module (Banner Image)" src="https://cdn-images-1.medium.com/max/1024/1*cn77Z9ClQyNScVDX4N3sRA.png" /><figcaption>How to Securely Upgrade Mendix Apps and the SAML Module</figcaption></figure><h4>The SAML module in Mendix enables Single Sign-On (SSO) by securely integrating your app with external identity providers such as Azure AD. This module facilitates encrypted data exchanges, simplifying user access management and enhancing security. Keeping your Mendix app and the SAML module up-to-date is critical for maintaining security, compatibility, and performance.</h4><p><strong>This guide provides step-by-step instructions on upgrading your Mendix app and the SAML module to the latest secure versions.</strong></p><h3>SAML Authentication Protocol</h3><p>SAML (Security Assertion Markup Language) is an open standard that allows secure authentication and authorization between identity providers and service providers. It ensures a seamless Single Sign-On (SSO) experience and robust data security.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jk4EVU9BRDRimcUxf313gA.jpeg" /><figcaption>SAML Authentication Protocol</figcaption></figure><p>Upgrading both your Mendix project and the SAML module to the latest versions is essential for maintaining application integrity and compliance with modern security standards.</p><h3>Steps to Upgrade</h3><h4>1. Upgrade the Mendix Project</h4><ul><li><strong>For Mendix 7:</strong> Update your app to version 7.23.23.</li><li><strong>For Mendix 8:</strong> Update your app to version 8.18.9.</li></ul><p>Ensure that any deprecated features are addressed and check the Mendix release notes for any breaking changes.</p><h4>2. Update the SAML Module</h4><ul><li><strong>For Mendix 7 Apps:</strong> Download SAML module version 1.15.4 or later (this version includes a fix for Azure integration).</li><li><strong>For Mendix 8 Apps:</strong> Download SAML module version 2.1.4 or later (this version includes a fix for Azure integration).</li></ul><h4>3. Ensure Compatibility</h4><ul><li>Run the project locally to confirm that the Java code compiles successfully.</li><li>Upgrading modules may introduce conflicts in JAR files, which you can identify during local testing.</li></ul><h4>4. Commit Changes</h4><p>Once the project runs without errors, commit the changes to your version control system.</p><h4>5. Deploy to QA</h4><p>Deploy the updated application to your QA environment for further testing.</p><h4>6. Test SSO Functionality</h4><ul><li>Verify that Single Sign-On (SSO) is functioning as expected.</li><li>Test all workflows that rely on the SAML module.</li></ul><p>Troubleshooting Common Issues</p><h4>Issue 1: Error with SAML v2.15.3</h4><p><strong>Problem:</strong><br>An error such as &quot;org.opensaml.xml.signature.impl.CryptoBinaryBuilder cannot be cast to org.opensaml.core.xml.XMLObjectBuilder&quot; occurs when logging in with SSO in the cloud or editing the SAML configuration.</p><p><strong>Solution:</strong></p><ol><li>Remove the JAR file org.apache.servicemix.bundles.opensaml-2.6.0_3 from the userlib folder.</li><li>Clean the deployment directory.</li><li>Retest the application.</li></ol><h4>Issue 2: Java Code Compilation Errors</h4><p><strong>Problem:</strong><br>Compilation errors, like &quot;cannot find symbol&quot;, may appear when running the project locally. These errors are typically caused by conflicting JAR files in the userlib folder.</p><p><strong>Solution:</strong></p><ol><li>Open your project in Eclipse.</li><li>Identify the Java file causing the error (it will display an error message in Eclipse).</li><li>Use <strong>CTRL + SHIFT + T</strong> in Eclipse to search for the conflicting class.</li><li>Look for duplicate libraries in the userlib folder.</li><li>Delete the older versions of the conflicting libraries.</li><li>Clean the deployment directory in Mendix Studio Pro.</li><li>Retest the project locally.</li></ol><h4>Issue 3: APPLICATION_SOAP_XML Errors</h4><p><strong>Problem:</strong><br>Errors like &quot;cannot find symbol: variable APPLICATION_SOAP_XML&quot; appear during Java compilation.</p><p><strong>Solution:</strong></p><ol><li>Remove the following JAR files from the userlib folder:</li></ol><ul><li>httpcore-4.4.11</li><li>org.apache.servicemix.bundles.opensaml-2.6.0_3</li></ul><p>2. Clean the deployment directory in Mendix Studio Pro.</p><p>3. Rebuild the project and test again.<br><br>Example Error Resolution</p><p><strong>Example Error:</strong></p><blockquote>Compiling 100 source files to C:\Mendix\TestApp-main\deployment\run\bin<br>C:\Mendix\TestApp-main\javasource\saml20\implementation\DelegatedAuthenticationHandler.java:308: error: cannot find symbol<br>httpPost.setEntity(new ByteArrayEntity(authnState.getModifiedSOAPRequest().getBytes(), ContentType.APPLICATION_SOAP_XML));<br>^<br>symbol: variable APPLICATION_SOAP_XML<br>location: class ContentType</blockquote><p><strong>Solution:</strong></p><ol><li>Remove the conflicting JAR files as outlined in <strong>Issue 2: Java Code Compilation Errors</strong>.</li><li>Clean and rebuild the project.</li></ol><p>For more details, refer to this <a href="https://community.mendix.com/link/space/app-development/questions/108258">Mendix Forum discussion</a>.</p><h3>Conclusion</h3><p>Following this step-by-step guide, you can upgrade your Mendix app and the SAML module to the latest secure versions, ensuring minimal downtime and enhanced security. Regularly upgrading your Mendix app and its components is essential for maintaining functionality and security in a rapidly changing technology landscape.</p><h4>References</h4><ul><li><a href="https://community.mendix.com/link/space/app-development/questions/107752">Mendix Forum</a></li><li><a href="https://community.mendix.com/link/space/app-development/questions/108258">Mendix Forum</a></li><li><a href="https://community.mendix.com/link/space/security/questions/108581">Mendix Forum</a></li></ul><h4>Read more</h4><p><a href="https://docs.mendix.com/appstore/modules/saml/">SAML</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd402e2f430f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mendix/how-to-securely-upgrade-mendix-apps-and-the-saml-module-fd402e2f430f">How to Securely Upgrade Mendix Apps and the SAML Module</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[Implementing Base64 in the Take Picture Javascript Action]]></title>
            <link>https://medium.com/mendix/implementing-base64-in-take-picture-activity-using-mendix-native-an-easy-and-efficient-method-e4047a2aba99?source=rss-8b6202c491ce------2</link>
            <guid isPermaLink="false">https://medium.com/p/e4047a2aba99</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[file-handling]]></category>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Narendran Jaganathan]]></dc:creator>
            <pubDate>Thu, 09 Feb 2023 12:29:15 GMT</pubDate>
            <atom:updated>2023-04-13T10:24:20.042Z</atom:updated>
            <content:encoded><![CDATA[<h4>An Easy and Efficient Method for Mendix Native Mobile</h4><figure><img alt="Implementing Base64 in the Take Picture Javascript Action — an atrial view of a waterfall, but the image is split in half and connected in the middle in a prism-like way" src="https://cdn-images-1.medium.com/max/1024/1*HC7t07c9dtBIQhbzRDjELQ.png" /><figcaption>Implementing Base64 in the Take Picture Javascript Action — an aerial view of a waterfall, but the image is split in half and connected in the middle in a prism-like way</figcaption></figure><p>I recently attempted to include a “Take Picture” functionality in my native mobile app, with the intention of storing the image as a base 64 encoded string. However, I encountered a challenge when I discovered that the existing “Take Picture” activity in Mendix only accepted the image as an object. To resolve this issue, I decided to customize the existing JavaScript action to incorporate the necessary code:</p><p><strong>You can download the Module from the Mendix Market Place here,<br></strong><a href="https://marketplace.mendix.com/link/component/205786">https://marketplace.mendix.com/link/component/205786</a></p><h4><strong>Introduction:</strong></h4><p>As I have explored various online forums, I have come across several discussions on the issue of synchronizing multiple image objects in native applications. In this scenario, a user visits a site and captures multiple images using the “TakePictureActivity.” However, the synchronization process can be time-consuming as it takes time to synchronize and store the images in the database.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*YhWAeyl_Cort-keQrVr05g.jpeg" /><figcaption>Image to base64 Conversion</figcaption></figure><p>To overcome this challenge, we have developed an innovative solution to synchronize images as base64. By converting the images into base64 objects before committing them to the database, we can significantly reduce the synchronization time and make it more efficient, even in low bandwidth networks.</p><h4><strong>Streamlined Approach:</strong></h4><p>For each “site” entity, multiple images can be captured and stored in the “siteImages” entity. During the image capture process, the <strong>TakePictureActivity</strong> will be executed, and the images will be converted into base64 using the following code:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*2SGFYiC8I8Yl3zxPe-aOng.png" /><figcaption>Domain Model</figcaption></figure><h4><strong>Code explanation:</strong></h4><p>Created an entity SiteImages and stored the base64 value in the Base64 attribute.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*x1ug5gZm1-q_AC9MeWKY9A.png" /><figcaption>Javascript action Parameter mapping</figcaption></figure><p>Created a new JavaScript action to handle the base64 content once a picture is captured.</p><p>1. Added a new parameter</p><p>2. Name: imgObj,</p><p>3. Type: object</p><h4><strong>Using react-native-image-picker library</strong></h4><p>1. Creating variable imagebase64 and returning the stored file</p><p>2. Added an imgObj on the export function</p><pre>export async function TakePicture_ImageToBase64_StopPhoto(picture, pictureSource, pictureQuality, maximumWidth, maximumHeight, imgObj) {<br>    // BEGIN USER CODE<br>    var imagebase64; // variable created<br>    try {<br>        const uri = await takePicture();<br>        if (!uri) {<br>            return false;<br>        }<br>        return storeFile(picture, uri, imagebase64); // return store files<br>    }<br>    catch (error) {<br>        if (error === &quot;canceled&quot;) {<br>            return false;<br>        }<br>        throw new Error(error);<br>    }<br>}</pre><p>1. Print the base64 working on the console log and the response on the console and store it in the created variable imagebase64 and check the response when a picture is not taken.</p><p>2. Instead of returning an undefined variable replaced with a response</p><p>3. For error handling.</p><pre>getPictureMethod()<br>    .then(method =&gt; method(options, (response) =&gt; {<br>        console.log(&#39;base64 working&#39;)<br>        console.log(response); // get response as base64<br>        //Check empty on response when the picture is not taken.<br>        if (response.assets == undefined) {<br>            return resolve(response);<br>        } else {<br>            imagebase64 = response.assets[0].base64;<br>        }<br>        if (response.didCancel) {<br>            return resolve(response); //returns the response of base64<br>            // return resolve(undefined);<br>        }<br>        if (nativeVersionMajor === 2) {<br>            response = response;<br>            if (response.error) {<br>                const unhandledError = handleImagePickerV2Error(response.error);<br>                if (!unhandledError) {<br>                    return resolve(undefined);<br>                }<br>                return reject(new Error(response.error));<br>            }<br>            return resolve(response);<br>        }<br>        response = response;<br>        if (response.errorCode) {<br>            handleImagePickerV4Error(response.errorCode, response.errorMessage);<br>            return resolve(undefined);<br>        }<br>        //Empty check undefined condition for the asset object to prevent system admin error<br>        if (response.assets == undefined) {<br>            return resolve(response);<br>        } else {<br>            return resolve(response.assets[0].uri);<br>        }<br>    }))<br>    .catch(error =&gt; reject(error));<br>});<br>}</pre><p>1. Set the <strong>exact attribute name used on the $siteImages entity</strong></p><p>Eg: Base64</p><pre>imageObject.set(“Name”, filename);<br>imageObject.set(“Base64”, imagebase64); // set attribute value eg:Base64</pre><p>Include base64 as true to enable it.</p><pre>return {<br>    mediaType: &quot;photo&quot;,<br>    includeBase64: true, // if not needed Base64 false<br>    function getOptionsV4() {<br>    const { maxWidth, maxHeight } = getPictureQuality();<br>    return {<br>        mediaType: &quot;photo&quot;,<br>        includeBase64: true, // if not needed Base64 false<br>        maxWidth,<br>        maxHeight<br>    };<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*87JdvsliemOp9zLkAmXiXA.png" /><figcaption>Take a picture as base64 activity</figcaption></figure><p>The siteImages entity now holds both images and their respective base64 values, however, due to the complexity of synchronizing both types of data, we have decided to only synchronize the base64 values. To achieve this, we have created a separate entity called imageBase64 to store the list of base64 values.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*jPaFhcqR98f2f2lwYAUdfg.png" /><figcaption>synchronizing to server</figcaption></figure><p>The siteImages entity is used to create a list of imageBase64 values, which is the only data that is synchronized. When it comes to committing the imageBase64 entity to the server, we have added a crucial step to the process. Before committing, an event handler is triggered to convert the imageBase64 values back into images, which are then committed to the siteImages entity and linked to the corresponding sites.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*jSFUEdj2YGNxmFgGbX5P6g.png" /><figcaption>base64 to image using java action.</figcaption></figure><p>Finally, the above-mentioned methodology will optimize the synchronization process of large image files, ensuring that they are transferred as efficiently as possible even in low network conditions (2G or 3G). This will significantly reduce the time it takes to synchronize these large files.</p><h4>Read more</h4><ul><li><a href="https://docs.mendix.com/howto/extensibility/write-javascript-actions/">Build JavaScript Actions: Part 1 (Basic)</a></li><li><a href="https://docs.mendix.com/howto/extensibility/write-javascript-github/">Build JavaScript Actions: Part 2 (Advanced)</a></li><li><a href="https://docs.mendix.com/howto/extensibility/best-practices-javascript-actions/">Implement Best Practices for JavaScript Actions</a></li><li><a href="https://www.npmjs.com/package/react-native-image-picker">react-native-image-picker</a></li></ul><p><em>From the Publisher -</em></p><p><em>If you enjoyed this article you could find more on our </em><a href="https://medium.com/mendix"><em>Medium page</em></a><em>. For great videos and live sessions, you can go to </em><a href="https://www.mendix.com/live/"><em>MxLive</em></a><em> or our community </em><a href="https://www.youtube.com/c/MendixCommunity/community"><em>Youtube pag</em></a><em>e.</em></p><p><em>For the makers looking to get started, you can sign up for a </em><a href="https://signup.mendix.com/link/signup/?source=direct"><em>free account</em></a><em>, and get instant access to learning with our </em><a href="https://academy.mendix.com/link/home"><em>Academy</em></a><em>.</em></p><p><em>Interested in getting more involved with 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>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4047a2aba99" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mendix/implementing-base64-in-take-picture-activity-using-mendix-native-an-easy-and-efficient-method-e4047a2aba99">Implementing Base64 in the Take Picture Javascript Action</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>