Teamcenter Connector Toolbox Samples
This module is a set of microflows wrapping up the standard “Teamcenter Connector” to accelerate implementation and extend the available activities. Be aware that you still need to understand the key concepts of the connector like Object Mapping, Operation Mapping.
Since it’s hard to have generic tools, some microflows can be used as is, and some other are more samples that are meant to be duplicated and adapted to your own datamodels since everything is microflows. However, it’s still faster to start with a model because the standard connector requires a lot of tricky and boring entity manipulations before and after each calls.
Key features : activities in a single call for the basics (create and find items, open BOM, etc...), download datasets as document or image and without duplication, Object Casting, Call a Tc Service with JSON at input or output (no OperationMapping), transform JSON with variable keys to an array
New Tc Services implemented : GetChildren, LoadObject, HomeFolder, Open BOP, Classification, Spatial Search, PLMXML export
Important note: this module expect you to add a few attributes in the domain model of the standard “Teamcenter Connector”, this will need to be re-done after every update of the connector.
This module is a set of microflows wrapping up the standard “Teamcenter Connector” to simplify and extend the available activities. Some tools can be used as is, some other can be duplicated and adapted to your datamodels since everything is microflows.
Typical usage scenario
Accelerate and extend the use of the standard Teamcenter Connector.
Features and limitations
Folder and Features :
- Single Call activities, with simple parameters
allowing you to start with a model because the standard connector requires a lot of tricky and boring entity manipulations before and after each calls
- Change Mgmt
- Navigation and Relations
- Object Mapping
This concept comes from the TcConnector. The Toolbox just offers a central constants for object mapping.
- Object Casting
While Object Mapping concept ensures that the objects are loaded in a given type (like RequirementRevision, DesignRevision), the responses lists can be a generalization like ItemRevision mixing objects of the many subtypes. Because of this, implementing the TcConnector connector leads you to intensively use object casting. This toolbox offers some ready to use microflows for common types, and encourage you to extend it. For a given type you will find a pair of microflows, one to cast a single object, the second one to cast a list of object.
- File Management
download dataset files as document or as image. Avoid File duplication by checking UIDs (see readme to modify the standard TcConnector domain model),
- Teamcenter services calls
- Call a Tc Service with JSON at input or output, because sometimes OperationMapping (TcConnector concept) is making things more complex tha it should
- transform JSON with variable keys to an array. Sometimes Teamcenter answers with a JSON where the key is a variable, which is not supported by Mendix. This utility transform the Json objects to an array.
New Tc Services implemented :
- Folder navigation
- Open BOP,
- Spatial Search,
- PLMXML export
- TC project (Get, select)
- MX v9.2.0
- Teamcenter Connector v3.5.0
Read and apply instructions in the readme. Some modification need to be done in the domain model of the standard module “Teamcenter Connector”, and will need to be done again after every update of the standard module.