diff --git a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension.md b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension.md deleted file mode 100644 index 347063d925e..00000000000 --- a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension.md +++ /dev/null @@ -1,342 +0,0 @@ ---- -title: "Teamcenter Extension" -url: /appstore/modules/siemens-plm/teamcenter-extension/ -description: "Describes Teamcenter Extension from the Mendix Marketplace. Teamcenter Extension facilitates a low-code approach to integrating with Siemens Teamcenter." -aliases: - - /appstore/modules/teamcenter-extension/ ---- - -## Introduction {#introduction} - -[Teamcenter Extension](https://marketplace.mendix.com/link/component/225544) is a Mendix Extension built using the Mendix Extensibility Framework to provide you with an effortless means to harness the capabilities of [Teamcenter Connector](https://marketplace.mendix.com/link/component/111627) for Mendix. Teamcenter Extension is built on Teamcenter Connector. It provides a low-code experience by making it easier to visualize and access Siemens Teamcenter data models and automating creation of Mendix domain models and microflows. - -{{% alert color="info" %}}Teamcenter Extension V 3.0.0 and above is also supported on macOS.{{% /alert %}} - -### Typical Use Cases {#usecases} - -Teamcenter Extension offers a list of use cases for which domain models and microflows can be created. After you select a use case, it uses an import mapping approach similar to Mendix [import mapping](/refguide/import-mappings/). Here, Teamcenter Extension allows you to select data from the business model of your Teamcenter instance. Teamcenter Extension uses the selected use case, the import mapping, and, in some use cases, additional configurations to generate and update the domain model for your integration and generate one or more ready-to-use microflows that you can drag and drop into your application logic. - -Teamcenter Extension offers the following integration options: - -* Search item revisions -* Create item and item revision -* Update item and item revision -* Revise item revision -* Search datasets -* Get datasets for item revision -* Attach dataset to item revision -* Search workspace objects -* Relate workspace objects -* Get structure - -### License {#license} - -Teamcenter Extension is free to download and use. You may, however, require a Teamcenter (Author or Consumer) license to connect to Teamcenter. - -### Dependencies {#dependencies} - -You must have these Marketplace modules installed: - -* [Teamcenter Connector](https://marketplace.mendix.com/link/component/111627): needed for all versions of Teamcenter Extension -* [Community Commons](https://marketplace.mendix.com/link/component/170): only needed for Teamcenter Extension V 1.0.0 - -Compatibility among Teamcenter Extension, Teamcenter Connector, and Studio Pro is as follows: - -| Teamcenter Extension Version | Teamcenter Connector Version | Studio Pro Version | -| ------------- | ------------- | ------------- | -| 1.0.0 | 3.6.1, V 3.6.0, V 3.5.0 | 10.6.5 thru 10.7 | -| 2.0.0 | 2406.0.0 | 10.12, patch versions 1 and above and 10.16.0 and above | -| 3.0.0 and above | 2406.3.0 | 10.12 patch version 6 and above and 10.16.0 and above | - -{{% alert color="info" %}} -Teamcenter Extension is not compatible with Studio Pro versions between 10.8 and 10.11, as well as 10.13.x, 10.14.x, and 10.15.x. If you use one of these Studio Pro versions, a possible workaround is to use Teamcenter Extension in one of the compatible versions of Studio Pro first, create the necessary artifacts, and then import them into your version. However, Mendix always recommends using the latest MTS or LTS Studio Pro version. -{{% /alert %}} - -{{% alert color="info" %}} -If you use Teamcenter Extension V 1.0.0 with Teamcenter Connector V 3.6.1 or below and want to upgrade to Teamcenter Extension V 3.0.0 and Teamcenter Connector V 2406.3.0, see the [Upgrading Teamcenter Extension V 1.0.0 to V 3.0.0](#upgrade) section. -{{% /alert %}} - -### Demo App {#demoapp} - -To see Teamcenter Extension in action, download and play with the [Teamcenter Extension Sample App](https://marketplace.mendix.com/link/component/225910). - -## Installation {#installation} - -Follow the instructions in [How to Use Marketplace Content](/appstore/use-content/) to import Teamcenter Extension into your app. - -## Actions - -### Search Item Revisions {#getitemrevision} - -The `Search Item Revisions` action allows you to generate the domain model and microflow to search for and retrieve `ItemRevisions` or its specialization. The resulting microflow implements the saved query `Item Revision...` from Teamcenter. - -### Create Item With Item Revision {#createitem-and-itemrevision} - -The `Create Item and Item Revision` action allows you to configure and generate the domain model and microflow to create an Item with `ItemRevision` or its specializations in Teamcenter. The resulting microflow implements the `Create Object and Update Properties` actions from the Teamcenter Connector. With the `Create Object` action, the `Item` and `ItemRevision` get created in Teamcenter, setting the Teamcenter properties that need to be set upon creation. With the `Update Properties` action, the remaining properties are updated in Teamcenter. - -### Update Item With Item Revision {#updateitem-and-itemrevision} - -The `Update Item and Item Revision` action allows you to generate the domain model and microflow to update an `Item` with `ItemRevision` or their specializations in Teamcenter. The resulting microflows implements the `Update Properties` action from the Teamcenter Connector. - -### Revise Item Revision {#reviseitem-and-itemrevision} - -The `Revise Item and Item Revision` allows you to generate the domain model and microflow to revise an `ItemRevision` or its specializations in Teamcenter. The resulting microflow implements the `Revise Object and Update Properties` actions from the Teamcenter Connector. With the `Revise Object` action, a new `ItemRevision` is created, setting the Teamcenter properties that need to be set upon revising. With the `Update Properties` action, the remaining properties are updated in Teamcenter. - -### Search Datasets {#getdatasets} - -The `Search Datasets` allows you to generate the domain model and microflow to search for and retrieve `Datasets` or its specialization. The resulting microflow implements the saved query `Datasets` from Teamcenter. - -### Get Datasets for Item Revision {#getdatasetsfromitemrevision} - -The `Get Datasets for Item Revision` action allows you to generate the domain model and microflow to retrieve datasets for an Item Revision and subsequently download files inside the dataset. - -### Attach Datasets to Item Revision {#attachdatasetstoitemrevision} - -The 'Attach Datasets to Item Revision' action allows you to generate a domain model and microflow which creates and attaches a Teamcenter dataset (or its specializations) with a file document to an Item Revision in Teamcenter. The resulting microflow implements the `Upload file`, `Create relation`, and `Get properties` actions from the `TcConnector` module. - -### Search Workspace Objects {#getworkspaceobjects} - -The `Search Workspace Objects` action allows you to configure and generate the domain model and microflow to search for and retrieve Workspace Objects or their specialization from Teamcenter. This action implements the saved query `General..` from Teamcenter. - -### Relate Workspace Objects {#relateworkspaceobjects} - -The 'Relate Workspace Objects' action allows you to generate the domain model and microflow to relate two workspace objects or their specialization from Teamcenter. The resulting microflow implements the `Create relation` action from the `TcConnector` module. - -### Get Structure {#getstructures} - -The `Get Structure` action allows you to generate the domain model and microflows to configure a BOM window and retrieve structure data from Teamcenter. This feature supports the retrieval of structures with the following: - -* `RevisionRule` (or default `RevisionRule`) -* `VariantRule` -* `BOMWindow` property flags - -Depending on the configuration, microflows are generated to do the following: - -* Create `BOMWindow` (implementing the `Create BOM Windows2` action from the Teamcenter Connector) -* Retrieve `RevisionRules` (implementing the `Get Revision Rules` action from the Teamcenter Connector) -* Retrieve `VariantRules` (implementing the `Get Variant Rule` action from the Teamcenter Connector) -* Expand a single `BOMLine` (implementing the `Expand One Level 2` action from the Teamcenter Connector) -* Expand all `BOMLines` (implementing the `Expand All Levels` action from the Teamcenter Connector) -* Close the `BOMWindow` (implementing the `Close BOM Window`s action from the Teamcenter Connector) -* Get the root `BOMLine` for a `BOMWindow`. - -To work with structures, such as BOMs, you need to first create a BOM window in Teamcenter. One can retrieve the root BOM Line from the BOM window and from there start expanding the structure either line by line or with all BOM Lines at the same time. The BOM Lines define the structure (based on the configuration you passed when generating the BOM window). Each BOM Line is associated with a single `ItemRevision`. - -This feature is designed specifically for generating microflows and domain models to retrieve and display simple BOM structures (unconfigured or configured). For other scenarios, consider alternative solutions. See the table below: - -| Scenario                                                 | Suggested Solution             | -| -------------------------------------------------------- | ------------------------------ | -| Work with large or complex BOM structures                | Use Active Workspace           | -| Have performance concerns                                | Use Active Workspace           | -| Transfer an entire BOM from Teamcenter to another system | Use Active Integration Gateway | -| Compare BOMs from different systems                      | Use Active Integration Gateway | -| Author BOMs                                              | Use Active Workspace           | -| Create BOM configurations                                | Use Active Workspace           | - -## Landing Page {#homepage} - -To open Teamcenter Extension in Studio Pro, go to **Extensions** > **Teamcenter Extension** > **Teamcenter Extension**. If you use Studio Pro versions 10.7 or lower, Teamcenter Extension is available under **View** > **Teamcenter Extension**. - -{{% alert color="info" %}} -For details on the version dependencies between Studio Pro and Teamcenter Extension, see the [Dependencies](#dependencies) section. -{{% /alert %}} - -The landing page has with three tabs: **Menu**, **History**, and **Settings**. - -### Menu Tab - -The **Menu** tab displays use cases or actions you can create artifacts for using Teamcenter Extension. - -{{< figure src="/attachments/appstore/platform-supported-content/modules/teamcenter-extension/menu-tab.png" >}} - -### History Tab - -The **History** tab displays the history of all actions (also referred as integrations) carried out in Teamcenter Extension. - -{{< figure src="/attachments/appstore/platform-supported-content/modules/teamcenter-extension/history-tab.png" >}} - -On the **History** tab, you can view details of each action, such as entities and microflows created, Teamcenter URL used to connect with, the preview of the import mapping, and much more. - - You can also edit, duplicate or delete an action using the buttons in the upper-right corner: - -* **Delete** – This deletes the selected action from the list. However, it does not delete the corresponding entities and microflows, since they may impact pages or other integrations. -* **Duplicate** – This allows you to create a new action based on an existing one. When you click **Duplicate**, it clones the selected action and takes you to the import mapping page, where you can modify your mapping and subsequently create new domain model and microflows. This operation does not modify any of existing actions. -* **Edit** – This allows you to modify an existing action and updating existing domain model and microflows. When you click **Edit**, it takes you to the import mapping page, where you can add or edit entities, attributes, and associations, subsequently updating the domain model and microflows. - -It is not recommended to make specific adjustments to artifacts generated by Teamcenter Extension outside of Teamcenter Extension. Doing so may result in breaking the integration. Instead, you should make adjustments inside Teamcenter Extension using the **Delete**, **Duplicate** or **Edit** operations, wherever possible. Examples of adjustments that are not advisable outside Teamcenter Extension are as follows: - -* Modifying the **CreateInput** and **CompoundCreateInput** entities generated from The **Create Item** action -* Modifying any entity generated from the **Revise Item Revision** action -* Deleting attributes or associations generated by Teamcenter Extension -* Deleting or editing microflows generated by Teamcenter Extension - -However, you can make the following adjustments outside Teamcenter Extension: - -* Adding attributes or associations -* Moving microflows -* Renaming microflows - -If you select an item in the **Action** list, Teamcenter Extension performs a validation check to see if the Teamcenter objects, entities, and microflows still exist and are valid. The results are reported in the **Validation** section. - -### Settings Tab - -The **Settings** tab allows you to change the **Teamcenter configuration**. - -{{< figure src="/attachments/appstore/platform-supported-content/modules/teamcenter-extension/teamcenter-configuration.png" >}} - -The tab indicates whether you currently have an active Teamcenter session, or whether the session is inactive. - -There are two buttons: - -* **Edit** – allows you to change the settings -* **Sign in** – signs you in to Teamcenter if **Authentication** is set to *Credentials* (see [Signin Configuration](#signin-configuration), below) - -#### Editing Settings - -Click **Edit** to change the settings. - -{{< figure src="/attachments/appstore/platform-supported-content/modules/teamcenter-extension/edit-configuration.png" >}} - -You can set up the following information. It will be saved when you click **Save**: - -##### Teamcenter Instance - -While building your app and using Teamcenter Extension you need to provide the details of the Teamcenter instance to connect to. To do this provide the following information under **Teamcenter instance**: - -* **TC URL** –the URL to which calls will be made to sign in and retrieve data. Teamcenter Extension supports both HTTP and HTTPS connections. -* **Certificate Path** – the path to certificates that have .crt and .pfx file extensions. The path should be relative to the app directory. - -##### Signin Configuration {#signin-configuration} - -Set **Authentication** to one of the following methods. - -* **Credentials** – Select this if your Teamcenter instance supports logging in using provided credentials. You will be prompted for your Teamcenter credentials when you click the **Sign in** button in the **Settings** tab. This method prevents sharing of credentials among developers through versioning. - -* **Teamcenter SSO** – Allows you to use SSO if your Teamcenter instance is configured to use it. You can get these settings from your Teamcenter administrator. - - {{< figure src="/attachments/appstore/platform-supported-content/modules/teamcenter-extension/teamcenter-sso.png" >}} - - You need to fill in the following: - - * **SSO Login Server URL** – the endpoint where your authentication request is sent. It acts as the main entry point for users trying to log in using SSO. This URL is typically associated with the Identity Provider (IdP) and is responsible for handling login requests and directing users through the authentication process - * **SSO Identity Server URL** – the URL of the Identity Server where the Teamcenter Extension application should be registered - * **Teamcenter Application ID** – the existing Teamcenter Application ID obtained from the Teamcenter Security Services Identity Service configuration. - * **Studio Pro Application ID** – the registered ID of the Teamcenter Extension at the Identity Server. - * **Callback Port**: The port of the callback URL. For the registration, the callback URL should be set to http://localhost:[PortNumber]/, for example, http://localhost:12345/. - - {{% alert color="info" %}}Although these settings generally align with those required to log in using SSO with the Teamcenter Connector in your Mendix application, the last two settings depend on the application registration with your Identity Server. Mendix recommends having a separate registration for the Teamcenter Extension on your Identity Server, distinct from your Mendix application’s registration. If you do not do this, conflicts might arise if your Mendix application is running.{{% /alert %}} - -* **Teamcenter X SSO** – Allows you to use the SSO credentials of your Teamcenter X instance. - - {{< figure src="/attachments/appstore/platform-supported-content/modules/teamcenter-extension/teamcenter_sso.png" class="no-border" max-width=75% >}} - - Please work with your Siemens CApS representative to fill out the following: - - * **TcX Client ID** - * **SAM Auth Base URL** - * **SAM Auth Client ID** - * **SAM Auth Client Secret** - * **Token Exchange Client ID** - * **Token Exchange Client Secret** - * **Callback URL** - -##### Mendix Module - -**Mendix module** selects the module where the Entities and Microflows will be created. We recommend that this is a module which is initially empty. - -## Import Mapping {#importmapping} - -Clicking any one of the actions opens an empty [import mapping](/refguide/import-mappings/) page. Here you can define what data you want to retrieve from Teamcenter and how to handle this data in Mendix. Depending on the action, the import mapping page starts with one or multiple entities or objects to configure, one per business object that needs to be configured. - -During configuration, the import mapping page will build up a preview of the Mendix domain model involved in the integration. In addition, the import mapping page shows the corresponding business objects on the Teamcenter side. For this, Teamcenter Extension displays both the display names of the objects and their properties, references, relations, and the corresponding technical names, as they will end up in the Mendix domain model. - -In Teamcenter Extension, the import mapping consists of the following steps: - -1. Object mapping: As Teamcenter works with many layers of specializations of its business objects, in the import mapping page, you need to configure which object type you want to retrieve from Teamcenter and what Mendix objects need to be created, when retrieving these business objects. This is called object mapping. -2. Selection of properties, references, and relations: Configure which properties, references, and relations you want to retrieve from Teamcenter and include in your Mendix model . - -{{< figure src="/attachments/appstore/platform-supported-content/modules/teamcenter-extension/domain-model.png" max-width=80% >}} - -### Object Mapping {#objectmapping} - -Clicking any one of the empty boxes in the import mapping page opens the object mapping dialog. On the left side of the dialog, a tree with all relevant business objects available from the configured Teamcenter instance is displayed. If you have created any custom business objects in Teamcenter BMIDE, those objects will be shown as well. The right side shows a tree of all relevant entities in your Mendix app. - -The relevant objects and entities are dependent on the actions you are configuring. For example, for the action to get `ItemRevisions` from Teamcenter, the Teamcenter tree has an `ItemRevision` as its root object. That means that, for this action, you can only select `ItemRevisions` or its specializations. Similarly, in this example, the Mendix tree has the `TcConnector.ItemRevision` entity as its root entity. - -{{< figure src="/attachments/appstore/platform-supported-content/modules/teamcenter-extension/select-objects.png" >}} - -When retrieving a tree of objects, relevance can also be based on the type of the relation or reference. When working with typed relations o references, the type of Teamcenter business object is dictated by the relation or reference. By limiting the list of Teamcenter objects and Mendix entities to those that are relevant, Teamcenter Extension guides you to select Teamcenter business objects that make sense in the context of the action you want to perform. - -To configure which type of Teamcenter business object you are interested in and what type of Mendix entities this should be mapped to, select a business object in the Teamcenter tree on the left side and an entity on the Mendix tree on the right side and click **OK**. - -It is also possible to create new entities for your integrations. This new entity needs to be a specialization of the root entity in the Mendix tree or one of its specializations. When you want to use a new entity, click your generalization of choice, click the **Create new specialization of selected entity** check box and provide an entity name. Once finishing the configuration for the actions, Teamcenter Extension will create a new entity with the given name and the selected entity as its generalization. You can also reuse or create the specialization of the generated entities in subsequent actions. - -{{< figure src="/attachments/appstore/platform-supported-content/modules/teamcenter-extension/new-entity.png" >}} - -Once you click **OK**, you will return to the import mapping tab with a sidebar open for you to configure which Teamcenter properties, references, and relations to include when retrieving data for this business object. - -### Teamcenter Properties, References, and Relations {#tcprop} - -In the import mapping sidebar, you can configure which Teamcenter properties, references, and relations to include when retrieving data from Teamcenter. The import mapping sidebar is launched automatically after the completion of object mapping. When you are on the import mapping page and the sidebar is closed, you can double-click a previously configured entity to open the sidebar for that entity. - -The sidebar shows all properties, references, and relations for the configured Teamcenter object. Depending on the use case, each one of them is accompanied with check boxes for reading ({{% icon name="view" %}}) and writing ({{% icon name="pencil" %}}) for you to configure what to include when retrieving data from or creating data in Teamcenter. - -{{% alert color="info" %}} The Teamcenter Extension currently does not display compound attributes from Teamcenter. A compound attribute is a property defined on one object but displayed on a different object.{{% /alert %}} - -You often see that check boxes are selected by default or grayed out. In general, the following rules apply: - -1. Properties that are already available on the Mendix entity or one of its generalizations are selected by default and cannot be unchecked. -2. Properties, references, and relations for Marketplace entities are disabled by default, as it is not good practice to change Mendix marketplace content. - -As an example, if a check box for reading ({{% icon name="view" %}}) is selected and grayed out, it means that property already exists as an attribute on the selected object or one of its generalizations. Similarly, if a check box for writing ({{% icon name="pencil" %}}) is selected and grayed out, it means the property is required during creation or revision of the selected object. - -{{< figure src="/attachments/appstore/platform-supported-content/modules/teamcenter-extension/attributes-associations.png" max-width=60% >}} - -You can select and deselect the properties, references, and relations depending on the data you need from Teamcenter. When you select a reference or relation, a new placeholder entity will be added to the object mapping tree. You will need to perform the import mapping for these referenced or related objects in a subsequent step (business object mapping and selection of Teamcenter properties, references, and relations). - -### Microflows and Domain Model - -Once you finished import mapping, click **Generate** to create microflows for the selected use case and its corresponding domain model. These artifacts can be used in your app logic. - -{{< figure src="/attachments/appstore/platform-supported-content/modules/teamcenter-extension/microflow.png" >}} - -## Upgrading Teamcenter Extension V 1.0.0 to V 3.0.0 {#upgrade} - -{{% alert color="info" %}} To prevent conflicts (such as integration duplications), it is advised that one developer in a team upgrades the Teamcenter Extension and commits changes before other developers continue working with the extension.{{% /alert %}} - -If you use Teamcenter Extension V 1.0.0 with Teamcenter Connector V 3.6.1 or below, and want to upgrade to Teamcenter Extension V 3.0.0 and Teamcenter Connector V 2406.3.0, perform the following procedure: - -1. Open your app in a Studio Pro version compatible with Teamcenter Extension V 3.0.0 (see version matrix under [Dependencies](#dependencies) section) -2. Follow the instructions in [How to Use Marketplace Content in Studio Pro](/appstore/general/app-store-content/) to download [Teamcenter Extension V 3.0.0](https://marketplace.mendix.com/link/component/225544) from the Marketplace and install it. -3. When a warning dialog box opens, click **Trust module and enable extension**. Otherwise, Teamcenter Extension will not be installed. -4. Follow the instructions in [How to Upgrade the Module to a Newer Version](/appstore/use-content/#update-module) to upgrade Teamcenter Connector to V 2406.0.0. - - {{% alert color="info" %}}Teamcenter Connector V 2406.3.0 has an updated domain model that makes certain entities and associations in Teamcenter Extension V 1.0.0 redundant. As a result, you will get errors after the upgrade.{{% /alert %}} - -5. To resolve the errors, use one of the solutions described the sections below: - - * [Solution 1](#solution-1) – Delete and recreate microflows—using Solution 1 has the advantage that after completing the procedure, the integrations will appear on the **History** tab. - - * [Solution 2](#solution-2) – Update references and parameters. - -### Resolving the Errors – Solution 1 {#solution-1} - -{{% alert color="info" %}} -Using Solution 1 has an advantage: after completing the procedure, the integrations will appear on the **History** tab. -{{% /alert %}} - -Perform the following steps: - -1. Delete the microflows generated with Teamcenter Extension V 1.0.0. This will cause errors in the locations where these microflows were used. Keep these errors so that you can identify where the microflows need to be implemented again. -2. Go to Teamcenter Extension V 3.0.0 and repeat the steps you did before in Teamcenter Extension V 1.0.0. Simply select the same entities and associations, as they already exist in your domain model. -3. Go over the errors caused by the missing microflows and implement the newly-generated microflows.  - -### Resolving the Errors – Solution 2 {#solution-2} - -Follow the instructions in the table below: - -| Error message                                           | How to Solve the Error                                       | -| ------------------------------------------------------- | ------------------------------------------------------------ | -| `TeamcenterToolkit.BOMWindow` no longer exists          |
  1. Update all references to
    `TcConnector.BOMWindow`.
  2. Search for `TeamcenterToolkit.BOMWindow` to find `BOMapping` parameters where the entity is used, and change it to `TcConnector.BOMWindow`.
| -| `TeamcenterToolkit.top_line` no longer exists           | Update all associations to `TcConnector.top_line`.           | -| The selected Java action parameter […] no longer exists | Set all the Java action parameters again.                    | diff --git a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/_index.md b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/_index.md new file mode 100644 index 00000000000..e1ddd16bd6f --- /dev/null +++ b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/_index.md @@ -0,0 +1,68 @@ +--- +title: "Teamcenter Extension" +url: /appstore/modules/siemens-plm/teamcenter-extension/ +description: "Describes Teamcenter Extension from the Mendix Marketplace. Teamcenter Extension facilitates a low-code approach to integrating with Siemens Teamcenter." +aliases: + - /appstore/modules/teamcenter-extension/ +--- + +## Introduction {#introduction} + +[Teamcenter Extension](https://marketplace.mendix.com/link/component/225544) is a Mendix extension built using the Mendix Extensibility Framework. Its aim is to provide you with an effortless means to harness the capabilities of [Teamcenter Connector](https://marketplace.mendix.com/link/component/111627) for Mendix. Teamcenter Extension is built on Teamcenter Connector. It provides a low-code experience by making it easier to visualize and access Siemens Teamcenter data models and automating creation of Mendix domain models and microflows. + +{{% alert color="info" %}}Teamcenter Extension V 3.0.0 and above is also supported on macOS.{{% /alert %}} + +### Typical Use Cases {#typical-use-cases} + +Teamcenter Extension offers a list of use cases for which domain models and microflows can be created. After you select a use case, it uses an import mapping approach similar to Mendix [import mapping](/refguide/import-mappings/). Here, Teamcenter Extension allows you to select data from the business model of your Teamcenter instance. Teamcenter Extension uses the selected use case, the import mapping, and, in some use cases, additional configurations to generate and update the domain model for your integration and generate one or more ready-to-use microflows that you can drag and drop into your application logic. + +Teamcenter Extension offers the following integration options: + +* Search item revisions +* Create item and item revision +* Update item and item revision +* Revise item revision +* Search datasets +* Get datasets for item revision +* Attach dataset to item revision +* Search workspace objects +* Relate workspace objects +* Get structure +* Get properties + +### License {#license} + +Teamcenter Extension is free to download and use. You may, however, require a Teamcenter (Author or Consumer) license to connect to Teamcenter. + +### Dependencies {#dependencies} + +You must have these Marketplace modules installed: + +* [Teamcenter Connector](https://marketplace.mendix.com/link/component/111627): needed for all versions of Teamcenter Extension +* [Community Commons](https://marketplace.mendix.com/link/component/170): only needed for Teamcenter Extension V 1.0.0 + +Compatibility among Teamcenter Extension, Teamcenter Connector, and Studio Pro is as follows: + +| Teamcenter Extension Version | Teamcenter Connector Version | Studio Pro Version | +| ------------- | ------------- | ------------- | +| 1.0.0 | 3.6.1, V 3.6.0, V 3.5.0 | 10.6.5 thru 10.7 | +| 2.0.0 | 2406.0.0 | 10.12, patch versions 1 and above and 10.16.0 and above | +| 3.0.0 thru 4.1.0 | 2406.3.0 and above | 10.12 patch version 6 and above and 10.16.0 and above | +| 4.1.1 | 2406.3.0 and above | 10.24.0 and above | +| 4.2.0 | 2406.3.0 and above | 10.24.8 and above | + +{{% alert color="info" %}} +Teamcenter Extension is not compatible with Studio Pro versions between 10.8 and 10.11, as well as 10.13.x, 10.14.x, and 10.15.x. If you use one of these Studio Pro versions, a possible workaround is to use Teamcenter Extension in one of the compatible versions of Studio Pro first, create the necessary artifacts, and then import them into your version. However, Mendix always recommends using the latest MTS or LTS Studio Pro version. +{{% /alert %}} + +{{% alert color="info" %}} +If you use Teamcenter Extension V 1.0.0 with Teamcenter Connector V 3.6.1 or below and want to upgrade to Teamcenter Extension V 3.0.0 and Teamcenter Connector V 2406.3.0, see the [Upgrading Teamcenter Extension V 1.0.0 to V 3.0.0](#upgrade) section. +{{% /alert %}} + +### Demo App {#demo-app} + +To see Teamcenter Extension in action, download and play with the [Teamcenter Extension Sample App](https://marketplace.mendix.com/link/component/225910). + +## Extension Installation {#extension-installation} + +Follow the instructions in [Using Marketplace Content](/appstore/use-content/) to import the Teamcenter Extension into your app. diff --git a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/creating-an-integration.md b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/creating-an-integration.md new file mode 100644 index 00000000000..495383d036a --- /dev/null +++ b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/creating-an-integration.md @@ -0,0 +1,135 @@ +--- +title: "Creating an Integration" +url: /appstore/modules/siemens-plm/teamcenter-extension/create-an-integration/ +description: "Describes Teamcenter Extension from the Mendix Marketplace. Teamcenter Extension facilitates a low-code approach to integrating with Siemens Teamcenter." +weight: 1 +--- + +## Main Menu {#main-menu} + +To open Teamcenter Extension in Studio Pro, go to **Extensions** > **Teamcenter Extension** > **Teamcenter Extension**. If you use Studio Pro versions 10.7 or lower, Teamcenter Extension is available under **View** > **Teamcenter Extension**. + +{{% alert color="info" %}} +For details on the version dependencies between Studio Pro and Teamcenter Extension, see the [Dependencies](#dependencies) section. +{{% /alert %}} + +The landing page has with three tabs: **Menu**, **History**, and **Settings**. + +### Menu Tab {#menu-tab} + +The **Menu** tab displays use cases or actions you can create artifacts for using Teamcenter Extension. + +{{< figure src="/attachments/appstore/platform-supported-content/modules/teamcenter-extension/menu-tab.png" >}} + +### Settings Tab {#settings-tab} + +The **Settings** tab allows you to change the **Teamcenter configuration**. + +{{< figure src="/attachments/appstore/platform-supported-content/modules/teamcenter-extension/teamcenter-configuration.png" >}} + +The tab indicates whether you currently have an active Teamcenter session, or whether the session is inactive. + +There are two buttons: + +* **Edit** – allows you to change the settings +* **Sign in** – signs you in to Teamcenter if **Authentication** is set to *Credentials* (see [Signin Configuration](#signin-configuration), below) + +#### Editing Settings {#editing-settings} + +Click **Edit** to change the settings. + +{{< figure src="/attachments/appstore/platform-supported-content/modules/teamcenter-extension/edit-configuration.png" >}} + +You can set up the following information. It will be saved when you click **Save**: + +##### Teamcenter Instance + +While building your app and using Teamcenter Extension you need to provide the details of the Teamcenter instance to connect to. To do this provide the following information under **Teamcenter instance**: + +* **TC URL** – The URL to which calls will be made to sign in and retrieve data. Teamcenter Extension supports both HTTP and HTTPS connections. +* **Certificate Path** – The path to certificates that have .crt and .pfx file extensions. The path should be relative to the app directory. + +## Import Mapping {#import-mapping} + +Clicking any one of the actions opens an empty [import mapping](/refguide/import-mappings/) page. Here you can define what data you want to retrieve from Teamcenter and how to handle this data in Mendix. Depending on the action, the import mapping page starts with one or multiple entities or objects to configure, one per business object that needs to be configured. + +During configuration, the import mapping page will build up a preview of the Mendix domain model involved in the integration. In addition, the import mapping page shows the corresponding business objects on the Teamcenter side. For this, Teamcenter Extension displays both the display names of the objects and their properties, references, relations, and the corresponding technical names, as they will end up in the Mendix domain model. + +In Teamcenter Extension, the import mapping consists of the following steps: + +1. Object mapping: As Teamcenter works with many layers of specializations of its business objects, in the import mapping page, you need to configure which object type you want to retrieve from Teamcenter and what Mendix objects need to be created, when retrieving these business objects. This is called object mapping. +2. Selection of properties, references, and relations: Configure which properties, references, and relations you want to retrieve from Teamcenter and include in your Mendix model . + +{{< figure src="/attachments/appstore/platform-supported-content/modules/teamcenter-extension/domain-model.png" max-width=80% >}} + +### Object Mapping {#object-mapping} + +Clicking any one of the empty boxes in the import mapping page opens the object mapping dialog. On the left side of the dialog, a tree with all relevant business objects available from the configured Teamcenter instance is displayed. If you have created any custom business objects in Teamcenter BMIDE, those objects will be shown as well. The right side shows a tree of all relevant entities in your Mendix app. + +The relevant objects and entities are dependent on the actions you are configuring. For example, for the action to get `ItemRevisions` from Teamcenter, the Teamcenter tree has an `ItemRevision` as its root object. That means that, for this action, you can only select `ItemRevisions` or its specializations. Similarly, in this example, the Mendix tree has the `TcConnector.ItemRevision` entity as its root entity. + +{{< figure src="/attachments/appstore/platform-supported-content/modules/teamcenter-extension/select-objects.png" >}} + +When retrieving a tree of objects, relevance can also be based on the type of the relation or reference. When working with typed relations o references, the type of Teamcenter business object is dictated by the relation or reference. By limiting the list of Teamcenter objects and Mendix entities to those that are relevant, Teamcenter Extension guides you to select Teamcenter business objects that make sense in the context of the action you want to perform. + +To configure which type of Teamcenter business object you are interested in and what type of Mendix entities this should be mapped to, select a business object in the Teamcenter tree on the left side and an entity on the Mendix tree on the right side and click **OK**. + +It is also possible to create new entities for your integrations. This new entity needs to be a specialization of the root entity in the Mendix tree or one of its specializations. When you want to use a new entity, click your generalization of choice, click the **Create new specialization of selected entity** check box and provide an entity name. Once finishing the configuration for the actions, Teamcenter Extension will create a new entity with the given name and the selected entity as its generalization. You can also reuse or create the specialization of the generated entities in subsequent actions. + +{{< figure src="/attachments/appstore/platform-supported-content/modules/teamcenter-extension/new-entity.png" >}} + +Once you click **OK**, you will return to the import mapping tab with a sidebar open for you to configure which Teamcenter properties, references, and relations to include when retrieving data for this business object. + +### Teamcenter Properties, References, and Relations {#teamcenter-properties} + +In the import mapping sidebar, you can configure which Teamcenter properties, references, and relations to include when retrieving data from Teamcenter. The import mapping sidebar is launched automatically after the completion of object mapping. When you are on the import mapping page and the sidebar is closed, you can double-click a previously configured entity to open the sidebar for that entity. + +The sidebar shows all properties, references, and relations for the configured Teamcenter object. Depending on the use case, each one of them is accompanied with check boxes for reading ({{% icon name="view" %}}) and writing ({{% icon name="pencil" %}}) for you to configure what to include when retrieving data from or creating data in Teamcenter. + +{{% alert color="info" %}} The Teamcenter Extension currently does not display compound attributes from Teamcenter. A compound attribute is a property defined on one object but displayed on a different object.{{% /alert %}} + +You often see that check boxes are selected by default or grayed out. In general, the following rules apply: + +1. Properties that are already available on the Mendix entity or one of its generalizations are selected by default and cannot be unchecked. +2. Properties, references, and relations for Marketplace entities are disabled by default, as it is not good practice to change Mendix marketplace content. + +As an example, if a check box for reading ({{% icon name="view" %}}) is selected and grayed out, it means that property already exists as an attribute on the selected object or one of its generalizations. Similarly, if a check box for writing ({{% icon name="pencil" %}}) is selected and grayed out, it means the property is required during creation or revision of the selected object. + +{{< figure src="/attachments/appstore/platform-supported-content/modules/teamcenter-extension/attributes-associations.png" max-width=60% >}} + +You can select and deselect the properties, references, and relations depending on the data you need from Teamcenter. When you select a reference or relation, a new placeholder entity will be added to the object mapping tree. You will need to perform the import mapping for these referenced or related objects in a subsequent step (business object mapping and selection of Teamcenter properties, references, and relations). + +## Generating Artifacts {#generating-artifacts} + +Once you have finished import mapping, click **Generate** to create microflows for the selected use case and its corresponding domain model. These artifacts can be used in your app logic. + +{{< figure src="/attachments/appstore/platform-supported-content/modules/teamcenter-extension/microflow.png" >}} + +## History {#history} + +The **History** tab displays the history of all actions (also referred as integrations) carried out in Teamcenter Extension. + +{{< figure src="/attachments/appstore/platform-supported-content/modules/teamcenter-extension/history-tab.png" >}} + +On the **History** tab, you can view details of each action, such as entities and microflows created, Teamcenter URL used to connect with, the preview of the import mapping, and much more. + + You can also edit, duplicate or delete an action using the buttons in the upper-right corner: + +* **Delete** – This deletes the selected action from the list. However, it does not delete the corresponding entities and microflows, since they may impact pages or other integrations. +* **Duplicate** – This allows you to create a new action based on an existing one. When you click **Duplicate**, it clones the selected action and takes you to the import mapping page, where you can modify your mapping and subsequently create new domain model and microflows. This operation does not modify any of existing actions. +* **Edit** – This allows you to modify an existing action and updating existing domain model and microflows. When you click **Edit**, it takes you to the import mapping page, where you can add or edit entities, attributes, and associations, subsequently updating the domain model and microflows. + +It is not recommended to make specific adjustments to artifacts generated by Teamcenter Extension outside of Teamcenter Extension. Doing so may result in breaking the integration. Instead, you should make adjustments inside Teamcenter Extension using the **Delete**, **Duplicate** or **Edit** operations, wherever possible. Examples of adjustments that are not advisable outside Teamcenter Extension are as follows: + +* Modifying the **CreateInput** and **CompoundCreateInput** entities generated from The **Create Item** action +* Modifying any entity generated from the **Revise Item Revision** action +* Deleting attributes or associations generated by Teamcenter Extension +* Deleting or editing microflows generated by Teamcenter Extension + +However, you can make the following adjustments outside Teamcenter Extension: + +* Adding attributes or associations +* Moving microflows +* Renaming microflows + +If you select an item in the **Action** list, Teamcenter Extension performs a validation check to see if the Teamcenter objects, entities, and microflows still exist and are valid. The results are reported in the **Validation** section. \ No newline at end of file diff --git a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/06-get-datasets-for-item-revision.md b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/06-get-datasets-for-item-revision.md new file mode 100644 index 00000000000..768aa1471b6 --- /dev/null +++ b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/06-get-datasets-for-item-revision.md @@ -0,0 +1,52 @@ +--- +title: "Get Datasets for Item Revision" +url: /appstore/modules/siemens-plm/teamcenter-extension/create-an-integration/integrations/get-datasets-for-item-revision/ +description: "Provides step by step guide to use \"Get Datasets for Item Revision\" integration in Teamcenter Extension." +weight: 6 +--- + +## Introduction {#introduction} +The **Get Dataset for Item Revision** integration allows you to generate domain model and microflow to retrieve **Datasets** for an **Item Revision** and subsequently download files present inside the dataset. For those not familiar with Teamcenter, a **Dataset** is a container for files and related metadata. They are typically attached to a business object such as **Item Revision**. + +This document takes you through a use case where we want to retrieve PDF, MS Word and Excel documents stored inside a dataset that is attached to an **Item Revision**. + +## Step-by-step Guide {#step-by-step-guide} +1. Make sure you have set up your credentials in the **Settings tab** before following these instructions. For more instructions on how to configure your settings, follow the steps [here](/appstore/modules/siemens-plm/teamcenter-extension/create-an-integration/#settings-tab). +2. Click on the **Get Dataset for Item Revision** button on the home page to start configuring your integration. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/icon.png">}} +3. You will land on the [import mapping page](/refguide/import-mappings/). This determines what data is retrieved from Teamcenter and what type of objects are created in Mendix. +There is a parameter entity placeholder on the top, which lets you select the object from which the **Dataset** should be retrieved +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/import-mapping.png">}} +Click on the parameter entity placeholder to open the object mapping panel. The left side shows Teamcenter **Item Revision** objects (out of the box and custom) retrieved from the Teamcenter instance. Select the `Item Revision` object. +4. The Mendix entity on the right is selected by default. The entity will be used as an input parameter to get **Datasets** for any type of **Item Revision**. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/object-mapping.png">}} +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/object-mapping-result.png">}} +After the object mapping panel is closed, a sidebar opens that shows the set of **8 default relationships** selected by default. These are the 8 most commonly used relationships in Teamcenter from which datasets are retrieved. You can modify the selections but in this case, we will keep the 8 relationships selected by default. You can always come back to it by **double clicking** on the annotation. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/property-mapping.png">}} +5. Now select the entity placeholder (below the parameter entity placeholder) to open the object mapping panel. Select the **Dataset** object on the left. The right side shows the relevant Mendix entities that can be mapped to the **Dataset** object and will be used to create objects when a **Dataset** is retrieved for an **Item Revision**. In our case, we want to have an entity specifically for **Datasets**. Hence, we select `TcConnector.Dataset` and then click on the checkbox to C**reate new Specialization of selected Entity**. The entity will be automatically named `Dataset` after the Teamcenter Object name, but it can be renamed here if required. Now click on **OK**, to finish the object mapping and close the object mapping dialog. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/object-mapping-association.png">}} +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/property-mapping-association.png">}} +6. Closing the object mapping dialog opens the attributes and associations sidebar. Here you can select from all properties available on the selected object. For our use case, we will not be adding any additional properties so you can close the panel by clicking on the close button. +7. Double click on the annotation **Retrieve all dataset types** to open the configure panel. +8. This panel lets you choose if you want to retrieve certain dataset types only (such as PDF, MS Word, etc.). +9. Since we are particularly interested in retrieving only documents (PDF, Word and Excel) attached to the item revision, we will select only the following **Dataset** types: + * PDF + * MS Word + * MS Excel + + {{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/object-mapping-association-result.png">}} +Close the panel +10. Click on the **Generate** button to generate the appropriate domain model and microflow. +11. Once the generation is done, you will be redirected to the **History tab** which shows a summary of what has been generated. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/history.png">}} + + +## Result {#result} +### Domain Model {#domain-model} +The extension generated the following entities in your domain model. +* **Dataset** – This is an entity to represent a Dataset object from Teamcenter. This serves as an input to microflow that attaches datasets. + +### Microflows {#microflows} +The following microflows are generated +* **GetDatasetForItemRevision** – This microflow implements the logic to retrieve specific datasets types (selected in step 8) from `Item Revision` based on the 8 relationships chosen from step 3. +* **Dataset_RetrieveFilesorImages** – This microflow implements the logic to retrieve files or images stored within the dataset. \ No newline at end of file diff --git a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/07-attach-dataset-to-item-revision.md b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/07-attach-dataset-to-item-revision.md new file mode 100644 index 00000000000..079d753a605 --- /dev/null +++ b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/07-attach-dataset-to-item-revision.md @@ -0,0 +1,51 @@ +--- +title: "Attach Dataset to Item Revision" +url: /appstore/modules/siemens-plm/teamcenter-extension/create-an-integration/integrations/attach-dataset-to-item-revision/ +description: "Provides step by step guide to use \"Attach Dataset to Item Revision\" integration in Teamcenter Extension." +weight: 7 +--- + +## Introduction {#introduction} +The **Attach Dataset to Item Revision** integration allows you to generate the domain model and microflows to create and attach Teamcenter **Datasets** (or its specializations) containing file documents to an **Item Revision** in Teamcenter. For those not familiar with Teamcenter, a **Dataset** essentially is a container for files and related metadata. If you want to attach a document to a Teamcenter object, you do this using datasets. + +This document takes you through a use case where we want to attach a PDF document to an **Item Revision** with a **Specification** relation. + +## Step-by-step Guide {#step-by-step-guide} +1. Make sure you have set up your credentials in the **Settings tab** before following these instructions. For more instructions on how to configure your settings, follow the steps [here](/appstore/modules/siemens-plm/teamcenter-extension/create-an-integration/#settings-tab). +2. Click on the **Attach Dataset to Item Revision** button on the home page to start configuring your integration. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/icon.png">}} +3. You will land on the [import mapping page](/refguide/import-mappings/). This determines what data is retrieved from Teamcenter and what type of objects are created in Mendix. +Click on one of the placeholder entities to start the import mapping. + {{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/import-mapping.png">}} +4. In the object mapping dialog that opens, the left side shows Teamcenter **Dataset** objects (out of the box and custom) retrieved from the Teamcenter instance. For this use case, select **Dataset** +The right side shows the relevant Mendix entities that can serve as input parameters for the microflow to attach datasets. In our case, we want to have an entity specifically for **Datasets**. Hence, we select `TcConnector.Dataset` and then click on the checkbox to **Create new Specialization of selected Entity**. The entity will automatically be named **Dataset** after the Teamcenter Object name, but it can be renamed here if required. Now click on **OK**, to finish the object mapping and close the object mapping dialog. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/object-mapping.png">}} +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/object-mapping-result.png">}} +5. Closing the object mapping dialog opens the attributes and associations sidebar. Here you can select from all properties available on the selected object. For our use case, we will not be adding any additional properties so you can close the panel by clicking on the backdrop. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/property-mapping.png">}} +6. Double click on the annotation **Attach any dataset** to open the configure panel. +This panel lets you choose if you want to configure settings such as **Dataset type**, **File type** and **Relation name**, needed to upload **Datasets**, inside the Extension or have them provided as input parameters to the generated microflows. +Since we are particularly interested in building the logic to attach a PDF document to item revision, make the following selections by turning on the switches. + * Dataset Type → PDF + * File Type → PDF_Reference (*.pdf) + * Relation Name → Specifications + + {{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/configure-dataset-attachment.png">}} +**Close** the panel. +7. Click on the **Generate** button to generate the appropriate domain model and microflows. +8. Once the generation is done, you will be redirected to the **History tab** which shows a summary of what has been generated. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/history.png">}} + +## Result {#result} +### Domain Model {#domain-model} +The extension generated the following entities in your domain model. +* **Dataset** – This is an entity to represent a `Dataset` object from Teamcenter. This serves as an input to microflow that attaches datasets. + +### Microflows {#microflows} +Since we chose specific options in Step 6, the following microflow is generated. +* **Dataset_AttachDataset** – This microflow implements the logic to create and attach PDF dataset type with `PDF_Reference` file type and `Specification` relation to an **Item Revision**. + +Depending on what options are chosen in the configure panel (step 7), additional microflows are generated. +* **GetAvailableDatasetTypes** – This microflow implements the logic to retrieve all available dataset types. +* **GetFileTypesForDatasetTypes** – This microflow implements the logic to retrieve all available files types for a specific dataset type. +* As we configured the dataset type and file type in the extension, the extension did not generate these additional microflows for this use case. \ No newline at end of file diff --git a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/08-search-workspace-objects.md b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/08-search-workspace-objects.md new file mode 100644 index 00000000000..c92fe70d7b5 --- /dev/null +++ b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/08-search-workspace-objects.md @@ -0,0 +1,48 @@ +--- +title: "Search Workspace Objects" +url: /appstore/modules/siemens-plm/teamcenter-extension/create-an-integration/integrations/search-workspace-objects/ +description: "Provides step by step guide to use \"Search Workspace Objects\" integration in Teamcenter Extension." +weight: 8 +--- + +## Introduction {#introduction} +The **Search Workspace Objects** integration allows you to generate the domain model and microflow to search for **Workspace Objects** or its specialization. For those familiar with Teamcenter, the resulting microflow implements the out of the box saved query `General...` from Teamcenter. + +This document takes you through a use case where we want to retrieve **FMEA (Failure Modes and Effects Analysis)** object types from Teamcenter. The purpose of **FMEA** is to proactively identify risks involved in product design /process and mitigate/eliminate them by defining prevention and detection actions. + +## Step-by-step Guide {#step-by-step-guide} +1. Make sure you have set up your credentials in the **Settings tab** before following these instructions. For more instructions on how to configure your settings, follow the steps [here](/appstore/modules/siemens-plm/teamcenter-extension/create-an-integration/#settings-tab). +2. Click on the **Search Workspace Objects** button on the home page to start configuring your integration. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-workspace-objects/icon.png">}} +3. You will land on the [import mapping page](/refguide/import-mappings/). This determines what data is retrieved from Teamcenter and what type of objects are created in Mendix. +Click on one of the placeholder entities to start the import mapping. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-workspace-objects/import-mapping.png">}} +4. In the object mapping dialog that opens, the left side shows Teamcenter objects (out of the box and custom) retrieved from the Teamcenter instance. Since we are interested in retrieving **FMEA** objects, we select `FMEA`. +The right side shows the relevant Mendix entities for which object could be created when we retrieve **Workspace objects** from Teamcenter. In our case, we want to have an entity specifically for **FMEA** so we can make changes and add new attributes to it. Hence, we select `TcConnector.WorkspaceObject` and then click on the checkbox to **Create new Specialization of selected Entity**. The entity will automatically be named after the Teamcenter Object name, but it can be renamed here if required. Now click on **OK**, to finish the object mapping and close the object mapping dialog. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-workspace-objects/object-mapping.png">}} +5. Closing the object mapping dialog opens the attributes and associations sidebar. Here you can select from all properties available on the selected Teamcenter Object the properties you want to have within your Mendix application. In this example, we want to create an integration where we retrieve additional **FMEA** object type attributes. Select in the side panel the following attributes to add to the `FMEA` entity. + * FMEA Category + * Last Saved Date + * Version Information + + {{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-workspace-objects/property-mapping.png">}} +6. After this selection, click on the **close** button to close the side panel. +7. Click on the **Generate** button to generate the appropriate Domain model and microflows so that you can start retrieving **FMEA** objects in your application. +8. Once the generation is done, you will be redirected to the **History tab** which shows a summary of what has been generated. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-workspace-objects/history.png">}} + +## Result {#result} +### Domain Model {#domain-model} +The extension generated the following entities in your domain model. +* **FMEA** – This is an entity to represent a FMEA Object from Teamcenter. The objects can be retrieved via `FMEA_PerformGeneralSearch`. + +### Microflows {#microflows} +The extension generated the following microflow in your project. +* **FMEA_PerformGeneralSearch** - This microflow can be used to retrieve a list of `FMEA` object types from Teamcenter. +The microflow receives three input parameters, a `ConfigName`, `GeneralQuery` and `SearchInput` + 1. The `configName` must be the **configName** on a **TcConnection.TeamcenterConfiguration** object and determines which Teamcenter configuration will be used to connect to Teamcenter. +If only one Teamcenter Configuration is used, the parameter can be left empty. + 2. The `GeneralQuery` is required and used as input arguments (entered by user as input) while searching for **FMEA**. + 3. The `SearchInput` parameter is used to provide additional input that’s required by the Teamcenter SOA that is called upon. + +The microflow will return a list of **FMEA** object types that matches the `SearchCriteria` provided in the `GeneralQuery`. \ No newline at end of file diff --git a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/09-relate-workspace-objects.md b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/09-relate-workspace-objects.md new file mode 100644 index 00000000000..dadbd9f6fae --- /dev/null +++ b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/09-relate-workspace-objects.md @@ -0,0 +1,45 @@ +--- +title: "Relate Workspace Objects" +url: /appstore/modules/siemens-plm/teamcenter-extension/create-an-integration/integrations/relate-workspace-objects/ +description: "Provides step by step guide to use \"Relate Workspace Objects\" integration in Teamcenter Extension." +weight: 9 +--- + +## Introduction {#introduction} +The **Relate Workspace Objects** integration allows you to generate the domain model and microflow to relate two **Workspace Objects** or their specialization from Teamcenter. The resulting microflow implements the `Create relation` action from the TcConnector module. +This document takes you through a use case where we want to relate a **CAE 3D Analysis** object with an **Item Revision**. A **CAE 3D Analysis** object typically contains simulation files of a **CAE (Computer Aided Engineering) 3D Analysis**. It can also contain results after the simulation has completed. The **Item Revision** contains the **CAD Parts** on which the simulation is to be performed. Users would want to relate the two objects to trace for which parts a 3D simulation has been performed. The relation type that will be created between the two objects is `CAE Target`. + + +## Step-by-step Guide {#step-by-step-guide} +1. Make sure you have set up your credentials in the **Settings tab** before following these instructions. For more instructions on how to configure your settings, follow the steps [here](/appstore/modules/siemens-plm/teamcenter-extension/create-an-integration/#settings-tab). +2. Click on the **Search Item Revision** button on the home page to start configuring your integration. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/relate-workspace-objects/icon.png">}} +3. You will be presented with the [import mapping page](/refguide/import-mappings/). Here we can determine what data is retrieved from Teamcenter and what type of objects should be created in Mendix. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/relate-workspace-objects/import-mapping.png">}} +4. When defining a relationship between two objects in Teamcenter, the object from which the relationship originates is called the **Primary Object** while the object to which it’s referenced is called the **Secondary Object**. For this reason, you’re seeing two placeholder entities on the import mapping page – **Primary entity** and **Secondary entity**. In our case, our primary object will be `Item Revision` while the secondary object will be `CAE 3D Analysis Revision`. +5. Click on the **Primary entity** placeholder. +6. In the object mapping dialog that opens, the left side shows Teamcenter objects (out of the box and custom) retrieved from your configured Teamcenter instance. Since we are interested in retrieving **Item Revision** objects, we select `Item Revision`. +The right side shows the relevant Mendix entities that can be created when we retrieve **Workspace Objects** from Teamcenter. In our case, we are only relating two objects and won’t be making any change to it. Hence, we just select the marketplace entity `TcConnector.WorkspaceObject`. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/relate-workspace-objects/object-mapping.png">}} +7. Closing the object mapping dialog opens the relations sidebar. Here you can choose to select the relationship name between the two objects. If you choose a **Relation Type**, the extension will generate a microflow to relate the two objects with the selected relation type. If no relation name is selected, the relation type needs to be provided manually in the microflow that gets generated to relate the objects. +8. In our case, we will select the `CAE Target` relationship. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/relate-workspace-objects/property-mapping.png">}} +9. After this selection, click on the **close** button to close the side panel. +10. Click on the **Secondary entity** placeholder and repeat the previous steps. But this time select `CAE 3D Analysis Revision` on the left and `TcConnector.ModelObject` on the right. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/relate-workspace-objects/object-mapping-association.png">}} +11. Click on the **Generate** button to generate the appropriate Domain model and microflows. +12. Once this has been completed, you will be redirected to the **History tab** which shows a summary of what has been generated. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/relate-workspace-objects/history.png">}} + +## Result {#result} +### Domain Model {#domain-model} +The extension has not generated any new entities since we are reusing the existing entities from the TcConnector Marketplace module. + +### Microflows {#microflows} +The extension generated the following microflow in your project. +* **WorkspaceObject_RelateToModelObject** - This microflow can be used to relate Primary object and Secondary object (i.e. `Item Revision` and `CAE 3D Analysis Revision` in this case). +The microflow receives four input parameters, a **ConfigName**, **Primary Workspace Object**, **Secondary Workspace Object** and **Relation Type**. + 1. The `configName` must be the **configName** of a **TcConnection.TeamcenterConfiguration** object and determines which Teamcenter configuration will be used to connect to Teamcenter. +If only one Teamcenter Configuration is used, the parameter can be left empty. + 2. The **Primary** and **Secondary Workspace Objects** are the objects between which the relation is to be created. + 3. The **Relation** is the **Relationship Type** between the two objects. In our case, this will be `CAE Target`. \ No newline at end of file diff --git a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/10-get-properties.md b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/10-get-properties.md new file mode 100644 index 00000000000..ffc38f33495 --- /dev/null +++ b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/10-get-properties.md @@ -0,0 +1,38 @@ +--- +title: "Get Properties" +url: /appstore/modules/siemens-plm/teamcenter-extension/create-an-integration/integrations/get-properties/ +description: "Provides step by step guide to use \"Get Properties\" integration in Teamcenter Extension." +weight: 10 +--- + +## Introduction {#introduction} +The **Get Properties** integration allows you to generate a microflow to retrieve additional properties of a Teamcenter **Workspace Object** or specializations thereof and the corresponding domain model. The resulting microflow implements the `Get Properties` action from Teamcenter Connector. + +This document takes you through a use case where we want to retrieve additional properties of a **Part Revision** object. **Part Revisions** are specific iterations of a part of a product that is managed using Teamcenter. A P**art Revision** contains essential information like the schematics of the **Part**. As a **Part Revision** is a sub-type of an **Item Revision**, it can be revised. + +## Step-by-step Guide {#step-by-step-guide} +1. Make sure you have set up your credentials in the **Settings tab** before following these instructions. For more instructions on how to configure your settings, follow the steps [here](/appstore/modules/siemens-plm/teamcenter-extension/create-an-integration/#settings-tab). +2. Click on the **Get Properties** button on the home page to start configuring your integration. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-properties/icon.png">}} +3. You will land on the [import mapping page](/refguide/import-mappings/). This determines what data is retrieved from Teamcenter and what type of objects are created in Mendix. You’ll also notice the **Get Properties Configuration** side bar opens by default. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-properties/import-mapping.png">}} +4. By default, this option is turned on. This means it will generate a microflow to create and populate Mendix Model Objects for a given list of Teamcenter product `UIDs`. If the option is turned off, the extension will generate a microflow to update and overwrite a list of existing Mendix Model Objects based on the selections made in the import mapping page. +5. Keep the option turned on and **close** the configuration panel. +6. Click on one of the placeholder entities to open the object mapping panel. The left side of the panel displays workspace objects and its sub-types (out of the box and custom). Since we are interested in retrieving **Part Revision** object properties, we select the `Part Revision` object. +7. The right side shows the relevant Mendix entities that can serve as input parameters for the microflow to retrieve additional properties. In our case, we want to have an entity specifically for **Part Revision**. Hence, we select `TcConnector.WorkspaceObject` and then click on the checkbox to **Create new Specialization of selected Entity**. The entity will be automatically named `PartRevision` after the Teamcenter Object name, but it can be renamed here if required. Now click on **OK**, to finish the object mapping and close the object mapping dialog. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-properties/object-mapping.png">}} +8. Closing the object mapping dialog opens the attributes and associations sidebar. Here you can select from all properties available on the selected object. In this case, we will not be selecting any additional properties. Close the sidebar by clicking on the import mapping page. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-properties/property-mapping.png">}} +9. Click on **Generate** button to generate the appropriate domain model and microflows. +10. Once the generation is done, you will be redirected to the **History tab** which shows a summary of what has been generated. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-properties/history.png">}} + +## Result {#result} +### Domain Model {#domain-model} +The extension generated the following entities in your domain model. +* **PartRevision** – This is an entity representing Part Revision in Teamcenter and serves as an input to the Java action that retrieve list of part revisions from the Teamcenter product `UIDs`. + +### Microflows {#microflows} +The following microflows are generated. +* **PartRevision_GetPropertiesByUIDs** – This microflow implements the logic to retrieve additional properties of part revisions based on the provided `UID` and Teamcenter configuration `Name`. +* **ModelObjectList_ToUIDList** – This microflow implements the logic to retrieve `UIDs` for a list of model objects. \ No newline at end of file diff --git a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/11-get-structure.md b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/11-get-structure.md new file mode 100644 index 00000000000..87e2532ab0b --- /dev/null +++ b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/11-get-structure.md @@ -0,0 +1,71 @@ +--- +title: "Get Structure" +url: /appstore/modules/siemens-plm/teamcenter-extension/integrations/get-structure/ +description: "Provides step by step guide to use the \"Get Structure\" integration in Teamcenter Extension." +weight: 11 +--- + +## Introduction {#introduction} + +The **Get Structure** integration allows you to generate the domain model and microflows to configure a Bill-of-Material (BOM) window and retrieve **BOM structures** from Teamcenter. A **BOM window** displays a **BOM structure** inside a Mendix application. + +This document takes you through a use case of creating logic using the Teamcenter Extension to display a simple **BOM structure** with options to configure it according to our needs. + +## Step-by-Step Guide {#step-by-step-guide} + +1. Make sure you have set up your credentials in the **Settings tab** before following these instructions. For more instructions on how to configure your settings, follow the steps in the [Settings Tab](/appstore/modules/siemens-plm/teamcenter-extension/create-an-integration/#settings-tab) section of *Teamcenter Extension*. +2. Click on the **Get Structure** button on the home page to start configuring your integration. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/icon.png">}} +3. When you click on this integration for the very first time, you’ll see a popup warning indicating that Mendix should be used to display small **BOM structures**. For larger **BOM structures**, it is recommended to use **Teamcenter Active Workspace**. Click **OK** to proceed further. This warning shows only the first time you click the integration. +4. You will land on the [import mapping page](/refguide/import-mappings/). This determines what data is retrieved from Teamcenter and what type of objects are created in Mendix. You’ll also notice the **Configure structure** side bar opens by default. This gives you the ability to configure the **BOM structure** at design time or have the Extension generate microflows where the BOM configurations are input parameters. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/import-mapping.png">}} + 1. Turn on **Revision Rule**. This will generate a microflow to retrieve **Structure** with **Revision Rule** as the input parameter and a microflow to retrieve **Revision Rules**. In other words, this lets you build a feature in your app where you can give the end-users the ability to select a **Revision Rule** at run-time and configure the BOM with the selected **Revision Rule**. + + If the option is turned off, the Extension will generate a microflow to retrieve **Structures** using the default revision rule (typically **LatestWorking**). + + 2. Turn on **Variant rules** option. Just like with **Revision Rule**, this will generate a microflow to retrieve **Structures** with **Variant Rules** as an input parameter and a microflow to retrieve **Variant Rules**. Just like with **Revision Rule** option, this also lets you build a feature in your app where you can give the end users the ability to select a **Revision Rule** at run-time and configure the BOM with selected **Variant Rule**. + + If the option is turned off, the extension will generate a microflow to retrieve structures without applying any variant rules. + + 3. Turn on the **BOM window properties** flag. This will allow you to configure the **BOM window properties** (see below) at design time. The Extension will generate a microflow to retrieve **Structures** with the selected properties. + + If the option is turned off, the Extension will generate a microflow to retrieve structures with `TcConnector.BOMWindowPropFlagMap` object as input parameter. This is a **HashMap** used in the Teamcenter Java SOA API when creating BOM windows and controls various display and behavior settings for BOM windows. +For more details on the **BOM Window properties**, please refer to Teamcenter Documentation. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/import-mapping-2.png">}} + +5. **Close** the configure structure panel. +6. In the import mapping page, click on `BOMLine` entity. This opens the Object Mapping dialog. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/import-mapping-empty.png">}} +7. In the object mapping dialog, the left side of the panel displays **BOMLine** and its sub-types. In Teamcenter, a **BOMLine** is a runtime object that represents a single entry/row in a product structure. The **BOM Lines** define the hierarcy of the structure and attached to each **BOMLine** is an **Item Revision**. The **BOMLine** is not a persistent item in the database. Instead, **BOMLines** are generated dynamically when a **BOMWindow** is created. +8. Select the parent **BOMLine** object. +9. The right side shows the relevant Mendix entities that can serve as input parameters to the microflow generated. Select the marketplace entity `TeamcenterToolkit.BOMLine` and click on the checkbox to **Create new Specialization of selected Entity**. The entity will be automatically named `BOMLine` after the Teamcenter Object name, but it can be renamed here if required. Now click on **OK**, to finish the object mapping and close the object mapping dialog. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/object-mapping.png">}} +10. Closing the object mapping dialog opens the attributes and associations sidebar. Here you can select from all properties available on the selected object. For our use case, we will not be adding any additional properties so you can close the panel by clicking on the **close** button. +11. Click on the other entity placeholder (**ItemRevision**) to re-open the object mapping dialog. +12. For our use case, the aim is to display **Item Revisions** in the **BOM tree**. Hence, select `ItemRevision` on the left and click on the checkbox to **Create a specialization of TcConnector.ItemRevision** on the right. Click **OK** to close the object mapping dialog. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/object-mapping-2.png">}} +13. This will re-open the **Attributes and Associations** sidebar on the right. Select the following attributes + * Last Saved Date (lsd) + * Maturity + + **Close** the panel. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/object-mapping-result.png">}} +14. Click on the **Generate** button to generate the appropriate domain model and microflows. +15. Once the generation is done, you will be redirected to the **History tab** which shows a summary of what has been generated. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/history.png">}} + +## Result {#result} +### Domain Model {#domain-model} +The extension generated the following entities in your domain model. +* **BOMLine** – This is an entity to represent the BOMLine object in Teamcenter. As stated before, the BOMLines define the hierarchy in a structure. When navigating the BOM, the BOMLine serves as an input to microflow that expands the BOM structure +* **ItemRevision** – This is an entity to represent the Item Revision object in Teamcenter. The ItemRevision also serves as an input to microflows that create the BOM window and retrieve variant rules. + +### Microflows {#microflows} +The following microflows are generated. +* **ItemRevision_CreateBOMWindow** – This microflow implements the logic to create a BOM window with input item revision as its top line. +* **BOMWindow_GetTopBOMLine** – This microflow implements the logic to retrieve the top line or root of the BOM structure. +* **BOMLine_ExpandAllLevels_GetAll** – This microflow implements the logic to expand all levels of the BOM structure. +* **BOMLine_ExpandOneLevel_GetChildren** – This microflow implements the logic to expand just one level of the BOM structure. +* **BOMWindow_Close** – This microflow implements the logic to close the BOM Window. +* **GetRevisionRules** – This microflow implements the logic to retrieve revision rules from your Teamcenter instance. +* **ItemRevision_VariantRules** – This microflow implements the logic to retrieve variant rules from your Teamcenter instance. \ No newline at end of file diff --git a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/_index.md b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/_index.md new file mode 100644 index 00000000000..f1785d90108 --- /dev/null +++ b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/_index.md @@ -0,0 +1,22 @@ +--- +title: "Integration Guides" +url: /appstore/modules/siemens-plm/teamcenter-extension/create-an-integration/integrations/ +weight: 2 +description: "Overview with step by step guides for various integrations supported by the Teamcenter Extension." +--- + +## Introduction {#introduction} + +Follow these step-by-step guides for various integrations supported by the Teamcenter Extension: + +* Search Item Revisions +* Create Item with Item Revision +* Update Item with Item Revision +* Revise Item Revision +* Search Datasets +* Get Datasets for Item Revision +* Attach Dataset to Item Revision +* Search Workspace Objects +* Relate Workspace Objects +* Get Properties +* Get Structure \ No newline at end of file diff --git a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/create-item-with-item-revision.md b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/create-item-with-item-revision.md new file mode 100755 index 00000000000..a8b79d2001d --- /dev/null +++ b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/create-item-with-item-revision.md @@ -0,0 +1,68 @@ +--- +title: "Create Item with Item Revision" +url: /appstore/modules/siemens-plm/teamcenter-extension/integrations/create-item-with-item-revision/ +description: "Provides step by step guide to use the \"Create Item with Item Revision\" integration in Teamcenter Extension." +weight: 2 +--- + +## Introduction {#introduction} + +The **Create Item with Item Revision** integration allows you to configure and generate the domain model and microflow to create an `Item` with `ItemRevision` or its specializations in Teamcenter. The resulting microflow implements the `Create Object` and `Update Properties` actions from the Teamcenter Connector. + +This document takes you through a use case of creating Problem Reports in Teamcenter. Problem Reports, represented by the `Problem Report Revision` business object, are used to manage the documentation or reproduction of an issue. They can also be used to determine the severity and priority of the issue. + +## Step-by-Step Guide {#step-by-step-guide} + +Follow these steps to create the integration: + +1. Make sure you have set up your credentials on the **Settings** tab before following these instructions. For more instructions on how to configure your settings, follow the steps in the [Settings Tab](/appstore/modules/siemens-plm/teamcenter-extension/create-an-integration/#settings-tab) section of *Teamcenter Extension*. + +2. Click the **Create Item w/ Item Revision** button on the home page to start configuring your integration. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/icon.png">}} + +3. The [Import Mapping page](/refguide/import-mappings/) is displayed. This determines what data is retrieved from Teamcenter, and what type of objects are created in Mendix. + When creating a `Problem Report` in Teamcenter, two objects are generated: `Problem Report` (sub-class of `Item`) and its associated `Problem Report Revision` (sub-class of `Item Revision`). As such, the import mapping page contains placeholders to map both objects to Mendix entities. + Click one of the top placeholder entities to start the import mapping. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/import-mapping.png">}} + +4. In the object mapping window that opens, follow these steps: + + 1. The left side shows all Teamcenter objects retrieved from the Teamcenter instance. These can be out-of-the-box or custom. For this use case, you want to create Problem Reports, so you select `Problem Report`, which can be found under `Item` > `Change Item` > `Generic Problem Report`. + 2. The right side shows the Mendix entities that can serve as input parameters for the microflow to create an Item with Item Revision. If you create your own entity here, you can ensure that additional attributes are set in Teamcenter upon creation. As such, select `TcConnector.ItemRevision`, then select the **Create new specialization of selected entity** checkbox. The entity is automatically named `PartRevision` after the Teamcenter Object name, but it can be renamed here if required. + Click **OK** to finish the object mapping and close the object mapping window. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/object-mapping.png">}} +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/object-mapping-result.png">}} + +5. For this use case, you also want to create a Problem Report Revision, so repeat this process to select `Problem Report Revision` with another specialized entity. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/property-mapping.png">}} + +6. Once you close the object mapping window, the attributes and associations sidebar is displayed. From here, select the properties you want to have within your Mendix app. For this use case, you want to create an integration to retrieve additional Problem Report Revision details. From the side panel, select the following attributes to add to the `Problem Report Revision` entity: + + * `Severity Rating` + + Once selected, click the backdrop or the close button to close the side panel. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/attribute-mapping.png">}} + +7. Click the **Generate** button to generate the appropriate domain model and microflows. + Once the generation is complete, you are redirected to the **History** tab, which displays a summary of what has been generated. + {{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/history.png">}} + +## Result {#result} + +The following sections describe the resulting domain model and microflows. + +### Domain Model {#domain-model} + +The extension generated the following entities in your domain model: + +* `ProblemReport` – This is an entity representing a Problem Report from Teamcenter. It can be used to create a new Item in Teamcenter. +* `ProblemReportRevision` – This is an entity representing Problem Report Revision from Teamcenter. It can be used to create a new Item Revision in Teamcenter. +* `ProblemReportCreateInput` – This is a helper entity that is used in the `ProblemReport_CreateItemAndItemRevision` microflow to create the Item in Teamcenter. +* `ProblemReportRevisionCompoundCreateInput` – This is a helper entity that is used in the `ProblemReport_CreateItemAndItemRevision` microflow to Create the `ItemRevision` in Teamcenter. + +### Microflows {#microflows} + +The extension generated the following microflows in your project: + +* `ProblemReport_CreateItemAndItemRevision` – This microflow implements the logic to create an item with item revision with only the necessary properties, and then it updates the objects with additional properties. +* `ProblemReportRevision_RetrieveProblemReport` – This microflow implements the logic to retrieve problem reports revision. It is primarily available if you are interested in retrieving problem report revisions that were created. diff --git a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/revise-item-revision.md b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/revise-item-revision.md new file mode 100755 index 00000000000..51abf21968c --- /dev/null +++ b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/revise-item-revision.md @@ -0,0 +1,53 @@ +--- +title: "Revise Item Revision" +url: /appstore/modules/siemens-plm/teamcenter-extension/integrations/revise-item-revision/ +description: "Provides step by step guide to use the \"Revise Item Revision\" integration in Teamcenter Extension." +weight: 4 +--- + +## Introduction {#introduction} + +The **Revise Item Revision** integration allows you to configure and generate the domain model and microflow to revise an `Item Revision` or its specializations in Teamcenter. The resulting microflow implements the `Revise Object` and `Update Properties` actions from the Teamcenter Connector. + +This document takes you through a use case of creating a revision of a `Requirement Revision` object. The `Requirements` object in Teamcenter facilitates the capture, organization, and tracking of various product requirements throughout the product lifecycle. `Requirements` undergo changes during the product's lifecycle, so new revisions of this object are created. + +## Step-by-Step Guide {#step-by-step-guide} + +1. Make sure you have set up your credentials on the **Settings** tab before following these instructions. For more instructions on how to configure your settings, follow the steps in the [Settings Tab](/appstore/modules/siemens-plm/teamcenter-extension/create-an-integration/#settings-tab) section of *Teamcenter Extension*. + +2. Click the **Revise Item Revision** button on the home page to start configuring your integration. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/revise-item-revision/icon.png">}} + +3. The [Import Mapping page](/refguide/import-mappings/) is displayed. This determines what data is retrieved from Teamcenter, and what type of objects are created in Mendix. Click one of the placeholder entities to start import mapping. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/revise-item-revision/object-mapping.png">}} + +4. In the object mapping window that opens, follow these steps: + + 1. The left side shows all Teamcenter objects retrieved from the Teamcenter instance. These can be out-of-the-box or custom. For this use case, you want to revise `Requirements Revisions`, so select `Requirement Revision`, which is available under `Item Revision`. + {{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/revise-item-revision/object-mapping.png">}} + 2. The right side shows the Mendix entities that can be used to create the new Revision of the Item Revision in Teamcenter. You want to have an entity specifically for `Requirement Revisions` so you can choose custom properties to be set when revising the `Item Revision`. As such, select `TcConnector.ItemRevision`, then select the **Create new specialization of selected entity** checkbox. The entity is automatically named `RequirementRevision` after the Teamcenter Object name, but it can be renamed here if required. + Click **OK** to finish the object mapping and close the object mapping window. + +5. Once you close the object mapping window, the attributes and associations sidebar is displayed. From here, select the properties you want to have within your Mendix app. For this use case, you want `Name`, `Item ID`, and `Description` to be provided as attributes that can be modified when revising the `Item Revision`. As such, make sure to select the write option for these attributes. Since it is already selected, no further actions are required in the sidebar. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/revise-item-revision/property-mapping.png">}} + +6. Click the **Generate** button to generate the appropriate domain model and microflows. + Once the generation is complete, you are redirected to the **History** tab, which displays a summary of what has been generated. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/revise-item-revision/history.png">}} + +## Result {#result} + +The following sections describe the resulting domain model and microflows. + +### Domain Model {#domain-model} + +The extension generated the following entities in your domain model: + +* `ReviseRequirementRevision` – This is a helper entity that is used in the `RequirementRevision_ReviseItemRevision` microflow to revise a Requirement revision in Teamcenter. +* `RequirementRevision` – This is an entity representing Requirement Revisions from Teamcenter. It can be used to revise a new Requirement Revision in Teamcenter. + +### Microflows {#microflows} + +The extension generated the following microflows in your project: + +* `RequirementRevision_ReviseItemRevision` – This microflow implements the logic to revise an Item Revision in Teamcenter. diff --git a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/search-datasets.md b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/search-datasets.md new file mode 100644 index 00000000000..30642f33d9b --- /dev/null +++ b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/search-datasets.md @@ -0,0 +1,60 @@ +--- +title: "Search Datasets" +url: /appstore/modules/siemens-plm/teamcenter-extension/integrations/search-datasets/ +description: "Provides step by step guide to use the \"Search Datasets\" integration in Teamcenter Extension." +weight: 5 +--- + +## Introduction {#introduction} + +The **Search Datasets** integration allows you to generate the domain model and microflow to search for `Datasets` or its specialization in Teamcenter. The resulting microflow implements the Teamcenter out-of-the-box `Datasets` saved query. + +This document takes you through a use case of creating the logic to search datasets with the option of choosing different dataset types, such as PDF, MS Word etc. + +## Step-by-Step Guide {#step-by-step-guide} + +1. Make sure you have set up your credentials on the **Settings** tab before following these instructions. For more instructions on how to configure your settings, follow the steps in the [Settings Tab](/appstore/modules/siemens-plm/teamcenter-extension/create-an-integration/#settings-tab) section of *Teamcenter Extension*. + +2. Click the **Search Datasets** icon on the home page to start configuring your integration. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-datasets/icon.png">}} + +3. The [Import Mapping page](/refguide/import-mappings/) is displayed. This determines what data is retrieved from Teamcenter, and what type of objects are created in Mendix. Click one of the placeholder entities to start import mapping. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-datasets/import-mapping.png">}} + +4. In the object mapping window that opens, follow these steps: + + 1. The left side shows all Teamcenter Datasets retrieved from the Teamcenter instance. These can be out-of-the-box or custom. For this use case, you want to search the different types of Datasets, so select `Dataset`. + 2. The right side shows the relevant Mendix entities for which objects can be created when we retrieve Datasets from Teamcenter. You want to have an entity specifically for `Database`. As such, select `TcConnector.Dataset`, then select the **Create new specialization of selected entity** checkbox. The entity is automatically named `Dataset` after the Teamcenter Object name, but it can be renamed here if required. + Click **OK** to finish the object mapping and close the object mapping window. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-datasets/object-mapping.png">}} + +5. COnce you close the object mapping window, the attributes and associations sidebar is displayed. From here, select the properties you want to have within your Mendix app. For this use case, you do not need to add any additional properties, so no selections are necessary. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-datasets/property-mapping.png">}} + +6. Click the **Generate** button to generate the appropriate domain model and microflows. + Once the generation is complete, you are redirected to the **History** tab, which displays a summary of what has been generated. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-datasets/history.png">}} + +## Result {#result} + +The following sections describe the resulting domain model and microflows. + +### Domain Model {#domain-model} + +The extension generated the following entities in your domain model: + +* `Dataset` – This is an entity that represents a Dataset object from Teamcenter. This serves as an input in microflows that attach datasets. + +### Microflows {#microflows} + +The extension generated the following microflows in your project: + +* `Datatset_SavedQueryDataset` – This microflow implements the Teamcenter `Dataset` saved query. The microflow receives the following two input parameters: + + * `ConfigName` – This must be the `configName` of a `TcConnection.TeamcenterConfiguration` object. It determines which Teamcenter configuration will be used to connect to Teamcenter. If only one Teamcenter Configuration is used, the parameter can be left empty. + * `DatasetSearchCriteria` – This can be used as an input argument while searching for Datasets. + +* `Dataset_RetrieveFilesorImages` – This microflow implements the logic to retrieve files stored inside the Dataset. This is a helper microflow that can be used to retrieve files on the returned Dataset. +* `GetFileTypesForDatasetType` – This microflow implements the logic to retrieve all file types associated to a particular Dataset type. +* `GetAvailableDatasetTypes` – This microflow implements the logic to retrieve dataset types for your given Teamcenter instance. +* `Dataset_GetImanFiles` – This microflow implements the logic to retrieve the `ImanFile` object associated with an input dataset object. diff --git a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/search-item-revisions.md b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/search-item-revisions.md new file mode 100755 index 00000000000..e0f687355a2 --- /dev/null +++ b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/search-item-revisions.md @@ -0,0 +1,79 @@ +--- +title: "Search Item Revisions" +url: /appstore/modules/siemens-plm/teamcenter-extension/integrations/search-item-revisions/ +description: "Provides step by step guide to use \"Search Item Revisions\" integration in Teamcenter Extension." +weight: 1 +--- + +## Introduction {#introduction} + +The  **Search Item Revisions** integration allows you to generate the domain model and microflow to search for an `Item Revision` or its specialization. The resulting microflow implements the out of the box saved query `Item Revision...` from Teamcenter. + +This document takes you through a use case of retrieving Part Revisions from Teamcenter. Part Revisions are specific iterations of a part of a product that is managed using Teamcenter. A Part Revision contains essential information like the schematics of the Part. Since a Part Revision is a subtype of an Item Revision, it can be revised. + +## Step-by-Step guide {#step-by-step-guide} + +Follow these steps to create the integration: + +1. Make sure you have set up your credentials on the **Settings** tab before following these instructions. For more instructions on how to configure your settings, follow the steps in the [Settings Tab](/appstore/modules/siemens-plm/teamcenter-extension/create-an-integration/#settings-tab) section of *Teamcenter Extension*. + +2. Click the **Search Item Revision** button on the home page to start configuring your integration. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-item-revisions/icon.png">}} + +3. The [Import Mapping page](/refguide/import-mappings/) is displayed. This determines what data is retrieved from Teamcenter, and what type of objects are created in Mendix. +Click one of the placeholder entities to start the import mapping. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-item-revisions/import-mapping.png">}} + +4. In the object mapping window that opens, follow these steps: + + 1. The left side shows all Teamcenter objects retrieved from the Teamcenter instance. These can be out-of-the-box or custom. For this use case, select `Part Revision (Part Revision)`, which can be found under `Item Revision`. + 2. The right side shows the relevant Mendix entities for which objects can be created when retrieving Item Revisions from Teamcenter. For this use case, you want to have an entity specifically for `Part Revisions`, so you can make changes and add new attributes to it. As such, select `TcConnector.ItemRevision`, then select the **Create new Specialization of selected entity** checkbox. The entity is automatically named `PartRevision` after the Teamcenter Object name, but it can be renamed here if required. + Click **OK** to finish the object mapping and close the object mapping window. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-item-revisions/object-mapping.png">}} + +5. Once you close the object mapping window, the attributes and associations sidebar is displayed. From here, select the properties you want to have within your Mendix app. For this use case, you want to create an integration to retrieve additional Part Revision details. From the side panel, select the following attributes to add to the `Part Revision` entity: + + * `Finish Type` + * `Multi-body` + * `Safety Part` + * `Standard` + * `Spare Part` + * `Technology Intent` + + Once selected, click the backdrop or the close button to close the side panel. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-item-revisions/property-mapping.png">}} + +6. Click the **Generate** button to generate the appropriate domain model and microflows, so that you can start retrieving Part Revisions in your application. + Once the generation is complete, you are redirected to the **History** tab, which displays a summary of what has been generated. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-item-revisions/history.png">}} + +## Result {#result} + +The following sections describe the resulting domain model and microflows. + +### Domain Model {#domain-model} + +The extension generated the following entities in your domain model: + +* `PartRevision` – This entity represents a `PartRevision` from Teamcenter. The objects can be retrieved via `PartRevision_SavedQueryItemRevision`. + +### Microflows {#microflows} + +The extension generated the following microflows in your project: + +* `PartRevision_SavedQueryItemRevision` - This microflow can be used to retrieve a list of Part Revisions from Teamcenter. + The microflow receives the following two input parameters: + + * `ConfigName` – This must be the `configName` on a `TcConnection.TeamcenterConfiguration` object. + It determines which Teamcenter configuration will be used to connect to Teamcenter. If only one Teamcenter Configuration is used, the parameter can be left empty. + * `ItemRevisionSearchCriteria` – This is required and must be used as input argument while searching for Item Revisions. + For hints on how to efficiently use this parameter, refer to [Item Revision Search Criteria](#item-revision-search-criteria). + +The microflow returns a list of Part Revisions that matches the `SearchCriteria` provided in the `ItemRevisionSearchCriteria`. + +## Tips and Tricks {#tips-and-tricks} + +### Item Revision Search Criteria {#item-revision-search-criteria} + +* It is highly recommended to provide the `_Type` field, as it significantly optimizes the `ItemRevision_SavedQueryItemRevision` microflow. The `_type` field specifies which types of `ItemRevisions` will be requested. The field should be set to `PartRevision` to retrieve only `PartRevisions` and specializations of it. +* The `Name` and `ItemID` fields of the `ItemRevisionSearchCriteria` parameter support wildcards. For example, if `Name` is set to `a*`, all revisions whose name starts with an `a` are returned. \ No newline at end of file diff --git a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/update-item-with-item-revision.md b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/update-item-with-item-revision.md new file mode 100644 index 00000000000..de6d72401b9 --- /dev/null +++ b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/integrations/update-item-with-item-revision.md @@ -0,0 +1,59 @@ +--- +title: "Update Item with Item Revision" +url: /appstore/modules/siemens-plm/teamcenter-extension/integrations/update-item-with-item-revision/ +description: "Provides step by step guide to use the \"Update Item with Item Revision\" integration in Teamcenter Extension." +weight: 3 +--- + +## Introduction {#introduction} + +The **Update Item and Item Revision** integration allows you to generate the domain model and microflow to update an `Item` with `ItemRevision` or their specializations in Teamcenter. The resulting microflows implement the `Update Properties` action from the Teamcenter Connector. + +This document takes you through a use case of updating the properties, such as `description`, of `CAE 3D Analysis Revision Reports` in Teamcenter. `CAE 3D Analysis Revision` business objects are used to manage files associated from a 3D simulation study, such as CFD or Structural. + +## Step-by-Step Guide {#step-by-step-guide} + +1. Make sure you have set up your credentials on the **Settings** tab before following these instructions. For more instructions on how to configure your settings, follow the steps in the [Settings Tab](/appstore/modules/siemens-plm/teamcenter-extension/create-an-integration/#settings-tab) section of *Teamcenter Extension*. + +2. Click the **Update Item and Item Revision** button on the home page to start configuring your integration. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/icon.png">}} + +3. The [Import Mapping page](/refguide/import-mappings/) is displayed. This determines what data is retrieved from Teamcenter, and what type of objects are created in Mendix. Click one of the placeholder entities to start import mapping. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/import-mapping.png">}} + +4. In the object mapping window that opens, follow these steps: + + 1. The left side shows all Teamcenter objects retrieved from the Teamcenter instance. These can be out-of-the-box or custom. For this use case, you want to update `CAE 3D Analysis Revision`, so look for `CAE 3D Analysis`. + 2. The right side shows the Mendix entities that can serve as input parameters for the microflow to update an Item with Item Revision. If you create your own entity here, you can ensure that additional attributes are set in Teamcenter upon creation. As such, select `TcConnector.Item`, then select the **Create new specialization of selected entity** checkbox. The entity is automatically named `CAEAnalysis` after the Teamcenter Object name, but it can be renamed here if required. + Click **OK** to finish the object mapping and close the object mapping window. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/object-mapping.png">}} +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/object-mapping-result.png">}} + +5. For this use case, you also want to update `CAE 3D Analysis Revision`, so repeat this process to select `CAE 3D Analysis Revision` with another specialized entity. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/object-mapping-association.png">}} + +6. Double click any of the boxes to display the **Properties** window. You want to update the `description` attribute, which is already selected. As such, do not select any additional attributes. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/property-mapping.png">}} + +7. Click the **Generate** button to generate the appropriate domain model and microflows. + Once the generation is complete, you are redirected to the **History** tab, which displays a summary of what has been generated. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/history.png">}} + +## Result {#result} + +The following sections describe the resulting domain model and microflows. + +### Domain Model {#domain-model} + +The extension generated the following entities in your domain model: + +* `CAE3DAnalysis` – This is an entity representing a CAE 3D Analysis from Teamcenter. +* `CAE3DAnalysisRevision` – This is an entity representing a CAE 3D Analysis Revision from Teamcenter. +{{< figure src="/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/domain-model.png">}} + +### Microflows {#microflows} + +The extension generated the following microflows in your project: + +* `CAE3DAnalysis_UpdateItem` – This microflow implements the logic to update properties of CAE 3D Analysis. The microflow takes two input parameters: `CAE 3D Analysis` and `ConfigName`. It returns one output variable named `CAE3DAnalysis_Updated_Cast`. +* `CAE3DAnalysisRevision_UpdateItemRevision` – This microflow implements the logic to update properties of CAE 3D Analysis Revision. diff --git a/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/upgrading-teamcenter-extension.md b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/upgrading-teamcenter-extension.md new file mode 100644 index 00000000000..0d1d4ca9391 --- /dev/null +++ b/content/en/docs/marketplace/platform-supported-content/modules/siemens/teamcenter-extension/upgrading-teamcenter-extension.md @@ -0,0 +1,47 @@ +--- +title: "Upgrading Teamcenter Extension" +url: /appstore/modules/siemens-plm/teamcenter-extension/upgrading-teamcenter-extension/ +description: "Describes Teamcenter Extension from the Mendix Marketplace. Teamcenter Extension facilitates a low-code approach to integrating with Siemens Teamcenter." +weight: 3 +--- + +## Upgrading Teamcenter Extension V 1.0.0 to V 3.0.0 {#upgrade} + +{{% alert color="info" %}} To prevent conflicts (such as integration duplications), it is advised that one developer in a team upgrades the Teamcenter Extension and commits changes before other developers continue working with the extension.{{% /alert %}} + +If you use Teamcenter Extension V 1.0.0 with Teamcenter Connector V 3.6.1 or below, and want to upgrade to Teamcenter Extension V 3.0.0 and Teamcenter Connector V 2406.3.0, perform the following procedure: + +1. Open your app in a Studio Pro version compatible with Teamcenter Extension V 3.0.0 (see version matrix under [Dependencies](#dependencies) section) +2. Follow the instructions in [How to Use Marketplace Content in Studio Pro](/appstore/general/app-store-content/) to download [Teamcenter Extension V 3.0.0](https://marketplace.mendix.com/link/component/225544) from the Marketplace and install it. +3. When a warning dialog box opens, click **Trust module and enable extension**. Otherwise, Teamcenter Extension will not be installed. +4. Follow the instructions in [How to Upgrade the Module to a Newer Version](/appstore/use-content/#update-module) to upgrade Teamcenter Connector to V 2406.0.0. + + {{% alert color="info" %}}Teamcenter Connector V 2406.3.0 has an updated domain model that makes certain entities and associations in Teamcenter Extension V 1.0.0 redundant. As a result, you will get errors after the upgrade.{{% /alert %}} + +5. To resolve the errors, use one of the solutions described the sections below: + + * [Solution 1](#solution-1) – Delete and recreate microflows—using Solution 1 has the advantage that after completing the procedure, the integrations will appear on the **History** tab. + + * [Solution 2](#solution-2) – Update references and parameters. + +### Resolving the Errors – Solution 1 {#solution-1} + +{{% alert color="info" %}} +Using Solution 1 has an advantage: after completing the procedure, the integrations will appear on the **History** tab. +{{% /alert %}} + +Perform the following steps: + +1. Delete the microflows generated with Teamcenter Extension V 1.0.0. This will cause errors in the locations where these microflows were used. Keep these errors so that you can identify where the microflows need to be implemented again. +2. Go to Teamcenter Extension V 3.0.0 and repeat the steps you did before in Teamcenter Extension V 1.0.0. Simply select the same entities and associations, as they already exist in your domain model. +3. Go over the errors caused by the missing microflows and implement the newly-generated microflows.  + +### Resolving the Errors – Solution 2 {#solution-2} + +Follow the instructions in the table below: + +| Error message                                           | How to Solve the Error                                       | +| ------------------------------------------------------- | ------------------------------------------------------------ | +| `TeamcenterToolkit.BOMWindow` no longer exists          |
  1. Update all references to
    `TcConnector.BOMWindow`.
  2. Search for `TeamcenterToolkit.BOMWindow` to find `BOMapping` parameters where the entity is used, and change it to `TcConnector.BOMWindow`.
| +| `TeamcenterToolkit.top_line` no longer exists           | Update all associations to `TcConnector.top_line`.           | +| The selected Java action parameter […] no longer exists | Set all the Java action parameters again.                    | diff --git a/package-lock.json b/package-lock.json index 59f5c598cd8..86ce2c819d5 100644 --- a/package-lock.json +++ b/package-lock.json @@ -408,6 +408,7 @@ "url": "https://github.com/sponsors/ai" } ], + "peer": true, "dependencies": { "caniuse-lite": "^1.0.30001587", "electron-to-chromium": "^1.4.668", @@ -1759,6 +1760,7 @@ "url": "https://github.com/sponsors/ai" } ], + "peer": true, "dependencies": { "nanoid": "^3.3.7", "picocolors": "^1.0.0", diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/configure-dataset-attachment.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/configure-dataset-attachment.png new file mode 100644 index 00000000000..bf18ba2f257 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/configure-dataset-attachment.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/history.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/history.png new file mode 100644 index 00000000000..6b4c8988d5e Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/history.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/icon.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/icon.png new file mode 100644 index 00000000000..a2f63dc20a3 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/icon.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/import-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/import-mapping.png new file mode 100644 index 00000000000..1947b4e82d7 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/import-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/object-mapping-result.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/object-mapping-result.png new file mode 100644 index 00000000000..f98d84c21b8 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/object-mapping-result.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/object-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/object-mapping.png new file mode 100644 index 00000000000..87239960c38 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/object-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/property-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/property-mapping.png new file mode 100644 index 00000000000..71b2c6769c2 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/attach-dataset-to-item-revision/property-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/attribute-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/attribute-mapping.png new file mode 100644 index 00000000000..fe3bdafdc57 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/attribute-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/history.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/history.png new file mode 100644 index 00000000000..6f422b3124a Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/history.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/icon.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/icon.png new file mode 100644 index 00000000000..331a833f85f Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/icon.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/import-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/import-mapping.png new file mode 100644 index 00000000000..87b9f55ca7b Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/import-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/object-mapping-result.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/object-mapping-result.png new file mode 100644 index 00000000000..b1c9824f9f9 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/object-mapping-result.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/object-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/object-mapping.png new file mode 100644 index 00000000000..69db7b4adbd Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/object-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/property-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/property-mapping.png new file mode 100644 index 00000000000..cada5cf6c75 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/create-item-with-item-revision/property-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/history.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/history.png new file mode 100644 index 00000000000..0f5d3594bad Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/history.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/icon.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/icon.png new file mode 100644 index 00000000000..cfd799c6e5c Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/icon.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/import-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/import-mapping.png new file mode 100644 index 00000000000..ba50da4c40e Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/import-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/object-mapping-association-result.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/object-mapping-association-result.png new file mode 100644 index 00000000000..ed175733645 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/object-mapping-association-result.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/object-mapping-association.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/object-mapping-association.png new file mode 100644 index 00000000000..27e7e6627d8 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/object-mapping-association.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/object-mapping-result.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/object-mapping-result.png new file mode 100644 index 00000000000..0aba9cb0c16 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/object-mapping-result.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/object-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/object-mapping.png new file mode 100644 index 00000000000..fbfa4f4e0e0 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/object-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/property-mapping-association.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/property-mapping-association.png new file mode 100644 index 00000000000..b0ce4f09a8e Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/property-mapping-association.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/property-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/property-mapping.png new file mode 100644 index 00000000000..259dbc56701 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-datasets-for-item-revision/property-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-properties/history.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-properties/history.png new file mode 100644 index 00000000000..07556135201 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-properties/history.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-properties/icon.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-properties/icon.png new file mode 100644 index 00000000000..d3c04f0d69a Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-properties/icon.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-properties/import-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-properties/import-mapping.png new file mode 100644 index 00000000000..7085d9964ee Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-properties/import-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-properties/object-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-properties/object-mapping.png new file mode 100644 index 00000000000..330f2f56aeb Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-properties/object-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-properties/property-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-properties/property-mapping.png new file mode 100644 index 00000000000..69d05e3cb59 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-properties/property-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/history.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/history.png new file mode 100644 index 00000000000..cbc19dc5638 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/history.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/icon.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/icon.png new file mode 100644 index 00000000000..9016d7b3adc Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/icon.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/import-mapping-2.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/import-mapping-2.png new file mode 100644 index 00000000000..f739b65487e Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/import-mapping-2.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/import-mapping-empty.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/import-mapping-empty.png new file mode 100644 index 00000000000..0ee8bd0c133 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/import-mapping-empty.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/import-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/import-mapping.png new file mode 100644 index 00000000000..a6064463fae Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/import-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/object-mapping-2.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/object-mapping-2.png new file mode 100644 index 00000000000..5be552d6150 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/object-mapping-2.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/object-mapping-result.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/object-mapping-result.png new file mode 100644 index 00000000000..58082ea6b70 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/object-mapping-result.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/object-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/object-mapping.png new file mode 100644 index 00000000000..cc819f02031 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/get-structure/object-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/relate-workspace-objects/history.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/relate-workspace-objects/history.png new file mode 100644 index 00000000000..a25372460f7 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/relate-workspace-objects/history.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/relate-workspace-objects/icon.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/relate-workspace-objects/icon.png new file mode 100644 index 00000000000..8b8f411a578 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/relate-workspace-objects/icon.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/relate-workspace-objects/import-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/relate-workspace-objects/import-mapping.png new file mode 100644 index 00000000000..cabbe3e0b2a Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/relate-workspace-objects/import-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/relate-workspace-objects/object-mapping-association.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/relate-workspace-objects/object-mapping-association.png new file mode 100644 index 00000000000..4b580f28b24 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/relate-workspace-objects/object-mapping-association.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/relate-workspace-objects/object-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/relate-workspace-objects/object-mapping.png new file mode 100644 index 00000000000..1611b04dc54 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/relate-workspace-objects/object-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/relate-workspace-objects/property-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/relate-workspace-objects/property-mapping.png new file mode 100644 index 00000000000..08b2036e21d Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/relate-workspace-objects/property-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/revise-item-revision/history.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/revise-item-revision/history.png new file mode 100644 index 00000000000..71101543159 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/revise-item-revision/history.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/revise-item-revision/icon.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/revise-item-revision/icon.png new file mode 100644 index 00000000000..59fc2484ede Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/revise-item-revision/icon.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/revise-item-revision/import-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/revise-item-revision/import-mapping.png new file mode 100644 index 00000000000..0136e93232c Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/revise-item-revision/import-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/revise-item-revision/object-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/revise-item-revision/object-mapping.png new file mode 100644 index 00000000000..7fab47237b4 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/revise-item-revision/object-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/revise-item-revision/property-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/revise-item-revision/property-mapping.png new file mode 100644 index 00000000000..0467fca6982 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/revise-item-revision/property-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-datasets/history.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-datasets/history.png new file mode 100644 index 00000000000..1648f094be9 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-datasets/history.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-datasets/icon.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-datasets/icon.png new file mode 100644 index 00000000000..4e0100c8a35 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-datasets/icon.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-datasets/import-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-datasets/import-mapping.png new file mode 100644 index 00000000000..7c42dec95da Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-datasets/import-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-datasets/object-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-datasets/object-mapping.png new file mode 100644 index 00000000000..5bb3d92b007 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-datasets/object-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-datasets/property-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-datasets/property-mapping.png new file mode 100644 index 00000000000..3737ad2e50d Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-datasets/property-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-item-revisions/history.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-item-revisions/history.png new file mode 100644 index 00000000000..560205f0db6 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-item-revisions/history.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-item-revisions/icon.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-item-revisions/icon.png new file mode 100644 index 00000000000..8361be35004 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-item-revisions/icon.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-item-revisions/import-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-item-revisions/import-mapping.png new file mode 100644 index 00000000000..a7a9fc664bc Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-item-revisions/import-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-item-revisions/object-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-item-revisions/object-mapping.png new file mode 100644 index 00000000000..925d1f4ec98 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-item-revisions/object-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-item-revisions/property-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-item-revisions/property-mapping.png new file mode 100644 index 00000000000..e2c69d1b9ee Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-item-revisions/property-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-workspace-objects/history.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-workspace-objects/history.png new file mode 100644 index 00000000000..b36e9364552 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-workspace-objects/history.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-workspace-objects/icon.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-workspace-objects/icon.png new file mode 100644 index 00000000000..10fae9a260a Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-workspace-objects/icon.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-workspace-objects/import-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-workspace-objects/import-mapping.png new file mode 100644 index 00000000000..68d85631ad2 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-workspace-objects/import-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-workspace-objects/object-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-workspace-objects/object-mapping.png new file mode 100644 index 00000000000..e609aae12a3 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-workspace-objects/object-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-workspace-objects/property-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-workspace-objects/property-mapping.png new file mode 100644 index 00000000000..41f643cb73d Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/search-workspace-objects/property-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/domain-model.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/domain-model.png new file mode 100644 index 00000000000..05433750cf2 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/domain-model.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/history.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/history.png new file mode 100644 index 00000000000..2bbff6a3a04 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/history.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/icon.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/icon.png new file mode 100644 index 00000000000..3707761ac55 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/icon.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/import-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/import-mapping.png new file mode 100644 index 00000000000..49bbd879887 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/import-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/object-mapping-association.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/object-mapping-association.png new file mode 100644 index 00000000000..e8f5dcef212 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/object-mapping-association.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/object-mapping-result.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/object-mapping-result.png new file mode 100644 index 00000000000..f3764d8ec56 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/object-mapping-result.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/object-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/object-mapping.png new file mode 100644 index 00000000000..277a284a0e6 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/object-mapping.png differ diff --git a/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/property-mapping.png b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/property-mapping.png new file mode 100644 index 00000000000..167b91100f6 Binary files /dev/null and b/static/attachments/appstore/platform-supported-content/modules/siemens/teamcenter-extension/update-item-with-item-revision/property-mapping.png differ