Teamcenter Extension

Content Type: Module
Categories: Extensions

Overview

Teamcenter Extension provides you with an effortless means to harness the full capabilities of Teamcenter Connector for Mendix. The Teamcenter Extension is layered atop the Teamcenter Connector, to provide a low-code experience by making it easier to visualize and access Teamcenter data model and automate creation of Mendix domain models and microflows.

Documentation

Please refer to Mendix Documentation

 

Installation:

  • Open Mendix Studio Pro and create an App.
  • Connect to Mendix Marketplace and download Teamcenter Extension.
  • You will see two popups asking if you want to install the Teamcenter Toolkit and if you trust the add-on module that contains the Teamcenter Extension.
  • Click Yes to both

Releases

Version: 3.2.0
Framework Version: 10.12.6
Release Notes: ## New features ### Dark Mode The Teamcenter Extension now supports dark mode. It will display the same mode as Studio Pro. Change your Studio Pro settings (Edit -> Preferences -> Work Environment) to Dark to see the new mode. ### Table sorting Tables in the Teamcenter extension now support sorting. For examples, when configuring an import mapping, the columns in the sidebar displaying the details of Teamcenter properties are now sortable. Click on the column headers to sort the columns ascending and descending alphabetically, respectively. ## Improvements * Changed label ‘Name’ to ‘Internal Name’ in property sidebar for added clarity. ## Fixes * Fixed an issue that when cancelling the deletion of an integration, the integration was no longer visible, until reloading the Teamcenter extension. * Fixed an issue with the Attach Dataset integration. The default property TC_manifestation was misspelled. ## Known issues * The Teamcenter extension is not compatible with Mendix Studio Pro 10.13.0, 10.13.1, 10.14.0, and 10.15.0. * Entities from add-on modules or entities where at least one of their generalizations is from an add-on module cannot be used in the object mapping. * Teamcenter properties can have spaces in their name; Mendix attributes cannot. These cannot be used. * When multiple developers are working with the extension simultaniously and commit their changes, duplication of integrations may occur.
Version: 3.1.0
Framework Version: 10.12.6
Release Notes: # New features ## Attach Datasets to ItemRevision We added the feature to generate a microflow to create and attach a dataset or specializations thereof with file document to an ItemRevision in Teamcenter and the corresponding domain model. The resulting microflow implements the Upload file, Create Relation and Get Properties actions from the TcConnector. In addition, the extension generates (depending on configuration) microflows to: * Get available Dataset types * Get file types for a Dataset type ## Improvements * Improved the validation of integrations where validations will pass when deleting and then restoring microflows or entities. * Added a dropdown with autocomplete functionality. * We renamed the empty parameter entity for clarity. * Dataset types are always fetched anew from Teamcenter, also when editing/duplicating an integration. * Introduced support for table properties from Teamcenter. ## Fixes * Fixed an issue with the positioning of the entities in the import mapping preview in the history tab. * Fixed an issue when using the mouse-back button. * Fixed an issue where sometimes when editing/duplicating an integration to get Datasets for ItemRevisions the dataset type was preselected when it should not have been. ## Known issues * The Teamcenter extension is not compatible with Mendix Studio Pro 10.13.0, 10.13.1, 10.14.0, and 10.15.0. * Entities from add-on modules or entities where at least one of their generalizations is from an add-on module cannot be used in the object mapping. * Teamcenter properties can have spaces in their name; Mendix attributes cannot. These cannot be used.
Version: 3.0.0
Framework Version: 10.12.6
Release Notes: **New features** ***Search Datasets*** We added the feature to generate a microflow to search for Datasets or specializations thereof in Teamcenter and the corresponding domain model. The resulting microflow implements the Saved Query Search action (Dataset…) from the TcConnector. In addition, the extension generates microflows to: * Get ImanFiles for a Dataset * Retrieve files or images for a Dataset * Get available Dataset types * Get file types for a Dataset type ***Get Datasets for ItemRevision*** We added the feature to generate a microflow to get Datasets for a an ItemRevision and the corresponding domain model. The resulting microflow implements the Expand GRM Relations for Primary action from the TcConnector. In addition, the extension generates a microflow to: * Retrieve files or images for a Dataset. ***Navigation to artifacts*** We added the feature where the developer can navigate to the (generated) entities and to the generated microflows from the history tab. **Breaking changes** Teamcenter Extension 3.0.0 has been upgraded to work with: * Mendix Studio Pro 10.12.6 (minimum version) * TcConnector 2406.3.0 (minimum version). For steps on how to upgrade from 2.0.0 to 3.0.0, please refer documentation. In addition, there is a change to the way Teamcenter extension integrations are stored on disk (the configurations of the integrations, not the generated microflows). We have added upgrade logic, so existing integrations should still work. **Improvements** * Improved the way the extension checks if editing or duplication of integrations is allowed. * Added validations to the history tab to check for conflicts in association names and multiplicities. * Developers can now leave the Teamcenter configuration name (ConfigName input parameter) empty. In that case, for the integrations the active Teamcenter configuration is retrieved from the database. If multiple active Teamcenter configurations exist, an exception will be thrown. * Reorganized the menu of the extension and created more intuitive icons for the supported integrations. * Improved the checks to check the compatibility of the extension with the Mendix Studio Pro version and the TcConnector version. Also, the extension is now working with minimum versions of its dependencies instead of exact versions. * Improved the consistency of how exceptions are logged and communicated to the user. * Added support for MacOS. Note, as MacOS support for Mendix Studio Pro is still in beta, the same is true for the Teamcenter extension. * Added path to root Teamcenter object type in the object mapping dialog. * Improved the text in the get structures configuration sidebar. **Fixes** * Mitigated maximum path length issues for Mendix projects with long path lengths. * Fixed an issue with the scrollbar for the list of integrations on the History tab. * Fixed an issue where relations and references were not preselected when editing or duplicating an integration. * Increased the consistency of the way error handling was modeled in the Toolkit microflows. * Fixed an issue that if an entity was reused in the import mapping, it turns up multiple times in the generated BO mapping. * Fixed a redundant warning when changing the object mapping without associated child mappings. * Fixed an issue where the user could still interact with the extension tab after editing or duplicating an integration. * Fixed an issue where it was not possible to change the object mapping in some of the Teamcenter integrations. **Known issues** * The Teamcenter extension is not compatible with Mendix Studio Pro 10.13.0, 10.13.1, 10.14.0, and 10.15.0. * In the object mapping dialog, entities from add-on modules or entities where at least one of their generalizations is from an add-on module will not be visible and cannot be used in the object mapping. * Teamcenter properties can have spaces in their name; Mendix attributes cannot. This results in errors in the generated/updated domain model.
Version: 2.0.0
Framework Version: 10.12.1
Release Notes: New features Teamcenter Extension 2.0.0 allows managing of integrations. We have added a new tab to the landing page of the extension where the integrations are listed. When clicking on an integration, details of the integration are shown including validation feedback showing the health of the integration. The developer can click on edit to change an integration and on duplicate to create a new integration using an existing integration as a starting point (the original integration will remain unchanged). Also, integrations can be deleted. Note that, in that case, the actual microflows and entities are not removed from the Mendix model. Breaking changes Teamcenter Extension 2.0.0 has been upgraded to work with • Mendix Studio Pro 10.12.1 (minimum version) • TcConnector 2406.0.0 (minimum version) For steps on how to upgrade from 1.0.0 to 2.0.0, please refer to Mendix documentation on Teamcenter Extension Improvements • Display integration title on the import mapping page for reference. • Added a link to Mendix docs in the object mapping dialog and Teamcenter Settings -> Edit dialog. • Enriched the documentation for the generated entities in the domain model. • Removed FMS URL from the Teamcenter settings as this was not actively used by the extension. • Removed spelling checker from the input fields. • Improved the sorting behavior of the object mapping dialog. • Improved the performance of the object mapping dialog • Removed dependence on Community Commons module Fixes • Maximum length of string attributes created by the extension did not match the maximum lengths as configured in Teamcenter. • Extension did not create a custom ReviseItemRevision input object when creating the entities and microflow to revise an ItemRevision. • Teamcenter properties/relations/references with spaces in the name could be selected when configuring an integration. The current version of the TcConnector does not support properties/relations/references with spaces in the name. • Microflow generated by the extension had a conflicting object name. • Fixed the minimum height of an entity in the import mapping page. • Fixed merge conflicts were created for the Teamcenter cookie. Known issues • In the object mapping dialog, entities from add-on modules or entities where at least one of their generalizations is from an add-on module will not be visible and cannot be used in the object mapping. • Teamcenter properties can have spaces in their name; Mendix attributes cannot. This results in errors in the generated/updated domain model.
Version: 1.0.0
Framework Version: 10.6.5
Release Notes: Initial Release