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
Version: 2512.0.0
Framework Version: 10.24.8
Release Notes:
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
Version: 2506.0.0
Framework Version: 10.20.0
Release Notes: 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.
o Introduced HandleActiveConfigErrors to show configuration errors.
• Handled partial errors for ReviseObjects java action. Partial errors can be read using ShowPartialErrors microflow.
• Handled Managed dependencies:
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
• Stack trace handling for java actions:
o Added Logger.trace to print stack trace when exception occurs
• Fixed UploadFiles java action to return FALSE on exceptions.
Version: 2412.225.0
Framework Version: 10.4.0
Release Notes: 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.
Teamcenter versions supported: 2412, 2406, 2312
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.
Version: 2412.0.0
Framework Version: 10.4.0
Release Notes: 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.
2. Cleaned up some unused jars
Version: 2406.3.0
Framework Version: 10.0.0
Release Notes: Following is the list of improvements/bug fixes in Teamcenter Connector version Tc2406.0003.0
Bug fixes:
1. Upgraded TcSS jars and modified SSORedirectRequestHandler.processCallback to allow create SSO App session using JSON type. XML Type is no more supported.
2. Added Access Rules for TcConnector.Image and TcConnector.ImanFile entity.
3. Mendix Teamcenter Connector now can upload Dataset named references defined with *
4. Changed length of POM_application_object.object_string and BOMLine.object_string to 4000 to match with Teamcenter data model
5. Cleaned up userlib folder by removing unrequired jars.
6. Setting up timeout for SendService microflow to 300s.
Version: 2406.0.0
Framework Version: 10.0.0
Release Notes: Following are the list of improvements in Teamcenter Connector version Tc2406.
1. Added following associations on BomWindow
• top_line (BOMWindow 1-1 BOMLine)
• revision_rule (BOMWindow 1-1 BOMLine)
2. Added following associations on BomLine:
• bl_revision (BOMLine 1-1 ItemRevision)
3. TcConnector.FileDocument now captures Dataset UID and ImanFile UID.
• Introduced new java action GetImanFiles which retrieves ImanFile information for a given dataset.
• If ImanFile's lastModifiedDate is later than the creation date of corresponding FileDocument/Image then consumer can download the file again.
4. Introduced new java action DownloadImages which downloads the ImanFile as an TcConnector.Image. Application/Consumer decides whether to download a dataset as FileDocument or an Image based on input dataset's _Type property value.
5. Multiplicity of association release_status_list is corrected (many-to-many)
6. PropertyResolver's static variable XSD_FORMAT of type SimpleDateFormat and is not thread safe. Making it local variable so as not to cause issue when gets executed through various threads.
7. Added locale support for SSO login.
8. Added action ExecuteSavedQueryWithObjectRefresh. Every time the saved query is executed using this call, a refreshed object is returned.
Version: 3.6.1
Framework Version: 10.0.0
Release Notes: This is a compatibility release only. Tc Connector was made compatible with Studio Pro version 10 onwards. No bug fixes are provided as part of this release.
Version: 3.6.0
Framework Version: 9.18.2
Release Notes: 1) Provided L10N support for SavedQuery execution
Search criteria entities are used as input for invoking Teamcenter service Query-2008-06-SavedQuery/executeSavedQueries through Mendix service 'Toolbox/Teamcenter/Saved Query Search'
Attributes on these input entities should be defined based on Teamcenter L10NKeys for its corresponding search criteria attribute.
e.g. If the Teamcenter Saved Query has search criteria entry for 'Item ID' and its corresponding L10NKey is ItemID, then in Mendix, define the Search Criteria Entity with 'ItemID' as attribute name.
Note: Criteria attribute L10NKeys does not change for locale and thus works for non-english locales too.
e.g. Refer to Teamcenter Query Locale keys from
\lang\textserver\en_US\qry_user_entry_names_locale.xml
2) Performance Improvements:
a) Avoided instantiation of undesired types. Only the types specified in Business Object mappings are instantiated. Consuming application needs to make sure to have entries in the Business Object mappings if specific type of Model object needs to be consumed.
b) BOM Expand APIs takes extra configuration parameter to decide whether to populate service data with Model objects. If consuming application does not refer to Model Objects directly from Service Data, then this new configuration parameter can be set to false during consumption.
Version: 3.5.0
Framework Version: 9.1.1
Release Notes: Bug fixes and performance improvements