Mendix Teamcenter Integration – Part 2

In the Mendix Teamcenter Integration Part-1 of the Blog, we saw how Teamcenter Connector can be integrated with a Mendix Application and take PLM and Teamcenter customization to the next level by invoking Teamcenter services and actions from within a Mendix Application. This ensures a seamless way to manage Access Control to Teamcenter Environment and restricting any unwanted implication by the Application End User. In this part of the Blog, we shall explore how we can invoke a simple Teamcenter Service to Search Items from Teamcenter and display it in Mendix List View.


Functional Diagram

  • Mendix Studio Pro greater than v8.5.0
  • Appropriate Teamcenter License
  • A working Teamcenter server instance that can be accessed externally. The minimum Teamcenter version that is supported is 10.1.6.
  • Teamcenter Connector integrated and configured as mentioned in Part-1 of this Blog.
  • User credentials to login to Teamcenter Server Instance.
The integrated version of the Mendix Teamcenter helps field engineers perform their tasks

Mendix App Pages

  • Mendix Page to take input queries from the UI for the Search Criteria. We can search for an Item based on Item ID in Teamcenter or we can simply put * as the Search Criteria to fetch all items from Teamcenter.
  • Once Teamcenter Connector gets a Response from the Teamcenter Server, we need to display the Array of Items in a List View or a Data Grid View.
  • The Search Result Page will have columns to display different attributes of the Item like Item UUI, Item Title, Item Description.

Search Item Page

List for Mendix Search Criteria input queries from the UI

Search Item Result Page

Mendix Search Result Page will have columns to show various Item UUI attributes, item title, item description

Search Item Microflow

Mendix consists of microflows to express the logic of your application
  • The Search Button passes the Search Criteria String to eh Microflow as Input.
  • We create a TcConnector Search Item Query object and set the Input Search Criteria attribute.
  • We then call the TcConnector SOA Service  Perform Item Simple Search and pass the input workspace object as Search Item Query
  • The response of the SOA Call is of the Object Type TcConnector.SearchResponse.
  • We then get a List of Workspace Objects which are basically Items from the Search Response and its Item attributes which are displayed on the Result Page.

Leave a Reply

Your email address will not be published. Required fields are marked *

Fill out this field
Fill out this field
Please enter a valid email address.