<?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 Sathish Kumar on Medium]]></title>
        <description><![CDATA[Stories by Sathish Kumar on Medium]]></description>
        <link>https://medium.com/@rocksathish34?source=rss-603718245214------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*jZWIOdR5Uskg9xh0IWTarQ.jpeg</url>
            <title>Stories by Sathish Kumar on Medium</title>
            <link>https://medium.com/@rocksathish34?source=rss-603718245214------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 18:03:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rocksathish34/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[The Seven Tokens That Make Date Math in Mendix XPath Painless]]></title>
            <link>https://medium.com/@rocksathish34/the-seven-tokens-that-make-date-math-in-mendix-xpath-painless-5bf269cc0836?source=rss-603718245214------2</link>
            <guid isPermaLink="false">https://medium.com/p/5bf269cc0836</guid>
            <category><![CDATA[xpath]]></category>
            <category><![CDATA[siemens]]></category>
            <category><![CDATA[token]]></category>
            <category><![CDATA[mendix]]></category>
            <dc:creator><![CDATA[Sathish Kumar]]></dc:creator>
            <pubDate>Tue, 01 Sep 2026 13:26:43 GMT</pubDate>
            <atom:updated>2026-09-01T13:26:43.313Z</atom:updated>
            <content:encoded><![CDATA[<p>Stop building “last 30 days” filters in microflows. Mendix has had a one-liner for this since version 3.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m1wanqR_7HoH85Ly74ZNPg.png" /></figure><p>Every Mendix developer eventually writes the same retrieve: <em>give me the orders from the last 30 days</em>. The reflex is to create a variable, call addDays([%CurrentDateTime%], -30), pass it into the XPath, and move on. It works. It&#39;s also three steps for something Mendix XPath can do in one.</p><p>The trick is a small, easily overlooked group of system variables called the <strong>period tokens</strong>.</p><h3>Meet the period tokens</h3><p>Mendix XPath ships with two families of time-related system variables. The first family gives you <em>points</em> in time — [%CurrentDateTime%], [%BeginOfCurrentDay%], [%EndOfCurrentWeek%], and friends. The second family gives you <em>lengths</em> of time:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8kNZpsg61iecWKSdnRUxHQ.png" /></figure><p>On their own, a length is not very useful. Combined with a point-in-time token, they let you shift a date forward or backward directly inside the constraint — no microflow variable needed.</p><h3>How the expression fits together</h3><p>The pattern is always the same: <strong>anchor ± multiplier × length</strong>, and the whole thing sits inside a single pair of quotes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*snIxHCTfMh0Cww5M2CFfUQ.png" /></figure><pre>[OrderDate &gt;= &#39;[%CurrentDateTime%] - 30 * [%DayLength%]&#39;]</pre><p>The quotes matter. Mendix resolves the tokens and evaluates the arithmetic <em>before</em> the query reaches the database, and it only does that for text it recognises as a system-variable string. Split the expression across two strings, or drop the quotes, and Studio Pro will reject it.</p><p>Here is what that constraint actually selects:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JZXytOiFTJ8nM-Cy8m39-Q.png" /></figure><h3>A quick tour of the history</h3><p>If you’re wondering whether these are a recent addition — they are not. The period tokens are part of the <em>original</em> set of XPath system variables:</p><ul><li>They appear in the <strong>Mendix 3</strong> reference guide. The Community Commons XPath.java helper still carries a comment linking to the <em>refguide3</em> page for its list of built-in tokens.</li><li>The <strong>Mendix 4</strong> Runtime API documents Core.resolveTokens() with all seven tokens — SecondLength through YearLength — already present.</li><li>Since then they’ve survived every major release unchanged. The Studio Pro 11 documentation lists exactly the same seven tokens, with the same descriptions.</li></ul><p>The one meaningful expansion came with OQL: the current docs state that all time-related XPath variables and expressions, including the period arithmetic, are supported in OQL queries too. So &#39;[%BeginOfCurrentDay%] - 3 * [%YearLength%]&#39; works in a dataset or an OQL Java action just as it does in an XPath constraint.</p><p>In other words: this is one of the most stable pieces of syntax in the platform. Anything you learn here will work on any Mendix version you’re likely to encounter.</p><h3>Practical examples</h3><p><strong>Orders from the last 30 days</strong> (Retrieve activity, data grid, or list view):</p><pre>[OrderDate &gt;= &#39;[%CurrentDateTime%] - 30 * [%DayLength%]&#39;]</pre><p><strong>Sessions active in the last hour</strong> (great for a “who’s online” dashboard):</p><pre>[LastActivity &gt;= &#39;[%CurrentDateTime%] - [%HourLength%]&#39;]</pre><p>No multiplier needed when you want exactly one unit.</p><p><strong>Tasks due in the next two weeks</strong>, anchored to midnight so the window doesn’t drift during the day:</p><pre>[DueDate &gt;= &#39;[%BeginOfCurrentDay%]&#39; and DueDate &lt; &#39;[%BeginOfCurrentDay%] + 2 * [%WeekLength%]&#39;]</pre><p><strong>Customers who registered in the past three years</strong> — the example straight from the Mendix docs:</p><pre>[DateRegistered &gt; &#39;[%BeginOfCurrentDay%] - 3 * [%YearLength%]&#39;]</pre><p><strong>Access rules.</strong> Because these are plain XPath constraints, they work in entity access rules too. A “support agents can only see tickets created in the last 90 days” rule becomes:</p><pre>[CreatedDate &gt;= &#39;[%CurrentDateTime%] - 90 * [%DayLength%]&#39;]</pre><p>No scheduled event, no flag attribute, no maintenance.</p><p><strong>Java actions.</strong> In Java you write the full query, entity and all:</p><p>java</p><pre>List&lt;IMendixObject&gt; recent = Core.createXPathQuery(<br>    &quot;//Sales.Order[OrderDate &gt;= &#39;[%CurrentDateTime%] - 7 * [%DayLength%]&#39;]&quot;<br>).execute(context);</pre><h3>Things that will trip you up</h3><p><strong>One string, always.</strong> &#39;[%CurrentDateTime%]&#39; - 30 * &#39;[%DayLength%]&#39; is not valid. Keep the anchor, the operator, the multiplier and the length inside the same quotes.</p><p><strong>No parentheses.</strong> Because the expression is a string, you can’t group sub-expressions with brackets. Keep it to a single + or - step. If you need something more elaborate, compute it in a microflow variable.</p><p><strong>No arithmetic outside tokens.</strong> The XPath reference is explicit: mathematical expressions are only evaluated inside these token strings. [Amount &gt; 100 * 2] won&#39;t work; &#39;[%CurrentDateTime%] - 2 * [%HourLength%]&#39; will.</p><p><strong>Pick your anchor deliberately.</strong> [%CurrentDateTime%] gives a rolling window that shifts every second. [%BeginOfCurrentDay%] gives a window that stays put until midnight — usually what users expect on a report. Both respect the user&#39;s time zone; the UTC variants exist if you need server-absolute boundaries.</p><p><strong>Month and year are lengths, not calendar boundaries.</strong> [%MonthLength%] shifts you by a fixed amount of time, not to &quot;the same day last month&quot;. When the calendar boundary is what matters — <em>this month&#39;s invoices</em> — use [%BeginOfCurrentMonth%] and [%EndOfCurrentMonth%] instead, and reserve the length tokens for rolling windows.</p><h3>Wrapping up</h3><p>Seven tokens, one pattern, zero microflow overhead. The period tokens have been sitting quietly in Mendix XPath since the platform’s early days, and they turn most “relative date” filters into a single readable line. Next time you reach for addDays() before a retrieve, try the constraint first.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5bf269cc0836" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enhance Mobile User Experience with the Mendix Bottom Sheet Widget]]></title>
            <link>https://medium.com/@rocksathish34/enhance-mobile-user-experience-with-the-mendix-bottom-sheet-widget-60e15ff2efa6?source=rss-603718245214------2</link>
            <guid isPermaLink="false">https://medium.com/p/60e15ff2efa6</guid>
            <category><![CDATA[siemens]]></category>
            <category><![CDATA[native]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[widget]]></category>
            <dc:creator><![CDATA[Sathish Kumar]]></dc:creator>
            <pubDate>Fri, 17 Jul 2026 14:47:42 GMT</pubDate>
            <atom:updated>2026-07-17T14:47:42.965Z</atom:updated>
            <content:encoded><![CDATA[<p>Mobile users expect applications to be fast, intuitive, and responsive. Navigating through multiple screens just to view details or perform simple actions can interrupt workflows and reduce productivity. In enterprise applications, where users frequently access large volumes of data, minimizing unnecessary navigation is essential.</p><p>The <strong>Bottom Sheet Widget</strong> in Mendix Native Mobile addresses this challenge by providing a modern, contextual user interface that allows users to access information and perform actions without leaving the current screen. This interaction pattern is widely used in Android and iOS applications and enables developers to create smoother, more engaging mobile experiences.</p><h3>What is a Bottom Sheet?</h3><p>A <strong>Bottom Sheet</strong> is a panel that slides up from the bottom of the screen to display additional content while keeping the current page visible in the background. Instead of navigating to a new page, users can quickly view information, edit data, or trigger actions within the same context.</p><p>This design pattern helps maintain focus, reduces navigation overhead, and creates a seamless user experience.</p><p>In Mendix Native Mobile applications, the Bottom Sheet Widget becomes even more powerful when combined with <strong>Nanoflows</strong>, <strong>Microflows</strong>, and <strong>dynamic data binding</strong>, making it suitable for a wide range of enterprise use cases.</p><h3>Why Use the Bottom Sheet Widget?</h3><p>Traditional mobile applications often require users to navigate through several screens:</p><p><strong>List Page → Detail Page → Action Page → Back Navigation</strong></p><p>Although functional, this workflow can become repetitive and time-consuming, especially in applications such as CRM, field service, inventory management, or sales.</p><p>With the Bottom Sheet Widget, the workflow becomes much simpler:</p><p><strong>List Page → Bottom Sheet → Perform Action</strong></p><p>This approach offers several advantages:</p><ul><li>Faster task completion</li><li>Reduced navigation between screens</li><li>Improved user satisfaction</li><li>Better mobile responsiveness</li><li>Native-like user experience consistent with Android and iOS design principles</li></ul><h3>Understanding the Bottom Sheet Widget</h3><p>The Bottom Sheet Widget acts as a flexible container capable of displaying virtually any UI component.</p><p>It can contain:</p><ul><li>Data Views</li><li>Lists</li><li>Text</li><li>Images</li><li>Buttons</li><li>Forms</li><li>Input fields</li><li>Nested layouts</li></ul><p>The widget is typically opened using a <strong>Nanoflow</strong> or <strong>Microflow</strong>, allowing it to display dynamic content based on the user’s current selection.</p><h3>Real-World Example: Sales CRM Mobile Application</h3><p>Let’s consider a realistic enterprise scenario.</p><p>A sales representative opens a <strong>Customer List</strong> containing hundreds of customer records.</p><p>Instead of navigating to a separate customer detail page, selecting a customer opens a Bottom Sheet containing key information and quick actions.</p><h3>Customer Summary</h3><ul><li>Customer Name</li><li>Industry</li><li>Account Tier (Gold, Silver, Bronze)</li><li>Active Status</li></ul><h3>Contact Information</h3><ul><li>Phone Number (Click-to-Call)</li><li>Email Address</li><li>Location (Open in Maps)</li></ul><h3>Business Information</h3><ul><li>Last Order Date</li><li>Total Revenue</li><li>Pending Invoices</li></ul><h3>Quick Actions</h3><ul><li>Create Order</li><li>Schedule Meeting</li><li>Update Customer Status</li><li>View Full Customer Profile</li></ul><p>This enables field sales representatives to complete common tasks much faster without repeatedly switching between pages.</p><h3>How the Bottom Sheet Works in Mendix</h3><p>The implementation follows a straightforward sequence of events.</p><h3>Step 1: User Interaction</h3><p>The user taps a customer record or action button.</p><h3>Step 2: Execute a Nanoflow</h3><p>The Nanoflow:</p><ul><li>Stores the selected customer</li><li>Updates the page context</li><li>Prepares the data for display</li></ul><h3>Step 3: Open the Bottom Sheet</h3><p>The Bottom Sheet Widget becomes visible based on the updated application state.</p><h3>Step 4: Bind Data</h3><p>A Data View inside the Bottom Sheet displays the selected customer information dynamically.</p><h3>Step 5: Execute Actions</h3><p>Users can perform various operations through buttons inside the Bottom Sheet, including:</p><ul><li>Calling Microflows for server-side business logic</li><li>Executing Nanoflows for client-side actions</li><li>Navigating to detailed pages when necessary</li><li>Triggering REST integrations</li></ul><h3>Step-by-Step Implementation Guide</h3><h3>Step 1: Install the Widget</h3><ul><li>Open the Mendix Marketplace.</li><li>Install the <strong>Bottom Sheet Widget</strong>.</li><li>Add it to your Native Mobile application module.</li></ul><h3>Step 2: Create the Domain Model</h3><p>Example entity:</p><p><strong>Customer</strong></p><p>AttributeTypeNameStringEmailStringPhoneStringStatusEnumerationRevenueDecimal</p><h3>Step 3: Add the Bottom Sheet to a Native Mobile Page</h3><p>Drag the widget onto the page and configure its behavior.</p><p>Typical settings include:</p><ul><li>Initial state (Collapsed or Expanded)</li><li>Enable or disable dragging</li><li>Close when tapping outside the sheet</li></ul><h3>Step 4: Bind the Data Context</h3><p>Use a selected Customer object stored through a Nanoflow or passed as a page parameter.</p><p>The Data View inside the Bottom Sheet automatically displays the selected customer’s information.</p><h3>Step 5: Design the User Interface</h3><p>A typical Bottom Sheet layout includes:</p><h3>Header</h3><ul><li>Customer Name</li><li>Status</li></ul><h3>Body</h3><ul><li>Contact Details</li><li>Business Information</li><li>Additional Attributes</li></ul><h3>Footer</h3><ul><li>Action Buttons</li></ul><p>This structured layout keeps information organized and easy to access.</p><h3>Step 6: Open the Bottom Sheet</h3><p>Configure the Customer List item.</p><p>On tap:</p><ul><li>Execute a Nanoflow</li><li>Set the selected customer</li><li>Open the Bottom Sheet</li></ul><p>The user immediately sees the contextual information without leaving the current screen.</p><h3>Step 7: Add Interactive Actions</h3><p>The Bottom Sheet can execute different types of actions.</p><p>Examples include:</p><ul><li><strong>Microflow</strong> — Create Customer Order</li><li><strong>Nanoflow</strong> — Launch Maps</li><li><strong>REST Call</strong> — Synchronize Customer Status</li><li><strong>Navigation</strong> — Open Full Customer Profile</li></ul><p>This makes the Bottom Sheet far more than a simple information panel — it becomes an interactive workspace.</p><h3>Common Enterprise Use Cases</h3><h3>CRM Applications</h3><ul><li>Customer preview</li><li>Lead qualification</li><li>Quick status updates</li><li>Sales follow-up actions</li></ul><h3>Field Service Management</h3><ul><li>View assigned jobs</li><li>Update work status</li><li>Assign technicians</li><li>Capture service information</li></ul><h3>E-Commerce Applications</h3><ul><li>Product quick view</li><li>Add to Cart</li><li>Product comparison</li><li>Filter and sorting options</li></ul><h3>Inventory Management</h3><ul><li>View stock details</li><li>Update inventory status</li><li>Scan product information</li><li>Perform warehouse actions</li></ul><h3>Approval Workflows</h3><ul><li>Review requests</li><li>Approve or reject submissions</li><li>View comments</li><li>Add remarks</li></ul><h3>Performance Best Practices</h3><p>To ensure smooth performance in Native Mobile applications, consider the following recommendations.</p><h3>Load Only Essential Data</h3><p>Display summary information in the Bottom Sheet and retrieve detailed data only when required.</p><h3>Prefer Nanoflows for UI Logic</h3><p>Use Nanoflows for temporary UI state management to minimize unnecessary server communication.</p><h3>Implement Lazy Loading</h3><p>Load additional sections only when users expand or request them.</p><h3>Keep the Layout Lightweight</h3><p>Avoid deeply nested layouts, large data grids, or high-resolution images that may impact rendering performance.</p><h3>Benefits of Using the Bottom Sheet Widget</h3><p>Implementing the Bottom Sheet Widget in Mendix Native Mobile applications provides several advantages:</p><ul><li>Reduces navigation between screens</li><li>Maintains user context</li><li>Improves task completion speed</li><li>Delivers a native mobile experience</li><li>Simplifies complex workflows</li><li>Enhances user productivity</li><li>Creates cleaner and more intuitive interfaces</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZWULUOOudXkPhByG93mWmQ.png" /></figure><h3>Conclusion</h3><p>The <strong>Bottom Sheet Widget</strong> is much more than a visual component — it’s a modern interaction pattern that significantly enhances the user experience in Mendix Native Mobile applications.</p><p>By allowing users to stay within the current context while accessing additional information and performing quick actions, developers can build applications that are faster, more intuitive, and more productive.</p><p>Whether you’re developing a CRM, field service solution, inventory application, or approval workflow, the Bottom Sheet Widget helps reduce navigation complexity and delivers the polished, native-like experience that modern mobile users expect.</p><p>If you’re building your next Mendix Native Mobile application, incorporating the Bottom Sheet Widget is a simple yet powerful way to elevate usability and create a more efficient mobile experience.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60e15ff2efa6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Advanced Teamcenter Integration Features in Mendix]]></title>
            <link>https://medium.com/@rocksathish34/advanced-teamcenter-integration-features-in-mendix-4f26b8ddca45?source=rss-603718245214------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f26b8ddca45</guid>
            <category><![CDATA[teamcenter]]></category>
            <category><![CDATA[plm]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[manufacturing]]></category>
            <category><![CDATA[siemens]]></category>
            <dc:creator><![CDATA[Sathish Kumar]]></dc:creator>
            <pubDate>Mon, 13 Jul 2026 15:09:16 GMT</pubDate>
            <atom:updated>2026-07-13T15:09:16.120Z</atom:updated>
            <content:encoded><![CDATA[<p>Advanced Teamcenter–Mendix Integration: Datasets, Relationships, and Queries</p><h3>Introduction</h3><p>Once you’re comfortable with Item Revisions, you can extend your integration to handle files, relationships, and advanced queries.</p><h3>Working with Datasets in Teamcenter</h3><p>In Teamcenter, a <strong>Dataset</strong> represents a file or document associated with a business object such as an Item or Item Revision.</p><h3>Simple Definition:</h3><p>A <strong>Dataset</strong> is nothing but a <strong>file document stored in Teamcenter</strong>.</p><p>These files can include:</p><ul><li>PDF documents</li><li>Word files</li><li>CAD files</li><li>Images and more</li></ul><p>Datasets are commonly used to attach supporting documents to product data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*2QRc1WyVow0vZxm0.png" /></figure><h3>Attaching a Dataset from Mendix</h3><p>If you need to upload and attach a file to an object in Teamcenter from Mendix, you can use the predefined microflow:</p><ul><li><strong>Dataset_CreateUpload</strong></li></ul><p>This microflow is available in the <strong>Teamcenter Connector Toolbox Samples module</strong> and simplifies the upload process.</p><h3>How Dataset Upload Works</h3><p>The process involves:</p><ol><li>Selecting a file in Mendix</li><li>Passing it to the microflow</li><li>Uploading it to Teamcenter</li><li>Associating it with the required object (e.g., Item Revision)</li></ol><h3>Prerequisites for Dataset Upload</h3><p>Before using the upload functionality, ensure you have the following inputs ready:</p><h3>1. File Document</h3><ul><li>The actual file you want to upload</li><li>This is typically selected or stored within Mendix</li></ul><h3>2. Dataset Type</h3><ul><li>Defines the type of document</li></ul><h3>Examples:</h3><ul><li>PDF</li><li>MS Word</li><li>Excel</li></ul><p>This should match the dataset type configured in Teamcenter.</p><h3>3. Dataset Name</h3><ul><li>The name of the file</li><li>Usually the same as the file name or a meaningful identifier</li></ul><h3>4. Named Reference</h3><ul><li>Represents the <strong>file format/type in Teamcenter</strong></li><li>Defines how the file is stored and accessed</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*SJvUb51I0hG87RnB.png" /></figure><h3>Creating Relationships in Teamcenter</h3><p>In Mendix, relationships between entities are maintained using <strong>associations</strong>. Similarly, in Teamcenter, relationships between different object types are established using <strong>relations</strong>.</p><p>This allows you to logically connect objects such as Items, Item Revisions, and Datasets.</p><h3>How Relationships Work in Teamcenter</h3><p>To maintain a relationship between two objects in Teamcenter:</p><ul><li>A <strong>relation type</strong> is defined</li><li>A <strong>primary object</strong> (parent) is linked to a <strong>secondary object</strong> (child)</li><li>The relationship is stored and managed within Teamcenter</li></ul><p>This ensures proper structure and traceability across product data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*-TTsPVYNmrV9t86F.png" /></figure><h3>Creating a Relation from Mendix</h3><p>To create relationships from Mendix, you can use the predefined microflow:</p><ul><li><strong>Create Relation</strong></li></ul><p>This microflow is typically available in the <strong>Teamcenter Connector Toolbox</strong> and simplifies the process of linking objects.</p><h3>Prerequisites for Creating a Relation</h3><p>Before executing the relation creation, ensure the following inputs are configured:</p><h3>1. Primary Object</h3><ul><li>The <strong>parent object</strong> in the relationship</li><li>This is the main object to which another object will be linked</li></ul><h3>2. Secondary Object</h3><ul><li>The <strong>child object</strong> in the relationship</li><li>This object will be associated with the primary object</li></ul><h3>3. Relation Name</h3><ul><li>The name of the relation</li><li>Must exactly match the relation defined in Teamcenter</li></ul><h3>Example:</h3><ul><li>IMAN_specification</li><li>IMAN_reference</li></ul><h3>Executing the Relation Creation</h3><p>Once all inputs are provided:</p><ol><li>Pass the Primary Object</li><li>Pass the Secondary Object</li><li>Provide the correct Relation Name</li><li>Execute the microflow</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*9iULXepGLChJiRyH.png" /></figure><h3>Getting LOV (List of Values) in Teamcenter</h3><p>In Teamcenter, certain properties use a <strong>List of Values (LOV)</strong> to ensure data consistency and standardization. These values are predefined in Teamcenter and can be retrieved from Mendix when needed.</p><p>This is especially useful for dropdown fields such as:</p><ul><li>Status</li><li>Categories</li><li>Types</li><li>Classifications</li></ul><h3>How LOV Retrieval Works in Mendix</h3><p>To fetch LOV values from Teamcenter, Mendix uses predefined input entities and a Java action. This allows you to dynamically load valid values for a given property.</p><h3>Prerequisites for Getting LOV Values</h3><p>Before retrieving LOV values, you need to configure the following input entities:</p><h3>1. boName (LovInputEntity)</h3><ul><li>Represents the <strong>Business Object name</strong> in Teamcenter</li><li>Defines which object’s LOV values you want to retrieve</li></ul><h3>2. Owning Object</h3><ul><li>Map the <strong>Model Object</strong> as the owning object</li><li>This ensures LOV values are retrieved in the correct context</li></ul><h3>3. LOVFilterDataInputEntity</h3><p>This entity controls filtering and result limits.</p><p>You need to configure:</p><ul><li><strong>filterString</strong> → Used to filter LOV results</li><li><strong>maxResults</strong> → Maximum number of values returned</li><li><strong>numberToReturn</strong> → Number of values to return in response</li></ul><h3>4. GetInitialLOVValuesInputEntity</h3><p>This is the main input entity for LOV retrieval.</p><p>You must:</p><ul><li>Set the <strong>propertyName</strong> for which LOV values are required</li><li>Associate it with:</li><li>LOVFilterDataInputEntity</li><li>LovInputEntity</li></ul><h3>Executing LOV Retrieval</h3><p>Once all inputs are configured:</p><ol><li>Use the Java action:</li></ol><ul><li><strong>Get Initial LOVs</strong></li></ul><ol><li>Pass the <strong>GetInitialLOVValuesInputEntity</strong> as input parameter</li><li>Execute the microflow</li></ol><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*HfRXgOPFFXJz_snk.png" /></figure><h3>Configuration Requirement</h3><p>Before running the action, ensure:</p><ul><li>The correct <strong>Teamcenter configuration name</strong> is set</li><li>Connection to Teamcenter is active</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*q4mpCY2FUhQpBvoT.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*89cjgtICCemgnzpn.png" /></figure><h3>Custom Query Search in Teamcenter</h3><p>In addition to standard searches like Item Revision search, Teamcenter also allows <strong>custom search operations</strong> using <strong>Saved Queries</strong>. This is useful when you need more flexibility and want to retrieve data based on specific business requirements.</p><h3>How Custom Query Search Works</h3><p>Custom queries in Teamcenter are executed using the <strong>Saved Query Search mechanism</strong>, which allows you to define and reuse search criteria.</p><p>From Mendix, you can invoke these saved queries to fetch relevant data dynamically based on your filters.</p><p>Press enter or click to view image in full size</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*9oCd1GWnBG7hUqUG.png" /></figure><h3>Key Considerations for Custom Search</h3><p>When working with custom query search, ensure the following are correctly configured:</p><h3>1. Query Name</h3><ul><li>You must provide the <strong>exact query name</strong> as defined in Teamcenter</li><li>The name is case-sensitive and must match the Teamcenter configuration</li></ul><h3>Example:</h3><ul><li>Item Revision</li><li>Find Objects</li><li>Custom Item Search</li></ul><h3>2. Additional Properties</h3><ul><li>You can pass extra properties to refine your search</li><li>These properties act as <strong>filters for query execution</strong></li></ul><h3>Examples:</h3><ul><li>Item ID</li><li>Object Name</li><li>Revision Type</li><li>Status</li></ul><p>The filter values must exactly match the expected format in Teamcenter.</p><h3>3. Search Filter Matching</h3><ul><li>The search criteria provided from Mendix must align with Teamcenter’s filter structure</li><li>Any mismatch may result in no data being returned</li></ul><p>This ensures consistency between both systems.</p><h3>4. Business Object (BO) Mapping</h3><ul><li>Proper <strong>Business Object Mapping</strong> must be configured</li><li>This ensures Teamcenter objects are correctly mapped to Mendix entities</li></ul><h3>Example:</h3><pre>ItemRevision = TcConnector.ItemRevision</pre><p>Accurate mapping is essential for:</p><ul><li>Data retrieval</li><li>Object casting</li><li>Microflow processing</li></ul><h3>Conclusion</h3><p>With datasets, relationships, LOVs, and custom queries, you can build a complete PLM integration solution. This enables scalable, efficient, and user-friendly applications on top of Teamcenter using Mendix.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f26b8ddca45" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Run a Mendix Application Using Eclipse and Debug Custom Java Actions]]></title>
            <link>https://medium.com/@rocksathish34/how-to-run-a-mendix-application-using-eclipse-and-debug-custom-java-actions-1135f529e3f5?source=rss-603718245214------2</link>
            <guid isPermaLink="false">https://medium.com/p/1135f529e3f5</guid>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[java]]></category>
            <dc:creator><![CDATA[Sathish Kumar]]></dc:creator>
            <pubDate>Mon, 22 Jun 2026 09:28:50 GMT</pubDate>
            <atom:updated>2026-06-22T09:28:50.749Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Introduction</strong></p><p>While Mendix Studio Pro provides excellent low-code development capabilities, there are scenarios where custom Java actions are required to implement complex business logic. During development, debugging Java code directly in Eclipse can significantly reduce troubleshooting time and help identify issues more effectively.</p><p>In this blog, we will learn:</p><ul><li>How to configure a Mendix application for Eclipse</li><li>How to import and run the application from Eclipse</li><li>How to create and debug a custom Java action</li><li>How to inspect variables and step through code execution</li></ul><p><strong>Step 1: Deploy the Mendix Application for Eclipse</strong></p><ol><li>Open your Mendix application in <strong>Mendix Studio Pro</strong>.</li><li>From the top menu, navigate to <strong>App → Deploy for Eclipse</strong>.</li><li>Wait for the deployment process to complete successfully. This will generate the necessary Eclipse project files and configurations required to run the application from Eclipse.</li></ol><p><strong>Step 2: Import the Project into Eclipse</strong></p><ol><li>Launch <strong>Eclipse IDE</strong>.</li><li>Navigate to <strong>File → Import</strong>.</li><li>In the Import wizard, select <strong>Existing Projects into Workspace</strong> under the <strong>General</strong> category and click <strong>Next</strong>.</li><li>Click <strong>Browse</strong> and select the root folder of your Mendix project that was deployed for Eclipse.</li><li>Eclipse will automatically detect the project and display it in the projects list.</li><li>Select the project and click <strong>Finish</strong>.</li></ol><p>The Mendix application will now be available in the Eclipse workspace and ready for execution and debugging.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*KxpSZYBCf-e-aVUtKjxpXA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*X-jbbrtuyeh9rfqdOjxFfA.png" /></figure><p><strong>Step 3: Configure the Application for Debugging</strong></p><ol><li>In Eclipse, select the imported Mendix project from the <strong>Package Explorer</strong>.</li><li>From the top menu, navigate to <strong>Debug → Debug Configurations</strong>.</li><li>In the <strong>Debug Configurations</strong> window, locate and select the launch configuration corresponding to your Mendix application.</li><li>Review the available configuration settings and ensure that the required options are enabled.</li><li>Check the checkbox(es) as highlighted in the image below to enable debugging support for the application.</li><li>Click <strong>Apply</strong> to save the configuration changes.</li></ol><p>Once the configuration is updated, the application is ready to be started in debug mode.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*66G1wLgDkZJnkoSTzM9q3Q.png" /></figure><p><strong>Step 4: Start the Mendix Application in Debug Mode</strong></p><ol><li>After selecting the required options in the <strong>Debug Configurations</strong> window, click <strong>Apply</strong> to save the configuration.</li><li>Click <strong>Close</strong> to exit the configuration window.</li><li>From the top menu, navigate to <strong>Debug</strong> and select the Mendix application launch configuration that you want to run.</li><li>Eclipse will start the Mendix Runtime in debug mode.</li><li>You can monitor the startup process in the <strong>Console</strong> view and verify that the application is being deployed successfully.</li></ol><p>Once the application has started successfully, Eclipse will display a popup similar to the one shown below, prompting you to switch to the <strong>Debug Perspective</strong>. Click <strong>Yes</strong> to switch to the Debug Perspective and access the debugging tools and views.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*ma12ainEGkEueFndG3hkNw.png" /></figure><h3>Step 5: Access the Running Mendix Application</h3><p>Once the application has started successfully, you can find the runtime port information in the Console view, as highlighted in the image above.</p><p>Locate the port number on which the Mendix Runtime is running. In this example, the application is running on <strong>port 8080</strong>.</p><p>Open a web browser and navigate to the application URL using the identified port number. The URL format is:</p><pre>http://localhost:&lt;port&gt;/index.html?profile=Responsive</pre><p>For example, if the application is running on port <strong>8080</strong>, the URL will be:</p><pre>http://localhost:8080/index.html?profile=Responsive</pre><p>Enter the URL in your browser to launch the Mendix application. Once the application is loaded, you can perform the required actions to trigger your custom Java actions and begin debugging them from Eclipse.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*qhBrXmcHyDs-8EY408Xo8Q.png" /></figure><p><strong>Step 6: Create and Synchronize the Custom Java Action</strong></p><p>With the application running successfully, the next step is to create a custom Java action in Mendix and debug its execution from Eclipse.</p><p>For this example, a custom Java action was created to convert an invalid or improperly formatted file name into a valid file name by removing or replacing unsupported characters.</p><ol><li>Open the Mendix application in <strong>Studio Pro</strong>.</li><li>Create a new <strong>Java Action</strong> and implement the required business logic.</li><li>Save the changes and deploy the application again by navigating to <strong>App → Deploy for Eclipse</strong>.</li><li>Wait for the deployment process to complete successfully.</li></ol><p>After the deployment is complete, switch to Eclipse and refresh the project to synchronize the latest Java source files generated by Mendix.</p><ol><li>Right-click the project in the <strong>Package Explorer</strong>.</li><li>Select <strong>Refresh</strong> or press <strong>F5</strong>.</li><li>Eclipse will update the project and load any newly generated or modified Java action files.</li></ol><p>This synchronization step is important because Mendix regenerates the Java action source files during deployment, and Eclipse must refresh the workspace to reflect the latest changes.</p><p>Once the refresh is completed, you should be able to locate the newly created Java action under the <strong>javasource</strong> folder and prepare it for debugging.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*a9THFmwfVEwbxFWUyy1Zxg.png" /></figure><p><strong>Step 7: Enable Debugging for the Java Action</strong></p><p>In the image above, you can see the implementation of the custom Java action that cleans the input file name. The logic processes the input string and removes or replaces unwanted characters to generate a valid file name.</p><p>To debug the Java action in Eclipse:</p><ol><li>Open the Java action source file in Eclipse.</li><li>Navigate to the line where you want the execution to pause.</li><li>Double-click in the left margin next to the line number.</li></ol><p>Once the breakpoint is added, a small blue circle will appear beside the line number, indicating that the debugger is enabled for that line.</p><p><strong>Step 8: Trigger the Java Action from the Application</strong></p><p>To execute the Java action:</p><p>1. Create a microflow that invokes the custom Java action.</p><p>2. Add a button on the page and configure it to trigger the microflow.</p><p>3. Run the application and click the button from the user interface.</p><p>When the microflow reaches the Java action, the execution will pause automatically at the breakpoint configured in Eclipse.</p><p>Switch back to Eclipse, and you will notice that the IDE enters debug mode. The following views will be available:</p><ul><li><strong>Debug</strong> — Displays the current execution stack and active thread.</li><li><strong>Variables</strong> — Shows the values of local variables, method parameters, and objects at the current execution point.</li><li><strong>Breakpoints</strong> — Lists all configured breakpoints and allows you to enable, disable, or remove them.</li></ul><p>At this stage, you can inspect variable values, validate business logic, and step through the code line by line to understand the execution flow of the Java action.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*fFYoHrCHe_J_6XOMF_o5EA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*wmRrWdWTuOF1HCqAaLkIng.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/631/1*eruIzn46Y-72GzJPUH6RDw.png" /></figure><p><strong>Step 9: Analyze the Execution Using the Debugger</strong></p><p>In the example shown above, the input file name provided to the Java action is:</p><p>Invoice@2026#Final!.pdf</p><p>The Java action processes the input and removes the unwanted special characters, resulting in the following cleaned file name:</p><p>Invoice2026Final.pdf</p><p>By using the Eclipse debugger, you can monitor the execution of the code line by line and verify whether the logic is producing the expected output. The debugger allows you to inspect variable values at each stage of execution, making it easier to identify issues and understand how the code is behaving at runtime.</p><p>Eclipse provides several debugging options to help you navigate through the code:</p><ul><li><strong>Step Into (F5)</strong> — Moves into the method being called, allowing you to inspect its internal implementation.</li><li><strong>Step Over (F6)</strong> — Executes the current line and moves to the next line without entering any method calls.</li><li><strong>Step Return (F7)</strong> — Completes the execution of the current method and returns to the calling method.</li><li><strong>Resume (F8)</strong> — Continues execution until the next breakpoint is encountered.</li></ul><p>These debugging capabilities are particularly useful when troubleshooting complex business logic, integrations, file-processing operations, or unexpected runtime behavior in custom Java actions.</p><p><strong>Conclusion</strong></p><p>In this blog, we explored how to run a Mendix application directly from Eclipse and how to enable debugging for custom Java actions. We covered the complete process, from deploying the application for Eclipse and importing the project into the workspace, to setting breakpoints and analyzing code execution using Eclipse’s debugging tools.</p><p>Debugging Java actions directly in Eclipse provides greater visibility into the execution flow and helps developers quickly identify and resolve issues. By leveraging breakpoints, variable inspection, and step-by-step execution, you can efficiently validate your custom Java logic and ensure that your Mendix applications behave as expected.</p><p>I hope this guide helps you get started with debugging custom Java actions in Mendix using Eclipse and improves your development and troubleshooting experience.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1135f529e3f5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Working with Item Revisions in Mendix]]></title>
            <link>https://medium.com/@rocksathish34/working-with-item-revisions-in-mendix-c99e85b86228?source=rss-603718245214------2</link>
            <guid isPermaLink="false">https://medium.com/p/c99e85b86228</guid>
            <category><![CDATA[plm-software]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[plm]]></category>
            <category><![CDATA[teamcenter]]></category>
            <dc:creator><![CDATA[Sathish Kumar]]></dc:creator>
            <pubDate>Tue, 05 May 2026 12:33:51 GMT</pubDate>
            <atom:updated>2026-05-05T12:46:28.130Z</atom:updated>
            <content:encoded><![CDATA[<p>Handling Item Revisions in Teamcenter via Mendix</p><h3>Introduction</h3><p>After setting up the integration, the next step is working with actual data — especially Item Revisions, which are central to Teamcenter.</p><h3>Key Attributes for Item Revision Search</h3><p>When performing an Item Revision search in Teamcenter through Mendix, certain attributes play a crucial role in identifying the correct object.</p><h3>Commonly Used Attributes:</h3><ul><li><strong>Name</strong> — Typically represents the <em>Part Name</em> or <em>Phantom Name</em></li><li><strong>ItemID</strong> — Usually the <em>Part Number</em> or <em>Phantom Number</em></li><li><strong>_Type</strong> — Defines the <em>object type</em> (optional, but useful for filtering)</li></ul><p>These attributes help narrow down and accurately retrieve the required Item Revision.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*DL_505vTEpKpj2_qeuxTVw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*wkrblhkHJub5gS7yOgrO_w.png" /></figure><h3>Handling Retrieved Objects in Mendix</h3><p>When data is fetched from Teamcenter:</p><ul><li>The returned object type is generally a <strong>Model Object</strong></li><li>This is a generic representation of Teamcenter data</li></ul><h3>Casting to Specific Object Type</h3><p>To work with specific object types in Mendix, you need to cast the Model Object.</p><p>This can be done using the Java action:</p><ul><li><strong>TeamcenterToolkit.JA_ModelObjectList_Cast</strong></li></ul><h3>Why Casting is Needed:</h3><ul><li>Converts generic Model Objects into specific business objects</li><li>Enables access to object-specific attributes</li><li>Improves data handling within Mendix</li></ul><p>This Java action is available in the <strong>Mendix Marketplace</strong>, making it easy to integrate into your project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*rSART4iLqVOGIJrlQufDlw.png" /></figure><h3>How Item Revision Search Works</h3><p>The <strong>Item Revision search</strong> is performed using the <strong>Saved Query Search</strong> mechanism provided by Teamcenter.</p><p>This allows structured and reusable queries to fetch data efficiently.</p><h3>Inputs Required for Saved Query Search</h3><p>To successfully execute a Saved Query Search, you need to configure the following inputs:</p><h3>1. Query Name</h3><ul><li>Default value is usually: <strong>“Item Revision”</strong></li></ul><p>⚠️ Note: This may vary depending on the project setup</p><h3>2. Input Data</h3><ul><li>Represents the <strong>search criteria</strong></li><li>Includes values like:</li><li>Item ID</li><li>Name</li><li>Type</li></ul><p>These inputs determine what data will be retrieved.</p><h3>3. Business Object Mapping</h3><ul><li>Defines how Teamcenter object types map to Mendix entities</li></ul><h4>Example:</h4><pre>ItemRevision = TcConnector.ItemRevision</pre><p>This ensures the retrieved data is correctly aligned with your Mendix domain model.</p><h3>4. Configuration Name</h3><ul><li>Refers to the <strong>Teamcenter configuration setup</strong> used for the connection</li></ul><p>This ensures the query runs against the correct environment and settings.</p><h3>Creating an Item Revision in Mendix</h3><p>Just like how you search for an Item Revision in Teamcenter, you can also <strong>create a new Item Revision object</strong> directly from Mendix using the Teamcenter Extension.</p><p>This process allows you to push data from your Mendix application into Teamcenter, enabling full lifecycle interaction.</p><h3>How Item Revision Creation Works</h3><p>The creation process is handled using the <strong>Create Item Revision</strong> functionality, which internally communicates with Teamcenter using SOA services.</p><p>In simple terms:</p><ul><li>You prepare the required input data in Mendix</li><li>Pass it to Teamcenter</li><li>Teamcenter creates the object and returns a response</li></ul><h3>Prerequisites for Creating an Item Revision</h3><p>Before creating an object, ensure the following setup is in place:</p><h3>1. CreateInput Entity</h3><p>To create an object in Teamcenter, you need a <strong>CreateInput entity</strong>.</p><p>You have two options:</p><ul><li>Use the <strong>CreateInput entity</strong> available in the <strong>TcConnector module</strong></li><li>OR create a custom entity and <strong>generalize it with CreateInput</strong></li></ul><h3>2. Define Object Type (_boName)</h3><ul><li><strong>_boName</strong> represents the <strong>Business Object Name</strong></li><li>It must exactly match the object type defined in Teamcenter</li></ul><p>This is critical — any mismatch will result in failure during object creation.</p><h3>3. Add Required Properties</h3><p>You can extend your CreateInput entity by:</p><ul><li>Adding <strong>additional attributes</strong> as needed</li><li>Mapping those attributes to Teamcenter fields</li></ul><p>Make sure:</p><ul><li>All mandatory properties are included</li></ul><p>Values are properly assigned before execution</p><h3>Configuring the Create Flow</h3><p>When setting up the microflow for object creation, configure the following:</p><h3>1. Create Input Object</h3><ul><li>The CreateInput object you prepare in the flow</li><li>This will be passed as an <strong>input parameter</strong> to the service</li></ul><h3>2. Business Object Mapping</h3><ul><li>Defines how Teamcenter object types map to Mendix entities</li></ul><h4>Example:</h4><pre>ItemRevision = TcConnector.ItemRevision</pre><h3>3. Configuration Name</h3><ul><li>Refers to the <strong>Teamcenter configuration</strong> being used</li><li>Ensures the request is sent to the correct environment</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*-cPgMyEY72B53Ap7JmzLgA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*agydZeq2JeiwBV5FcU35dQ.png" /></figure><h3>Updating an Item Revision in Mendix</h3><p>In many real-world scenarios, you may need to <strong>modify existing data</strong> in Teamcenter. Using Mendix, you can easily update properties of an <strong>Item Revision</strong> without directly interacting with Teamcenter’s UI.</p><p>This enables seamless data updates directly from your application.</p><h3>How Update Works</h3><p>When updating an Item Revision:</p><ul><li>Mendix sends the updated values to Teamcenter</li><li>Teamcenter processes the request via SOA services</li><li>The existing object is updated with new values</li></ul><h3>Using Predefined Update Flow</h3><p>The <strong>Teamcenter Connector Toolbox</strong> provides a <strong>predefined microflow</strong> for updating object properties.</p><h3>Prerequisites for Updating Item Revision</h3><p>Before executing the update, ensure the following inputs are properly configured:</p><h3>1. List of Property Names</h3><ul><li>Provide all the properties that need to be updated</li><li>Use a <strong>semicolon ( ; )</strong> as a separator</li></ul><h4>Example:</h4><pre>object_name;object_desc;owning_user</pre><h3>2. Model Object List</h3><ul><li>Provide a <strong>list of Model Objects</strong> that need to be updated</li><li>These are typically the objects retrieved earlier (e.g., via Saved Query Search)</li></ul><h3>Executing the Update</h3><p>Once the inputs are ready:</p><ol><li>Pass the <strong>Property Names list</strong></li><li>Provide the <strong>Model Object list</strong></li><li>Execute the predefined update flow</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*gN41lwmj8qdTCILATnHlcw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*TvwZ5vtGcR4JDupB8JC9JA.png" /></figure><h3>Conclusion</h3><p>You can now search, create, and update Item Revisions directly from Mendix. In the next blog, we’ll explore advanced features like datasets, relationships, and custom queries.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c99e85b86228" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting Started with Teamcenter–Mendix Integration]]></title>
            <link>https://medium.com/@rocksathish34/getting-started-with-teamcenter-mendix-integration-02f9d74e77b1?source=rss-603718245214------2</link>
            <guid isPermaLink="false">https://medium.com/p/02f9d74e77b1</guid>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[siemens]]></category>
            <category><![CDATA[teamcenter]]></category>
            <category><![CDATA[plm-software]]></category>
            <category><![CDATA[plm]]></category>
            <dc:creator><![CDATA[Sathish Kumar]]></dc:creator>
            <pubDate>Wed, 29 Apr 2026 14:39:12 GMT</pubDate>
            <atom:updated>2026-04-29T14:39:12.299Z</atom:updated>
            <content:encoded><![CDATA[<h3>Teamcenter Integration with Mendix: Fundamentals and Setup</h3><p>In today’s fast-paced product development landscape, seamless data flow between systems is essential. One powerful combination is integrating <strong>Teamcenter</strong> with <strong>Mendix</strong>, enabling organizations to connect product lifecycle management with low-code application development.</p><p>This blog walks you through the basics of Teamcenter, how integration works with Mendix, and the prerequisites you need to get started.</p><h3>What is Teamcenter?</h3><p><strong>Teamcenter</strong> is a Product Lifecycle Management (PLM) software developed by <strong>Siemens</strong>. In simple terms, it helps organizations manage all product-related data and processes across the entire lifecycle:</p><ul><li>Idea and concept development</li><li>Product design</li><li>Manufacturing</li><li>Service and maintenance</li></ul><p>By centralizing product data, Teamcenter ensures consistency, traceability, and collaboration across teams.</p><h3>What is Mendix?</h3><p><strong>Mendix</strong> is a low-code development platform that allows developers to quickly build and deploy applications. It is widely used for creating enterprise-grade apps with minimal coding effort.</p><p>When integrated with Teamcenter, Mendix can act as a powerful front-end or process automation layer for PLM workflows.</p><h3>How Teamcenter Integration Works in Mendix</h3><p>The integration between Mendix and Teamcenter is typically achieved using <strong>Service-Oriented Architecture (SOA) calls</strong> provided by Teamcenter.</p><h3>Key Concept:</h3><ul><li>Mendix communicates with Teamcenter by invoking <strong>SOA services</strong></li><li>These services allow you to:</li><li>Fetch product data</li><li>Update records</li><li>Trigger workflows</li><li>Manage lifecycle processes</li></ul><p>This approach ensures a standardized and scalable way to connect both systems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*UE1oG0p30aQO3PH-ftyFUA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*W4rJn3uq7SQopCMaG1kCqQ.png" /></figure><h3>Prerequisites for Integration</h3><h3>Access to Teamcenter Extension Module in Mendix</h3><p>Below steps are required to log into and configure the Teamcenter extension module within <strong>Mendix Studio Pro</strong>.</p><p><strong>1. Teamcenter URL</strong></p><p>You need the correct Teamcenter endpoint.</p><ul><li>The URL must be in the format:</li></ul><p><a href="https://%3cyour-teamcenter-server%3e/tc">https://&lt;your-teamcenter-server&gt;/tc</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*GcoTaDnIP2x9_rls7omGTQ.png" /></figure><p><strong>2. Account Credentials</strong></p><p>Ensure you have valid login credentials:</p><ul><li><strong>Username</strong></li><li><strong>Password</strong></li><li><strong>Group</strong> (if applicable)</li><li><strong>Role</strong> (if required)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*mZ9JxZffxdLXgO4IABDrdA.png" /></figure><p><strong>3. Service Account (Recommended)</strong></p><p>It is highly recommended to use a <strong>service account</strong> instead of a personal user account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*q682pL_iqzFMbmwUtI8_Ew.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*I6BUHE-1rHQ6ikl1dgpBeA.png" /></figure><h3>Session Management in Teamcenter Integration</h3><p>Once valid credentials are provided, a session is established in <strong>Teamcenter</strong> using the given account details. The created session acts as the foundation for all further interactions between <strong>Mendix</strong> and Teamcenter.</p><p>Mendix and Teamcenter interaction can happen in two ways such as Standard Login or Single Sign-On (SSO).</p><h3>Standard Login:</h3><p>The standard login ensures secure and consistent communication between the two platforms (<strong>Mendix</strong> and<strong> Teamcenter)</strong></p><h4>How Does It Works:</h4><ul><li>The system authenticates using the provided credentials</li><li>Upon successful login, a <strong>session is created in Teamcenter</strong></li><li>All subsequent SOA calls are executed within this active session</li></ul><h3>Alternate Option: Single Sign-On (SSO)</h3><p>Teamcenter also supports <strong>Single Sign-On (SSO)</strong> for session creation. SSO is especially useful in enterprise environments where identity management systems are already in place.</p><h4>Benefits of SSO:</h4><ul><li>Eliminates the need to manage separate credentials</li><li>Enhances user convenience</li><li>Improves security through centralized authentication</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*Pfp9f91NHDWloi5hH4k0tQ.png" /></figure><h3>What is an Item Revision?</h3><p>Understanding <strong>Item Revisions</strong> is fundamental when working with Teamcenter.</p><h3>Simple Explanation:</h3><p>An <strong>Item Revision</strong> represents a specific version of a product.</p><ul><li><strong>Item</strong> → The product itself</li><li><strong>Item Revision</strong> → A particular version of that product</li></ul><h3>Searching Item Revisions in Mendix</h3><p>One of the key capabilities of the Teamcenter Extension in Mendix is the ability to <strong>search and access Item Revision objects</strong> directly within your application.</p><p>This allows developers to retrieve specific product versions and work with their associated data seamlessly.</p><h3>How Search Item Revision Works</h3><p>Using the <strong>Search Item Revision</strong> functionality, you can:</p><ul><li>Query Teamcenter for specific Item Revision objects</li><li>Retrieve the required data into Mendix</li><li>Use the data for further processing or display</li></ul><h3>Example</h3><p>Suppose you want to work with a specific object like:</p><ul><li><strong>D4_ProblemInformation</strong></li></ul><p>By using the search functionality, you can locate and access this Item Revision object inside Mendix, making it available for your application logic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*CWxu957q073hHWKEOYngqQ.png" /></figure><h3>Mapping to Mendix Domain Model</h3><p>Once you have selected the required <strong>Item Revision object</strong>, the next important step is to integrate it into your Mendix data model.</p><h3>Key Step: Create a Generalization</h3><p>To create a <strong>generalization relationship,</strong></p><ul><li>User need to select the <strong>Item Revision and Model object </strong>in Mendix</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*4PZpf_A7rNcOvWH8XrVY3A.png" /></figure><h3>What is a Model Object in Teamcenter?</h3><p>A <strong>Model Object</strong> represents any object stored in Teamcenter.</p><p>In other words, it is:</p><ul><li>A <strong>real data record</strong></li><li>Created based on the <strong>Teamcenter data model</strong></li><li>Used to represent entities like Items, Item Revisions, datasets, and more</li></ul><h3>Working with Model Objects in Mendix</h3><p>Once you’ve identified the required <strong>Item Revision object</strong> and created a <strong>generalization</strong> with the Model Object, Mendix begins to simplify the integration process in the backend.</p><h3>Step 1: Import Mapping Generation</h3><p>After completing the generalization an <strong>import mapping</strong> is automatically generated for the selected object. This mapping helps transform Teamcenter data into Mendix objects.</p><p>Additionally, you can:</p><ul><li>Access <strong>extra attributes</strong></li><li>Configure <strong>reference associations</strong> if needed</li></ul><p>This gives you flexibility to bring in exactly the data your application requires.</p><h3>Step 2: Configure Attributes and Associations</h3><p>Before proceeding, ensure that:</p><ul><li>All required <strong>attributes</strong> are selected</li><li>Necessary <strong>associations</strong> are properly mapped</li></ul><p>This step is crucial for ensuring your data is complete and usable inside your Mendix application.</p><h3>Step 3: Generate the Flow</h3><p>Once everything is configured,</p><ul><li>Click on the <strong>Generate</strong> icon (available at the top of the interface). This action will automatically create a microflow for you.</li></ul><h3>Step 4: SavedQuerySearch Flow Creation</h3><p>After generation:</p><ul><li>A <strong>SavedQuerySearch</strong> flow will be created.It will appear inside the selected Mendix module.</li><li>This flow acts as a ready-to-use logic block for querying Teamcenter.</li></ul><h3>Using the SavedQuerySearch Flow</h3><p>You can now use the generated flow to:</p><ul><li>Query <strong>Item Revision objects</strong> from Teamcenter</li><li>Retrieve data dynamically based on your requirements</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*mBhXxGTJqjWBk8mGwo0a0Q.png" /></figure><h3>Conclusion</h3><p>You now have a clear understanding of the fundamentals of Teamcenter–Mendix integration, from setup and authentication to retrieving Item Revisions. In the next blog, we will explore how to effectively handle and manipulate this data.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=02f9d74e77b1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>