Teamcenter Connector
Overview
This module allows you to connect to Teamcenter, the Siemens product lifecycle management system that brings together people and processes, and call SOAs to read and write data.
For an enhanced low-code experience, check out Teamcenter Extension. Built atop the Teamcenter Connector, the Teamcenter Extension enables developers to effortlessly harness the full capabilities of the Connector. It simplifies the visualization and access to the Teamcenter data model while automating the creation of Mendix domain models and microflows.
Releases
Fixes
- Updated com.fasterxml.jackson.core:jackson-databind com.fasterxml.jackson.core:jackson-core to 2.21.2 to resolve vulnerabilities
Fixes
- Added TC SSO compatibility with TC2406 and TC2312
- Updated Java Dependencies to remove vulnerabilities in the dependencies
- Improved Core-2012-02-DataManagement/whereUsed - clientId from the request is returned correctly in the response. Level is correctly mapped in the response.
Breaking changes
- User provisioning for TC SSO has changed as a result of the fix. TcSSOUserInformation now only contains User and Locale. To get the Teamcenter Username in user provisioning use 'User' instead of 'sub'.
Fixes
- Fixed an error due to Teamcenter responses containing arrays with a mix of empty strings and Model Object UIDs (Ticket 269666)
- Allow for Teamcenter URLs without top-level domains (e.g. not ending in .com)
- Made the FMS URL configuration field optional
- Throw a clear error when a Teamcenter URL that does not end with a slash is called
(original publication 11 December 2025, republished to include OSS license information)
New features
- GetWorkflowTemplates2 Java Action to support the newer 2013-05/Workflow/getWorkflowTemplates SOA endpoint
- PerformAction3 Java Action to support the newer 2014-06/Workflow/performAction3 SOA endpoint
- WhereUsed2 Java Action to support the newer 2012-02/DataManagement/whereUsed SOA endpoint
- 'StartUp' microflow to register request handlers for AWC widgets (TcBOM widget)
Improvements
- Reimplemented Teamcenter X SSO to remove the OIDC module dependency
- Reimplemented Teamcenter SSO to be consistent with Teamcenter X SSO
- Improved the overall SSO setup experience to remove the need for startup microflow and custom home pages
- Teamcenter SSO now supports user provisioning and anonymous user authentication from the login page
- Aligned and simplified the authentication process - Credentials, Tc SSO and TcX SSO are now consistent
- Updated styling of the Teamcenter login page
- Support for Mx11
- Support for the React client
Changes
- Updated fmsutils.jar to Tc2512 compatible version
Fixes
- Fixed an issue with a synchronization statement in the Java code where a single locked user could also lock out other users
Breaking changes
- Removed UserLogin microflow, use NAV_UserLogin navigation microflow instead
- Removed ShowLoginPage microflow, use NAV_UserLogin navigation microflow instead
- Removed LoginToMultipleTeamcenters microflow, use NAV_UserLoginMultipleActive navigation microflow instead
- Removed AdminLogin microflow, use User module role instead
- Removed AdminHomePage page, use NAV_AdminHomePage navigation microflow instead
- Removed SSO_RegisterRequestHandlers after startup microflow, no longer required
- Removed TeamcenterConfiguration event handlers, if you have custom logic for TeamcenterConfiguration objects, confirm it has the correct validations
- Deleted HomePage entity, no longer required
- Multiple microflows and pages deleted from the Private folder
- Multiple microflows and pages moved from Public to Private folder, check these are no longer directly referenced
Improvements
- Support for Mx11
- Support for the React client
Fixes
- Upgraded to Mendix 10.24.8
- Updated Java dependencies to resolve vulnerabilities
- Ensured compatibility with OIDC 4.3.0 and OIDC 4.4.0
Teamcenter versions supported: 2506
Improvements:
- Cleaned up unused jars.
- Upgraded FMS/TcSS jars to 2506 version.
- Added support for using authenticated FSC for TcX
- Updated string property length of TcConnector Domain Model entities to align with corresponding Teamcenter property length.
- Fixed error handling for RetrieveConfigNameFromSingleActiveConfiguration microflow. On error, exception is thrown. It is consumers' responsibility to deal with exceptions as per requirement.
- Introduced HandleActiveConfigErrors to show configuration errors.
- Handled partial errors for ReviseObjects java action. Partial errors can be read using ShowPartialErrors microflow.
- Stack trace handling for java actions:
- Added Logger.trace to print stack trace when exception occurs
- Fixed UploadFiles java action to return FALSE on exceptions.
Configured Managed dependencies for:
- jackson-annotations-2.19.0.jar
- jackson-core-2.19.0.jar
- jackson-databind-2.19.0.jar
- log4j-api-2.24.3.jar
- log4j-core-2.24.3.jar
- org.apache.httpcomponents-httpmime-4.5.13
- org.apache.httpcomponents-httpcore- 4.4.13
- org.apache.httpcomponents- httpclient-4.5.13
Userlib exclusions:
- TcLogging.jar
- fmsutil.jar
- fscjavaclientproxy.jar
- teamcenter_sso_applib.jar
- teamcenter_sso_common.jar
Known issues:
- When setting up Teamcenter X, and the following error occurs: "Name has an issue: This field is required! FriendlyName has an issue: This field is required!" Then there is a empty claim being imported at microflow CreateClaimwithFriendlyName, please add a empty check as workaround.
Release Notes (Teamcenter Connector version 2412.0225.0)
Following is the list of improvements/bug fixes in Teamcenter Connector version Tc2412.0225.0
Note: This version of TcConnector is supported on Mendix 10.4.0 onwards.
Supported with Teamcenter version: 2412
Improvements:
1. Cleaned up some unused jars.
2. Fixed Mendix-Teamcenter SSO connection issue. The issue is fixed by upgrading TCSS jars to TCSS2412.
Please refer to documentation for configuring Teamcenter with single sign on.
3. Updated log4j from 2.17.1 to 2.23.1 for managing conflicts with Excel Export Module.
Known issues:
- When setting up Teamcenter X, and the following error occurs: "Name has an issue: This field is required! FriendlyName has an issue: This field is required!" Then there is a empty claim being imported at microflow CreateClaimwithFriendlyName, please add a empty check as workaround.
Fixes
- Upgraded to Mendix 10.24.8
- Updated Java dependencies to remove unused jar files and to resolve vulnerabilities
- Ensured compatibility with OIDC 4.3.0 and OIDC 4.4.0
Release Notes (Teamcenter Connector version 2412.0.0)
Following is the list of improvements/bug fixes in Teamcenter Connector version Tc2412.0.0
Note: This version of TcConnector is supported on Mendix 10.4.0 onwards
Improvements:
1. Provided support for connection to TcX using SAM Auth
Note: Refer Document snippet for more detailed steps on how to setup Mendix application to communicate with TcX using SAM Authentication.
- Due to limitations with SAMAuth registration in 2412, TcConnector is not supported with Teamcenter X version 2412 and lower (updated - April 2026)
- Cleaned up some unused jars
Known issues:
- When setting up Teamcenter X, and the following error occurs: "Name has an issue: This field is required! FriendlyName has an issue: This field is required!" Then there is a empty claim being imported at microflow CreateClaimwithFriendlyName, please add a empty check as workaround.
Fixes
- Upgraded to Mendix 10.24.8
- Updated Java dependencies to remove unused jar files and to resolve vulnerabilities
- Dependencies now implemented using managed dependencies (vendorlib)
Breaking changes
- Before updating this module, make sure to remove all old .jar files of the previous version of the Teamcenter Connector from the userlib folder