From 06bfcc3bc782d1e997006a428fcbce0bf329b334 Mon Sep 17 00:00:00 2001
From: wanchoorohan <157635704+wanchoorohan@users.noreply.github.com>
Date: Wed, 22 Jul 2026 13:24:52 -0400
Subject: [PATCH 1/9] Add documentation for Teamcenter Connector 2606
Added documentation for Teamcenter Connector 2606, including an overview, architecture, and prerequisites.
---
.../1-overview-introduction | 67 +++++++++++++++++++
1 file changed, 67 insertions(+)
create mode 100644 content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/Unified Teamcenter Connector 2606/1-overview-introduction
diff --git a/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/Unified Teamcenter Connector 2606/1-overview-introduction b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/Unified Teamcenter Connector 2606/1-overview-introduction
new file mode 100644
index 00000000000..4eb2095828b
--- /dev/null
+++ b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/Unified Teamcenter Connector 2606/1-overview-introduction
@@ -0,0 +1,67 @@
+# Teamcenter Connector 2606 — Documentation Guide
+
+---
+
+## Overview & Introduction
+
+### What is Teamcenter Connector 2606?
+
+Teamcenter Connector 2606 marks a shift in how Mendix integrates with Teamcenter. For the first time, we're bringing together everything you need in a single, unified Marketplace module. This release combines what were previously two separate Marketplace downloads: Teamcenter Connector and the Teamcenter Extension (which itself contained two modules: Teamcenter Toolkit and the Extension add-on) into one streamlined package that works seamlessly with Mendix 11.12 and higher.
+
+Additionally, Teamcenter Extension has been re-built using the Web Extensibility Framework and is now available as a Teamcenter service document. You can think of a Teamcenter service document as a container that can be created on a per module basis which stores everything related to your Teamcenter integrations within a specific module.
+
+In previous versions, the Extension stored the Teamcenter integrations and configurations on disk (resources folder), separate from your Mendix app. This made version control tricky and team collaboration more complex. With the Teamcenter service document approach, everything is stored inside the Mendix model, just like microflows, pages, and domain models. This means:
+* Your integrations travel with your module when you export it or commit it to version control.
+* You can have different Teamcenter service documents for different purposes within the same app.
+* You can have different Teamcenter service documents for different Teamcenter instances, for example for test and production.
+
+### Architecture Overview
+
+Here's how all the pieces fit together:
+
+```
+Studio Pro (Mendix 11.12+)
+│
+├── Teamcenter service document ← stores integrations + connection settings
+│ └── Extension UI (TypeScript / Web Extensibility Framework)
+│ ├── Settings Tab
+│ ├── Integrations Tab
+│ ├── Integration Mapping Editor
+│ └── Integration Configuration Dialogs
+│
+├── Generated Artifacts (per module)
+│ ├── Domain Model (entities, associations, specializations)
+│ └── Microflows (search, create, update, revise, get, relate, BOM)
+│
+└── TcConnector module (runtime — includes former Toolkit)
+ ├── Published Microflows (Toolbox) [Published — Teamcenter icon]
+ ├── Java Actions (Toolbox) [Published — Teamcenter icon]
+ ├── Internal Actions [Private — no icon]
+ ├── TcConnector Domain Model (base entities, BOMLine, search criteria)
+ ├── CallTeamcenterService (custom SOA calls)
+ └── Authentication (Credentials / TcSSO / TcX SSO)
+ │
+ ▼
+ Teamcenter SOA Layer
+ (self-hosted v2506+ / Teamcenter X v2506+)
+```
+
+### How it works in practice
+
+1. You start by creating a Teamcenter service document, where you configure your Teamcener connection and create integrations.
+2. The Teamcenter service document generates domain model entities and microflows specific to your integration needs, placing them directly in your module.
+3. The generated microflows make use of predefined Teamcenter connector microflows for the integration with Teamcenter, using the TcConnector Java Actions to call Teamcenter's SOA layer
+
+### Prerequisites and Compatibility
+
+Before you start working with Teamcenter Connector 2606, make sure your environment meets these requirements:
+
+| Requirement | Minimum version |
+|---|---|
+| Mendix Studio Pro | 11.12.1 |
+| Teamcenter (self-hosted) | 2606, 2512, 2506 |
+| Teamcenter X | 2606, 2512, 2506 |
+
+#### Required Marketplace modules
+* Community Commons
+* Encryption
From d5370686fb23766e8c41714b1e220084ac43be59 Mon Sep 17 00:00:00 2001
From: wanchoorohan <157635704+wanchoorohan@users.noreply.github.com>
Date: Wed, 22 Jul 2026 13:33:15 -0400
Subject: [PATCH 2/9] Add getting started guide for Teamcenter Connector 2606
Added a comprehensive guide for getting started with the Teamcenter Connector 2606, including installation, setup, and integration steps.
---
.../2-getting-started.md | 129 ++++++++++++++++++
1 file changed, 129 insertions(+)
create mode 100644 content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/Unified Teamcenter Connector 2606/2-getting-started.md
diff --git a/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/Unified Teamcenter Connector 2606/2-getting-started.md b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/Unified Teamcenter Connector 2606/2-getting-started.md
new file mode 100644
index 00000000000..34743b49fa7
--- /dev/null
+++ b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/Unified Teamcenter Connector 2606/2-getting-started.md
@@ -0,0 +1,129 @@
+## Getting Started
+
+### Installation and Setup
+
+1. **Download and import the module**
+* Open Mendix Studio Pro 11.12, and go to the Marketplace tab. Download Teamcenter Connector 2606. Remember: you don't need to download Teamcenter Extension separately since its already included.
+* Alternatively, you can download Teamcenter Connector 2606 from the Mendix Marketplace and import it into your Mendix 11.12 project.
+
+2. **Add required dependencies**
+* Make sure your app includes Community Commons and the Encryption module. These are both available from the Marketplace.
+
+3. **Configure security**
+* Assign the `TcConnector.User` role to the relevant user roles in your app's security settings. **Important**: The Administrator role now only has access to `TcConnector.TeamcenterConfiguration`. For all integration work, use the User role.
+* Click "Update Security" in Studio Pro to refresh entity access rules.
+
+4. **Enable React client**
+- Make sure the React client is enabled in your app settings (Project → Settings → Runtime). This is required for the Teamcenter service document to work properly.
+
+---
+
+### What a Teamcenter service document contains
+
+1. **Settings**
+ * This is where you configure the connection to your Teamcenter instance. This is required so the Teamcenter service document can communicate with Teamcenter to retrieve business objects and properties so you can build artifacts as per your use case.
+ * Set up your authentication method, test the connection, and manage sign-in state.
+ * You typically configure this once per Teamcenter service document, unless you need to switch environments.
+
+
+
+2. **Integrations**
+ * It shows an overview of all the integrations you've configured in this document.
+ * You can see the Teamcenter integration type, the entities and microflows that were generated, and when each integration was last modified.
+ * From here, you can:
+ * View details of an integration.
+ * Edit an existing integration.
+ * Duplicate an integration (useful for creating variations).
+ * Delete integrations you no longer need.
+ * Navigate directly to the generated microflows and entities by double-clicking on them.
+ * This is also where you can add new integrations.
+
+
+
+---
+
+**You can have multiple Teamcenter service documents**
+You can create several Teamcenter service documents in a single app, each in its own module. This is useful for separating concerns. For example:
+* A "Parts" module with a Teamcenter service document for part-related integrations.
+* A "Workflows" module with a Teamcenter service document for workflow-related integrations.
+* A "Documents" module with a Teamcenter service document for dataset and document integrations.
+
+---
+
+### Create and build your first Teamcenter service document
+
+#### 1. Create a Teamcenter service document
+* In the App Explorer, right-click on the module where you want to create your integrations.
+* Select "Add other" → "Teamcenter service".
+* Give it a name (e.g., "PartsIntegrations" or "MainTeamcenterConnection").
+
+#### 2. Open the Settings tab
+* Navigate to the Settings tab of the Teamcenter service document (it's one of the tabs at the top of the document)
+
+#### 3. Configure your connection
+* In the Settings tab, provide your Teamcenter authentication option along with credentials. Please refer to the [old Teamcenter Extension](https://docs.mendix.com/appstore/modules/siemens-plm/teamcenter-extension/create-an-integration/#settings-tab) settings page for more details.
+
+#### 4. Test your connection
+* Once you've entered your connection details, click the "Sign In" button to test the connection.
+
+>[!NOTE] Important note about auto-logout
+The Teamcenter service document automatically clears your sign-in state when you edit or reset connection details. This is a security feature to ensure you're always using the correct credentials with the correct Teamcenter environment.
+
+#### 5. **Add your first Teamcenter integration**
+* Click on the "Integrations" tab at the top. Right now, it's empty—this is normal for a new Teamcenter service document.
+* Click on "Add integration".
+* You'll see tiles representing all available integration types (like "Search Item Revisions," "Create Item with Item Revision," etc.).
+* Click on one of these tiles to start configuring that type of integration.
+* This will take you to the Import Mapping page.
+
+#### 6. **Use the Import Mapping Mapping Page**
+Double-click on any one of the boxes to open the object mapping dialog.
+
+
+
+**Teamcenter side (left)**
+* Browse the Teamcenter object hierarchy.
+* Select the business object type you want to work with (for example, "Item Revision" or "Dataset").
+
+**Mendix side (right)**
+* Choose whether to create a new entity or use an existing one.
+ * If creating new, the Teamcenter service will generate an entity that is a specialization of the selected entity.
+ * If using existing, you can select an entity you've already defined in your domain model.
+* When you're done, choose the **Select** button at the bottom to proceed.
+
+**Mapping additional properties**
+* Once you've selected the Teamcenter object type and Mendix entity, you can add additional properties/references/relations to the list of default selected properties.
+* Double-click on the entity or select an entity and click Select Elements at the top.
+* Use the checkboxes to indicate:
+ * "Read" — should this property be retrieved from Teamcenter?
+ * "Write" — should this property be sent to Teamcenter when creating or updating (note the write checkboxes are only available in integrations where you can write data to Teamcenter).
+* Select the properties you need for your integration.
+
+
+
+**Teamcenter integration-specific panels**
+* Depending on the integration type, you'll be presented with additional configuration dialog.
+* For example:
+ * Dataset integrations let you filter by dataset type.
+ * BOM integrations let you configure BOM window properties and revision rules.
+* Configure these integration-specific settings as needed.
+* For more information on each of the Teamcenter integrations, refer to [integration guides](https://docs.mendix.com/appstore/modules/siemens-plm/teamcenter-extension/create-an-integration/integrations/).
+
+#### 7. **Generate your integration**
+* Once you've configured everything, click the "Generate" button.
+* The Teamcenter service document will:
+ * Validate your integration to make sure everything is correct.
+ * Generate domain model entities (placed in your domain model as a tree for easy visualization).
+ * Generate microflows that implement the integration logic.
+ * Save the integration to the Teamcenter service document
+ * Navigate to the Integrations tab where the integration is now listed
+
+#### 8. **Explore the results**
+* After generation completes, you'll automatically return to the Integrations tab.
+* Find your newly created integration in the list.
+* You'll see links to:
+ * The generated microflows (double-click to jump directly to them in Studio Pro).
+ * The generated entities (double-click to jump directly to the Domain model).
+* Double click on a microflow name for Studio to open that microflow, and you can see exactly what was generated.
+
+
From 798a07a176814f4314de6a2d7a9285affc95530c Mon Sep 17 00:00:00 2001
From: wanchoorohan <157635704+wanchoorohan@users.noreply.github.com>
Date: Wed, 22 Jul 2026 13:33:48 -0400
Subject: [PATCH 3/9] Add migration guide for Teamcenter Connector 2606
Added a comprehensive migration guide for upgrading to Teamcenter Connector 2606, including pre-migration checklist, step-by-step process, breaking changes, and deprecated microflows and Java actions.
---
.../3-migrate-to-2606.md | 147 ++++++++++++++++++
1 file changed, 147 insertions(+)
create mode 100644 content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/Unified Teamcenter Connector 2606/3-migrate-to-2606.md
diff --git a/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/Unified Teamcenter Connector 2606/3-migrate-to-2606.md b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/Unified Teamcenter Connector 2606/3-migrate-to-2606.md
new file mode 100644
index 00000000000..1493b575df5
--- /dev/null
+++ b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/Unified Teamcenter Connector 2606/3-migrate-to-2606.md
@@ -0,0 +1,147 @@
+
+## Migrating to 2606
+
+### Migrating from Teamcenter Connector 2512 and Extension v4.x
+
+In version 2606 of the Teamcenter Connector contains both the TcConnector module and the extension, meaning that from this version onwards the Teamcenter Extension doesn't need to be downloaded seperately. If you have an existing app using Teamcenter Connector 2512 and Extension v4.x, you can migrate to version 2606. While this migration involves some breaking changes, the benefits—unified module, modern Extension framework, improved security, and better error handling—make it worthwhile.
+
+**Before you start: Pre-migration checklist**
+
+⚠️ **Follow these steps carefully to avoid issues:**
+
+1. **Upgrade to Mendix 11.12.1 or higher first** — Version 2606 requires Mendix 11.12.1+. If you're on Mendix 10, you must upgrade Studio Pro before importing the new connector. Mendix 10 cannot run 2606.
+
+2. **Have only one developer perform the migration** — If multiple developers migrate simultaneously, you'll end up with duplicate generated artifacts. Coordinate with your team and designate one person to handle the migration, then have others pull the updated code from version control.
+
+3. **Migrate from 2512** - If the project still contains an older version of the Teamcenter Connector (2506 or older) first follow the steps in: https://docs.mendix.com/appstore/modules/siemens-plm/upgrade-teamcenter-connector-2506-to-2512/
+
+4. **Make a backup** — Before starting, either create a full backup of your app or commit all current changes to version control. This gives you a safety net in case you need to roll back.
+
+**Step-by-step migration process**
+
+**Step 1: Prepare your environment**
+
+1. Open your app in Studio Pro 11.12.1 or higher
+2. Make sure all changes are committed (if using version control) or backed up
+
+**Step 2: Move the Toolkit contents to the TcConnector module**
+
+3. Remove the old TcConnector module from your project, ignore the errors for now
+4. Rename the old TeamcenterToolkit module to TcConnector, then remove the module. By doing this, the old Toolkit references in the project are now pointing to the TcConnector module.
+> [!NOTE]
+> This step doesn't change the BOMapping, we will fix this in a later step
+
+**Step 3: Import the new connector**
+
+5. Remove the TeamcenterExtension module under add-ons, the old extension is not compatible with the new Teamcenter Connector 2606 module
+6. Download the Teamcenter Connector 2606 from the Mendix Marketplace, this now also contains the new version of the extension
+> [!NOTE]
+> The Teamcenter Extension is not found anymore under Extensions, but it can now be found as a new Service Document, similar as a microflow, it can be found by: Right click > Add other > Teamcenter service__
+
+**Step 4: Resolve breaking changes**
+
+7. Studio Pro will show you errors where your microflows or domain model reference things that have changed. Work through these systematically. The most common issues you'll encounter:
+ - Errors in microflows that were generated by the Teamcenter Extension can best be re-created by the new version of the extension, see Step 9
+ - Missing microflows/Java actions can be found in the deprecated table below
+ - References to `TeamcenterToolkit.*` — Change these to `TcConnector.*` (because Toolkit was merged into TcConnector)
+ - References to `FileType` — Change these to `NamedReference`
+ - Microflows that handle the Boolean return value from `Login` — Remove this handling, as `Login` now throws an exception instead
+ - See the breaking changes reference below
+
+**Step 5: Update security**
+
+8. Click "Update Security" in Studio Pro (open domain model → Update Security), make sure that all atrributes on persistent entities have read-rights
+9. Remember: the Administrator role now only has access to Teamcenter Configuration, so assign the User role to module roles that need entity access
+
+**Step 6: Enable React client**
+
+10. Go to Project → Settings → Runtime
+11. Make sure "Use React client" is turned on
+
+**Step 7: Create a Teamcenter Service Document**
+
+12. In the module where your Teamcenter integrations live, right-click and select "Add others" → "Teamcenter Service"
+13. Give it a name (e.g., "MainIntegrations")
+
+**Step 8: Reconfigure your connection**
+
+14. Open the Teamcenter Service Document and go to the Settings tab
+15. Enter your Teamcenter URL and authentication settings
+16. Click "Sign In" and login to Teamcenter
+
+**Step 9: Recreate your integrations**
+
+17. Your existing domain model entities and microflows are still in your app—they haven't been deleted. However, you'll want to regenerate them using the new Extension to take advantage of improvements and ensure they're compatible with the new connector
+18. In the Service Document, click on '+ Add integration' and start a journey that matches each of your existing integrations
+19. Configure it the same way as before (the journey types and options are the same)
+20. Click "Generate" to save and generate the integration
+21. Replace the old microflows with the new generated microflows
+22. You can use the "Duplicate" feature in the History tab to create variations of an integration without reconfiguring from scratch
+
+**Step 10: Test thoroughly**
+
+23. Run each generated microflow against your Teamcenter instance
+24. Verify that search, create, update, and retrieval operations work as expected
+25. Test error handling by triggering error conditions (e.g., invalid search criteria)
+26. If you have automated tests, run them to ensure integration behavior is correct
+
+**Breaking changes reference**
+
+Here's a comprehensive table of breaking changes and what you need to do about each one:
+
+| Area | Change | Action required |
+|---|---|---|
+| **Teamcenter Toolkit Module** | Module merged into TcConnector; module no longer exists | Update all references from `TeamcenterToolkit.*` to `TcConnector.*` |
+| **Entity security** | Create and Delete rights removed from all entities | Remove any UI or microflow logic that relied on client-side Create/Delete; use microflows instead |
+| **Input parameter `ConfigName` renamed to `ConfigurationName`** | in generated microflows the input parameter is now called ConfigurationName and is optional | Set the ConfigurationName or leave it empty |
+| **Admin role** | Administrator no longer has entity access | Reassign to User role where needed |
+| **`FileType` / `File Type`** | Renamed to `NamedReference` / `Named Reference` | Update all references in microflows and mappings |
+| **`CreateBOMWindow_Generic`** | Moved to TcConnector; updated to use `CreateOrReconfigureBOMWindows`; pre-configured variants removed | Regenerate BOM microflows via the Extension or update manually to use `TcConnector.CreateBOMWindow_Generic` |
+| **`Login` Java action** | No longer returns Boolean; throws exception on failure | Remove Boolean result handling; wrap in error handler |
+| **`Logout` Java action** | Now returns Boolean | Update callers if return value was previously ignored |
+| **Error messages** | Connector no longer shows in-app messages; throws exceptions instead | Ensure calling microflows have error handlers |
+
+**Deprecated microflows — with replacements**
+
+These microflows still exist in the deprecated folder but can't be used anymore (excluded). Replace them with the recommended alternatives:
+
+| Deprecated | Replacement |
+|---|---|
+| `AreMultipleTcConfigActive` | No replacement |
+| `CloseBOMWindow`| `BOMWindow_Close` |
+| `DownloadFile` | `DownloadFile` / `DownloadImage` Java action |
+| `ExecuteLogin` | `Login` microflow |
+| `ExecuteLogout` | `Logout` microflow |
+| `HandleActiveConfigErrors` | No replacement |
+| `HandleServiceErrors` | No replacement |
+| `RetrieveConfigNameFromSingleActiveConfiguration` | Use `empty` for configurationName parameter in Java actions, Java actions now handles active configuration in the Java code |
+| `RetrieveHttpHeaderList` | No replacement |
+| `RetrieveTcSessionBasedOnConfigName` | No replacement, TcSession should not be manually consumed; it is automatically handled by the TcConnector module. |
+| `RetrieveTeamcenterConifgurationByName` | Use `empty` for configurationName parameter in Java actions, Java actions now handles active configuration in the Java code |
+| `RetrieveTeamcenterConifgurationFromTcSession` | No replacement TcSession should not be manually consumed; it is automatically handled by the TcConnector module |
+| `ShowPartialErrors` | No replacement |
+| `UpdateSession` | No replacement |
+
+**Deprecated Java actions — with replacements**
+
+These Java actions still exist in the deprecated folder but can't be used anymore (excluded). Replace them with the recommended alternatives:
+
+|Java Action | Replacement |
+|---|---|
+| `PerformAction` | `PerformAction3` |
+| `GetWorkflowTemplates` | `GetWorkflowTemplates2` |
+| `CreateBOMWindows` | `CreateOrReConfigureBOMWindows` |
+| `CreateBOMWindows2` | `CreateOrReConfigureBOMWindows` |
+| `WhereUsed` | `WhereUsed2` |
+| `ExpandPSOneLevel` | `ExpandPSOneLevel2` |
+| `GetTcSessionInfo` | `GetTcSessionInformation` |
+| `GetItemFromId` | `GetItemAndRelatedObjects` |
+| `RetrieveCookie` | No replacement |
+
+**What carries forward automatically**
+
+The good news: not everything needs to be rebuilt from scratch.
+
+✅ **Your domain model is preserved** — Entities and associations generated by the previous Extension remain in your module. They're part of your app, so they don't disappear during the migration.
+
+✅ **Your microflows are preserved** — Generated microflows remain in your app. Only those affected by specific breaking changes (input entity naming, Toolkit module references) need regeneration or updates.
From cd3ee68e197cd5044d90274bc848bef670337021 Mon Sep 17 00:00:00 2001
From: nicoletacoman
Date: Thu, 23 Jul 2026 11:19:57 +0200
Subject: [PATCH 4/9] Added metadata and created architecture
---
.../2506-configuration/_index.md | 4 +--
.../configuring-connection.md | 2 +-
.../2506-configuration/teamcenterx.md | 2 +-
.../upgrading-2506-to-2512.md | 2 +-
...uration-guide.md => 2512-configuration.md} | 4 +--
.../_index.md} | 21 +++++++-----
.../getting-started.md} | 33 ++++++++++---------
.../migrate-to-2606.md} | 8 +++--
8 files changed, 43 insertions(+), 33 deletions(-)
rename content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/{ => 2506-configuration}/upgrading-2506-to-2512.md (99%)
rename content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/{teamcenter-configuration-guide.md => 2512-configuration.md} (99%)
rename content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/{Unified Teamcenter Connector 2606/1-overview-introduction => 2606-configuration/_index.md} (91%)
rename content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/{Unified Teamcenter Connector 2606/2-getting-started.md => 2606-configuration/getting-started.md} (89%)
rename content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/{Unified Teamcenter Connector 2606/3-migrate-to-2606.md => 2606-configuration/migrate-to-2606.md} (96%)
diff --git a/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2506-configuration/_index.md b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2506-configuration/_index.md
index 46f2f4ee8d0..43a6a3aff40 100644
--- a/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2506-configuration/_index.md
+++ b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2506-configuration/_index.md
@@ -1,8 +1,8 @@
---
title: "Configuring the Connection to Teamcenter with Teamcenter Connector 2506.0.0 and Below"
-linktitle: "Connecting with Teamcenter Connector 2506.0.0 and Below"
+linktitle: "Teamcenter Connector 2506.0.0 and Below"
url: /appstore/modules/siemens-plm/configuring-connection-2506/
-weight: 3
+weight: 4
description: "Describes the steps to configure the connection to your Teamcenter instance using Teamcenter Connector 2506.0.0 and below."
---
diff --git a/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2506-configuration/configuring-connection.md b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2506-configuration/configuring-connection.md
index 469c9415b57..5503998a609 100644
--- a/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2506-configuration/configuring-connection.md
+++ b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2506-configuration/configuring-connection.md
@@ -1,7 +1,7 @@
---
title: "Configuring the Connection to Teamcenter"
url: /appstore/modules/siemens-plm/configuring-connection/
-weight: 4
+weight: 10
description: "Describes the connection configuration steps for Teamcenter."
---
diff --git a/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2506-configuration/teamcenterx.md b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2506-configuration/teamcenterx.md
index e7ab17b4cb0..0af704a5d14 100644
--- a/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2506-configuration/teamcenterx.md
+++ b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2506-configuration/teamcenterx.md
@@ -1,7 +1,7 @@
---
title: "Configuring the Connection to Teamcenter X"
url: /appstore/modules/siemens-plm/teamcenterx/
-weight: 5
+weight: 20
description: "Describes the steps to connect to Teamcenter X."
---
diff --git a/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/upgrading-2506-to-2512.md b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2506-configuration/upgrading-2506-to-2512.md
similarity index 99%
rename from content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/upgrading-2506-to-2512.md
rename to content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2506-configuration/upgrading-2506-to-2512.md
index 80b1babf205..ac18c970be3 100644
--- a/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/upgrading-2506-to-2512.md
+++ b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2506-configuration/upgrading-2506-to-2512.md
@@ -1,7 +1,7 @@
---
title: "Upgrading Teamcenter Connector 2506.0.0 to 2512.0.0"
url: /appstore/industry/teamcenter-connector/upgrade-teamcenter-connector-2506-to-2512/
-weight: 4
+weight: 30
description: "Describes the steps to upgrade Teamcenter Connector 2506.0.0 to 2512.0.0 and discusses how breaking changes can be resolved."
aliases:
- /appstore/modules/siemens-plm/upgrade-teamcenter-connector-2506-to-2512/
diff --git a/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/teamcenter-configuration-guide.md b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2512-configuration.md
similarity index 99%
rename from content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/teamcenter-configuration-guide.md
rename to content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2512-configuration.md
index 18f4ed60b55..0b3f7322022 100644
--- a/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/teamcenter-configuration-guide.md
+++ b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2512-configuration.md
@@ -1,8 +1,8 @@
---
title: "Configuring the Connection to Teamcenter with Teamcenter Connector 2512.0.0 and Above"
-linktitle: "Connecting with Teamcenter Connector 2512.0.0 and Above"
+linktitle: "Teamcenter Connector 2512.0.0 and Above"
url: /appstore/industry/teamcenter-connector/configuring-connection-2512/
-weight: 2
+weight: 3
description: "Describes the steps to configure the connection to your Teamcenter instance using Teamcenter Connector 2512.0.0 and above."
aliases:
- /appstore/modules/siemens-plm/configuring-connection-2512/
diff --git a/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/Unified Teamcenter Connector 2606/1-overview-introduction b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2606-configuration/_index.md
similarity index 91%
rename from content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/Unified Teamcenter Connector 2606/1-overview-introduction
rename to content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2606-configuration/_index.md
index 4eb2095828b..b297bd036b3 100644
--- a/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/Unified Teamcenter Connector 2606/1-overview-introduction
+++ b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2606-configuration/_index.md
@@ -1,21 +1,23 @@
-# Teamcenter Connector 2606 — Documentation Guide
-
+---
+title: "Teamcenter Connector 2606"
+url: /appstore/industry/teamcenter-connector/teamcenter-connector-2606/
+weight: 2
+description: "Describes the unified Teamcenter Connector 2606."
---
-## Overview & Introduction
-
-### What is Teamcenter Connector 2606?
+## Introduction
Teamcenter Connector 2606 marks a shift in how Mendix integrates with Teamcenter. For the first time, we're bringing together everything you need in a single, unified Marketplace module. This release combines what were previously two separate Marketplace downloads: Teamcenter Connector and the Teamcenter Extension (which itself contained two modules: Teamcenter Toolkit and the Extension add-on) into one streamlined package that works seamlessly with Mendix 11.12 and higher.
Additionally, Teamcenter Extension has been re-built using the Web Extensibility Framework and is now available as a Teamcenter service document. You can think of a Teamcenter service document as a container that can be created on a per module basis which stores everything related to your Teamcenter integrations within a specific module.
In previous versions, the Extension stored the Teamcenter integrations and configurations on disk (resources folder), separate from your Mendix app. This made version control tricky and team collaboration more complex. With the Teamcenter service document approach, everything is stored inside the Mendix model, just like microflows, pages, and domain models. This means:
+
* Your integrations travel with your module when you export it or commit it to version control.
* You can have different Teamcenter service documents for different purposes within the same app.
* You can have different Teamcenter service documents for different Teamcenter instances, for example for test and production.
-### Architecture Overview
+## Architecture Overview
Here's how all the pieces fit together:
@@ -46,13 +48,13 @@ Studio Pro (Mendix 11.12+)
(self-hosted v2506+ / Teamcenter X v2506+)
```
-### How it works in practice
+## How it works in practice
1. You start by creating a Teamcenter service document, where you configure your Teamcener connection and create integrations.
2. The Teamcenter service document generates domain model entities and microflows specific to your integration needs, placing them directly in your module.
3. The generated microflows make use of predefined Teamcenter connector microflows for the integration with Teamcenter, using the TcConnector Java Actions to call Teamcenter's SOA layer
-### Prerequisites and Compatibility
+## Prerequisites and Compatibility
Before you start working with Teamcenter Connector 2606, make sure your environment meets these requirements:
@@ -62,6 +64,7 @@ Before you start working with Teamcenter Connector 2606, make sure your environm
| Teamcenter (self-hosted) | 2606, 2512, 2506 |
| Teamcenter X | 2606, 2512, 2506 |
-#### Required Marketplace modules
+### Required Marketplace modules
+
* Community Commons
* Encryption
diff --git a/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/Unified Teamcenter Connector 2606/2-getting-started.md b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2606-configuration/getting-started.md
similarity index 89%
rename from content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/Unified Teamcenter Connector 2606/2-getting-started.md
rename to content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2606-configuration/getting-started.md
index 34743b49fa7..8007f739d65 100644
--- a/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/Unified Teamcenter Connector 2606/2-getting-started.md
+++ b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2606-configuration/getting-started.md
@@ -1,6 +1,12 @@
-## Getting Started
+---
+title: "Getting Started with Teamcenter Connector 2606"
+linktitle: "Getting Started"
+url: /appstore/industry/teamcenter-connector/teamcenter-connector-2606-getting-started/
+weight: 10
+description: "Describes how to install, configure, and build your first Teamcenter Connector 2606 integration in Mendix Studio Pro, including setup, security, connection settings, and generating microflows and entities from a Teamcenter service document."
+---
-### Installation and Setup
+## Installation and Setup
1. **Download and import the module**
* Open Mendix Studio Pro 11.12, and go to the Marketplace tab. Download Teamcenter Connector 2606. Remember: you don't need to download Teamcenter Extension separately since its already included.
@@ -16,9 +22,7 @@
4. **Enable React client**
- Make sure the React client is enabled in your app settings (Project → Settings → Runtime). This is required for the Teamcenter service document to work properly.
----
-
-### What a Teamcenter service document contains
+## What a Teamcenter service document contains
1. **Settings**
* This is where you configure the connection to your Teamcenter instance. This is required so the Teamcenter service document can communicate with Teamcenter to retrieve business objects and properties so you can build artifacts as per your use case.
@@ -48,35 +52,34 @@ You can create several Teamcenter service documents in a single app, each in its
* A "Workflows" module with a Teamcenter service document for workflow-related integrations.
* A "Documents" module with a Teamcenter service document for dataset and document integrations.
----
-### Create and build your first Teamcenter service document
+## Create and build your first Teamcenter service document
-#### 1. Create a Teamcenter service document
+### 1. Create a Teamcenter service document
* In the App Explorer, right-click on the module where you want to create your integrations.
* Select "Add other" → "Teamcenter service".
* Give it a name (e.g., "PartsIntegrations" or "MainTeamcenterConnection").
-#### 2. Open the Settings tab
+### 2. Open the Settings tab
* Navigate to the Settings tab of the Teamcenter service document (it's one of the tabs at the top of the document)
-#### 3. Configure your connection
+### 3. Configure your connection
* In the Settings tab, provide your Teamcenter authentication option along with credentials. Please refer to the [old Teamcenter Extension](https://docs.mendix.com/appstore/modules/siemens-plm/teamcenter-extension/create-an-integration/#settings-tab) settings page for more details.
-#### 4. Test your connection
+### 4. Test your connection
* Once you've entered your connection details, click the "Sign In" button to test the connection.
>[!NOTE] Important note about auto-logout
The Teamcenter service document automatically clears your sign-in state when you edit or reset connection details. This is a security feature to ensure you're always using the correct credentials with the correct Teamcenter environment.
-#### 5. **Add your first Teamcenter integration**
+### 5. **Add your first Teamcenter integration**
* Click on the "Integrations" tab at the top. Right now, it's empty—this is normal for a new Teamcenter service document.
* Click on "Add integration".
* You'll see tiles representing all available integration types (like "Search Item Revisions," "Create Item with Item Revision," etc.).
* Click on one of these tiles to start configuring that type of integration.
* This will take you to the Import Mapping page.
-#### 6. **Use the Import Mapping Mapping Page**
+### 6. **Use the Import Mapping Mapping Page**
Double-click on any one of the boxes to open the object mapping dialog.
@@ -109,7 +112,7 @@ Double-click on any one of the boxes to open the object mapping dialog.
* Configure these integration-specific settings as needed.
* For more information on each of the Teamcenter integrations, refer to [integration guides](https://docs.mendix.com/appstore/modules/siemens-plm/teamcenter-extension/create-an-integration/integrations/).
-#### 7. **Generate your integration**
+### 7. **Generate your integration**
* Once you've configured everything, click the "Generate" button.
* The Teamcenter service document will:
* Validate your integration to make sure everything is correct.
@@ -118,7 +121,7 @@ Double-click on any one of the boxes to open the object mapping dialog.
* Save the integration to the Teamcenter service document
* Navigate to the Integrations tab where the integration is now listed
-#### 8. **Explore the results**
+### 8. **Explore the results**
* After generation completes, you'll automatically return to the Integrations tab.
* Find your newly created integration in the list.
* You'll see links to:
diff --git a/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/Unified Teamcenter Connector 2606/3-migrate-to-2606.md b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2606-configuration/migrate-to-2606.md
similarity index 96%
rename from content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/Unified Teamcenter Connector 2606/3-migrate-to-2606.md
rename to content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2606-configuration/migrate-to-2606.md
index 1493b575df5..f5cdce5e6ee 100644
--- a/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/Unified Teamcenter Connector 2606/3-migrate-to-2606.md
+++ b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2606-configuration/migrate-to-2606.md
@@ -1,5 +1,9 @@
-
-## Migrating to 2606
+---
+title: "Migrating to Teamcenter Connector 2606"
+url: /appstore/industry/teamcenter-connector/migrating-to-teamcenter-connector-2606/
+weight: 20
+description: "Describes how to migrate an existing app from Teamcenter Connector 2512 and Extension v4.x to Teamcenter Connector 2606, including pre-migration steps, breaking changes, deprecated microflows and Java actions."
+---
### Migrating from Teamcenter Connector 2512 and Extension v4.x
From 6a0cbf63a6dfbe276a435e08bcb1faa6fee012b6 Mon Sep 17 00:00:00 2001
From: nicoletacoman
Date: Thu, 23 Jul 2026 16:54:35 +0200
Subject: [PATCH 5/9] TW review
---
.../2606-configuration/_index.md | 36 +--
.../2606-configuration/getting-started.md | 228 +++++++++---------
.../2606-configuration/migrate-to-2606.md | 188 ++++++++-------
.../teamcenter2606/integrations-result.png | Bin 0 -> 336956 bytes
.../teamcenter2606/object-mapping.png | Bin 0 -> 255358 bytes
.../teamcenter2606/property-mapping.png | Bin 0 -> 250528 bytes
.../service-document-integrations.png | Bin 0 -> 348740 bytes
.../service-document-settings.png | Bin 0 -> 148598 bytes
8 files changed, 232 insertions(+), 220 deletions(-)
create mode 100644 static/attachments/appstore/industry-components/teamcenter/teamcenter2606/integrations-result.png
create mode 100644 static/attachments/appstore/industry-components/teamcenter/teamcenter2606/object-mapping.png
create mode 100644 static/attachments/appstore/industry-components/teamcenter/teamcenter2606/property-mapping.png
create mode 100644 static/attachments/appstore/industry-components/teamcenter/teamcenter2606/service-document-integrations.png
create mode 100644 static/attachments/appstore/industry-components/teamcenter/teamcenter2606/service-document-settings.png
diff --git a/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2606-configuration/_index.md b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2606-configuration/_index.md
index b297bd036b3..bfaad833777 100644
--- a/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2606-configuration/_index.md
+++ b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2606-configuration/_index.md
@@ -2,27 +2,27 @@
title: "Teamcenter Connector 2606"
url: /appstore/industry/teamcenter-connector/teamcenter-connector-2606/
weight: 2
-description: "Describes the unified Teamcenter Connector 2606."
+description: "Describes Teamcenter Connector 2606, a unified Mendix Marketplace module for integrating Mendix with Teamcenter."
---
## Introduction
-Teamcenter Connector 2606 marks a shift in how Mendix integrates with Teamcenter. For the first time, we're bringing together everything you need in a single, unified Marketplace module. This release combines what were previously two separate Marketplace downloads: Teamcenter Connector and the Teamcenter Extension (which itself contained two modules: Teamcenter Toolkit and the Extension add-on) into one streamlined package that works seamlessly with Mendix 11.12 and higher.
+Teamcenter Connector 2606 is a unified Mendix Marketplace module that brings together everything you need to integrate Mendix with Teamcenter. It combines what were previously two separate Marketplace modules, Teamcenter Connector and Teamcenter Extension, with Teamcenter Extension containing two modules, Teamcenter Toolkit and the Extension add-on. Teamcenter Connector 2606 is a streamlined package that works seamlessly with Mendix 11.12 and above.
-Additionally, Teamcenter Extension has been re-built using the Web Extensibility Framework and is now available as a Teamcenter service document. You can think of a Teamcenter service document as a container that can be created on a per module basis which stores everything related to your Teamcenter integrations within a specific module.
+Teamcenter Extension has been rebuilt using the Web Extensibility Framework and is available as a Teamcenter service document. A Teamcenter service document is a container that you can create on a per-module basis. It stores everything related to your Teamcenter integrations within a specific module.
-In previous versions, the Extension stored the Teamcenter integrations and configurations on disk (resources folder), separate from your Mendix app. This made version control tricky and team collaboration more complex. With the Teamcenter service document approach, everything is stored inside the Mendix model, just like microflows, pages, and domain models. This means:
+In previous versions, the Teamcenter Extension stored integrations and configurations on disk, in the resources folder, separate from your Mendix app. This made version control difficult and team collaboration more complex. With a Teamcenter service document, everything is stored inside the Mendix model, just like microflows, pages, and domain models. This means:
* Your integrations travel with your module when you export it or commit it to version control.
* You can have different Teamcenter service documents for different purposes within the same app.
-* You can have different Teamcenter service documents for different Teamcenter instances, for example for test and production.
-
-## Architecture Overview
+* You can have different Teamcenter service documents for different Teamcenter instances, such as for test and production.
-Here's how all the pieces fit together:
+### Architecture Overview
+
+The following diagram shows how all the pieces fit together:
```
-Studio Pro (Mendix 11.12+)
+Studio Pro 11.12+
│
├── Teamcenter service document ← stores integrations + connection settings
│ └── Extension UI (TypeScript / Web Extensibility Framework)
@@ -48,23 +48,25 @@ Studio Pro (Mendix 11.12+)
(self-hosted v2506+ / Teamcenter X v2506+)
```
-## How it works in practice
+## How It Works
+
+These steps describe how Teamcenter Connector 2606 works in a nutshell:
-1. You start by creating a Teamcenter service document, where you configure your Teamcener connection and create integrations.
+1. You start by creating a Teamcenter service document, where you configure your Teamcenter connection and create integrations.
2. The Teamcenter service document generates domain model entities and microflows specific to your integration needs, placing them directly in your module.
-3. The generated microflows make use of predefined Teamcenter connector microflows for the integration with Teamcenter, using the TcConnector Java Actions to call Teamcenter's SOA layer
+3. The generated microflows use predefined Teamcenter connector microflows for the integration with Teamcenter, using the TcConnector Java Actions to call Teamcenter's SOA layer.
## Prerequisites and Compatibility
-Before you start working with Teamcenter Connector 2606, make sure your environment meets these requirements:
+Before working with Teamcenter Connector 2606, make sure your environment meets these requirements:
-| Requirement | Minimum version |
-|---|---|
-| Mendix Studio Pro | 11.12.1 |
+| Requirement | Supported versions |
+| --- | --- |
+| Mendix Studio Pro | 11.12.1 and above |
| Teamcenter (self-hosted) | 2606, 2512, 2506 |
| Teamcenter X | 2606, 2512, 2506 |
-### Required Marketplace modules
+### Required Marketplace Modules
* Community Commons
* Encryption
diff --git a/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2606-configuration/getting-started.md b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2606-configuration/getting-started.md
index 8007f739d65..e109cdc54f3 100644
--- a/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2606-configuration/getting-started.md
+++ b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2606-configuration/getting-started.md
@@ -8,125 +8,129 @@ description: "Describes how to install, configure, and build your first Teamcent
## Installation and Setup
-1. **Download and import the module**
-* Open Mendix Studio Pro 11.12, and go to the Marketplace tab. Download Teamcenter Connector 2606. Remember: you don't need to download Teamcenter Extension separately since its already included.
-* Alternatively, you can download Teamcenter Connector 2606 from the Mendix Marketplace and import it into your Mendix 11.12 project.
+Follow these steps and install and set up Teamcenter Connector 2606
-2. **Add required dependencies**
-* Make sure your app includes Community Commons and the Encryption module. These are both available from the Marketplace.
+1. Download the module from Mendix Marketplace and import it in Studio Pro 11.12.
+ Remember that you don't need to download Teamcenter Extension separately, since it is already included.
-3. **Configure security**
-* Assign the `TcConnector.User` role to the relevant user roles in your app's security settings. **Important**: The Administrator role now only has access to `TcConnector.TeamcenterConfiguration`. For all integration work, use the User role.
-* Click "Update Security" in Studio Pro to refresh entity access rules.
+2. Add the required dependencies. Make sure your app includes Community Commons and the Encryption module. These are both available in Mendix Marketplace.
-4. **Enable React client**
-- Make sure the React client is enabled in your app settings (Project → Settings → Runtime). This is required for the Teamcenter service document to work properly.
+3. Configure security. To do that, follow these steps:
-## What a Teamcenter service document contains
+ 1. Assign the `TcConnector.User` role to the relevant user roles in your app's security settings.
+ {{% alert color="info" %}} The **Administrator** role now only has access to `TcConnector.TeamcenterConfiguration`. For all integration work, use the **User** role. {{% /alert %}}
+ 2. Click **Update Security** in Studio Pro to refresh entity access rules.
-1. **Settings**
- * This is where you configure the connection to your Teamcenter instance. This is required so the Teamcenter service document can communicate with Teamcenter to retrieve business objects and properties so you can build artifacts as per your use case.
- * Set up your authentication method, test the connection, and manage sign-in state.
- * You typically configure this once per Teamcenter service document, unless you need to switch environments.
+4. Enable the React client from your app settings. This is required for the Teamcenter service document to work properly.
-
+## Contents of a Teamcenter Service Document
-2. **Integrations**
- * It shows an overview of all the integrations you've configured in this document.
- * You can see the Teamcenter integration type, the entities and microflows that were generated, and when each integration was last modified.
- * From here, you can:
- * View details of an integration.
- * Edit an existing integration.
- * Duplicate an integration (useful for creating variations).
- * Delete integrations you no longer need.
- * Navigate directly to the generated microflows and entities by double-clicking on them.
- * This is also where you can add new integrations.
+These are the details included in a Teamcenter service document:
-
+* **Settings** – This is what you can do:
----
+ * Configure the connection to your Teamcenter instance. This is required so the Teamcenter service document can communicate with Teamcenter to retrieve business objects and properties, which allow you to build artifacts per your use case.
+ * Configure your authentication method, test the connection, and manage the sign-in state. You typically configure this once per Teamcenter service document, unless you need to switch environments.
+
+ {{< figure src="/attachments/appstore/industry-components/teamcenter/teamcenter2606/service-document-settings.png" alt="Settings tab of the Teamcenter service document" max-width=70% >}}
+
+* **Integrations** – This is what you can do:
+
+ * See an overview of all the integrations you've configured in this document.
+ * See the Teamcenter integration type, the entities and microflows that were generated, and when each integration was last modified. From here, you can:
+
+ * View the details of an integration.
+ * Edit an existing integration.
+ * Duplicate an integration. This is useful for creating variations.
+ * Delete integrations you no longer need.
+ * Navigate directly to the generated microflows and entities by double-clicking them.
+
+ * Add new integrations.
+
+ {{< figure src="/attachments/appstore/industry-components/teamcenter/teamcenter2606/service-document-integrations.png" alt="Integrations tab of the Teamcenter service document" max-width=100% >}}
+
+You can have multiple Teamcenter service documents in a single app, each in its own module. This is useful for separating concerns. For example:
+
+* A **Parts** module with a Teamcenter service document for part-related integrations.
+* A **Workflows** module with a Teamcenter service document for workflow-related integrations.
+* A **Documents** module with a Teamcenter service document for dataset and document integrations.
+
+## Creating and Building Your First Teamcenter Service Document
+
+The following steps walk you through creating and building a Teamcenter service document.
+
+1. Create a Teamcenter service document.
+
+ 1. In the App Explorer, right-click the module where you want to create your integrations.
+ 2. Select **Add other**, then select **Teamcenter service**.
+ 3. Give the Teamcenter service a name, such as "PartsIntegrations" or "MainTeamcenterConnection".
+
+1. Configure your connection.
+
+ 1. Navigate to the **Settings** tab of the Teamcenter service document.
+ 2. On the **Settings** tab, provide your Teamcenter authentication option along with credentials. For details, refer to the previous [Teamcenter Extension settings page](/appstore/modules/siemens-plm/teamcenter-extension/create-an-integration/#settings-tab) information.
+
+1. Test your connection.
+ Once you have entered your connection details, click **Sign In** to test the connection.
+ {{% alert color="warning" %}} The Teamcenter service document automatically clears your sign-in state when you edit or reset connection details. This is a security feature to ensure you're always using the correct credentials with the correct Teamcenter environment. {{% /alert %}}
+
+1. Add your first Teamcenter integration.
+
+ 1. Click the **Integrations** tab at the top. At this point, the tab is empty. This is normal for a new Teamcenter service document.
+ 2. Click **Add integration**. Tiles representing all available integration types, such as **Search Item Revisions**, **Create Item with Item Revision**, are displayed.
+ 3. Click one of the integration type tiles to start configuring that specific type of integration. The **Object Mapping** page is displayed.
+
+1. Fill in the required information on the **Object Mapping** page:
+
+ {{< figure src="/attachments/appstore/industry-components/teamcenter/teamcenter2606/object-mapping.png" alt="Object Mapping window" max-width=80% >}}
+
+* Teamcenter objects
+
+ 1. Browse the Teamcenter object hierarchy.
+ 2. Select the business object type you want to work with, such as **Item Revision** or **Dataset**.
+
+* Mendix entities
+
+ 1. Choose whether to create a new entity or use an existing one.
+ If you create a new entity, the Teamcenter service will generate an entity that is a specialization of the selected entity.
+ If you use an existing entity, you can select an entity you've already defined in your domain model.
+ 2. When you're done, click **Select** to proceed.
+
+* Additional properties
+ Once you've selected the Teamcenter object type and Mendix entity, you can add additional propertiesreferences/relations to the list of default selected properties. Follow these steps:
+
+ 1. Double-click the entity or select an entity and click **Select Elements** at the top.
+ 2. Use the checkboxes to indicate:
+
+ * **Read** — Should this property be retrieved from Teamcenter?
+ * **Write** — Should this property be sent to Teamcenter when creating or updating? Write checkboxes are only available in integrations where you can write data to Teamcenter.
+
+ 3. From the **Property Mapping** window, select the properties you need for your integration.
+
+ {{< figure src="/attachments/appstore/industry-components/teamcenter/teamcenter2606/property-mapping.png" alt="Property Mapping window" max-width=80% >}}
+
+* Teamcenter integration-specific panels.
+ Depending on the integration type you choose, you might be presented with an additional configuration dialog window. For example:
+
+ * Dataset integrations let you filter by dataset type.
+ * BOM integrations let you configure BOM window properties and revision rules.
+
+ Configure these integration-specific settings as needed.
+ For more information on each of the Teamcenter integrations, refer to the [integration guides](/appstore/modules/siemens-plm/teamcenter-extension/create-an-integration/integrations/).
+
+1. Generate your integration.
+ Once you have configured everything, click **Generate**. The Teamcenter service document performs the following actions:
+
+ * Validates your integration to make sure everything is correct.
+ * Generates domain model entities, which are placed in your domain model as a tree for easy visualization.
+ * Generates microflows that implement the integration logic.
+ * Saves the integration to the Teamcenter service document.
+ * Navigates to the **Integrations** tab where the integration is now listed.
+
+1. Explore the results.
+ Once the Teamcenter service document is fully generated, you are automatically returned to the **Integrations** tab. You can find your newly created integration in the list, along with links to:
+
+ * The generated microflows. Double-click to jump directly to them in Studio Pro. Double-click a microflow name to open it in Studio Pro, and see what exactly was generated.
+ * The generated entities. Double-click to jump directly to the domain model.
-**You can have multiple Teamcenter service documents**
-You can create several Teamcenter service documents in a single app, each in its own module. This is useful for separating concerns. For example:
-* A "Parts" module with a Teamcenter service document for part-related integrations.
-* A "Workflows" module with a Teamcenter service document for workflow-related integrations.
-* A "Documents" module with a Teamcenter service document for dataset and document integrations.
-
-
-## Create and build your first Teamcenter service document
-
-### 1. Create a Teamcenter service document
-* In the App Explorer, right-click on the module where you want to create your integrations.
-* Select "Add other" → "Teamcenter service".
-* Give it a name (e.g., "PartsIntegrations" or "MainTeamcenterConnection").
-
-### 2. Open the Settings tab
-* Navigate to the Settings tab of the Teamcenter service document (it's one of the tabs at the top of the document)
-
-### 3. Configure your connection
-* In the Settings tab, provide your Teamcenter authentication option along with credentials. Please refer to the [old Teamcenter Extension](https://docs.mendix.com/appstore/modules/siemens-plm/teamcenter-extension/create-an-integration/#settings-tab) settings page for more details.
-
-### 4. Test your connection
-* Once you've entered your connection details, click the "Sign In" button to test the connection.
-
->[!NOTE] Important note about auto-logout
-The Teamcenter service document automatically clears your sign-in state when you edit or reset connection details. This is a security feature to ensure you're always using the correct credentials with the correct Teamcenter environment.
-
-### 5. **Add your first Teamcenter integration**
-* Click on the "Integrations" tab at the top. Right now, it's empty—this is normal for a new Teamcenter service document.
-* Click on "Add integration".
-* You'll see tiles representing all available integration types (like "Search Item Revisions," "Create Item with Item Revision," etc.).
-* Click on one of these tiles to start configuring that type of integration.
-* This will take you to the Import Mapping page.
-
-### 6. **Use the Import Mapping Mapping Page**
-Double-click on any one of the boxes to open the object mapping dialog.
-
-
-
-**Teamcenter side (left)**
-* Browse the Teamcenter object hierarchy.
-* Select the business object type you want to work with (for example, "Item Revision" or "Dataset").
-
-**Mendix side (right)**
-* Choose whether to create a new entity or use an existing one.
- * If creating new, the Teamcenter service will generate an entity that is a specialization of the selected entity.
- * If using existing, you can select an entity you've already defined in your domain model.
-* When you're done, choose the **Select** button at the bottom to proceed.
-
-**Mapping additional properties**
-* Once you've selected the Teamcenter object type and Mendix entity, you can add additional properties/references/relations to the list of default selected properties.
-* Double-click on the entity or select an entity and click Select Elements at the top.
-* Use the checkboxes to indicate:
- * "Read" — should this property be retrieved from Teamcenter?
- * "Write" — should this property be sent to Teamcenter when creating or updating (note the write checkboxes are only available in integrations where you can write data to Teamcenter).
-* Select the properties you need for your integration.
-
-
-
-**Teamcenter integration-specific panels**
-* Depending on the integration type, you'll be presented with additional configuration dialog.
-* For example:
- * Dataset integrations let you filter by dataset type.
- * BOM integrations let you configure BOM window properties and revision rules.
-* Configure these integration-specific settings as needed.
-* For more information on each of the Teamcenter integrations, refer to [integration guides](https://docs.mendix.com/appstore/modules/siemens-plm/teamcenter-extension/create-an-integration/integrations/).
-
-### 7. **Generate your integration**
-* Once you've configured everything, click the "Generate" button.
-* The Teamcenter service document will:
- * Validate your integration to make sure everything is correct.
- * Generate domain model entities (placed in your domain model as a tree for easy visualization).
- * Generate microflows that implement the integration logic.
- * Save the integration to the Teamcenter service document
- * Navigate to the Integrations tab where the integration is now listed
-
-### 8. **Explore the results**
-* After generation completes, you'll automatically return to the Integrations tab.
-* Find your newly created integration in the list.
-* You'll see links to:
- * The generated microflows (double-click to jump directly to them in Studio Pro).
- * The generated entities (double-click to jump directly to the Domain model).
-* Double click on a microflow name for Studio to open that microflow, and you can see exactly what was generated.
-
-
+ {{< figure src="/attachments/appstore/industry-components/teamcenter/teamcenter2606/integrations-result.png" alt="Results displayed on the Integration tab of the Teamcenter service window" max-width=100% >}}
diff --git a/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2606-configuration/migrate-to-2606.md b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2606-configuration/migrate-to-2606.md
index f5cdce5e6ee..19e10533c41 100644
--- a/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2606-configuration/migrate-to-2606.md
+++ b/content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2606-configuration/migrate-to-2606.md
@@ -5,112 +5,119 @@ weight: 20
description: "Describes how to migrate an existing app from Teamcenter Connector 2512 and Extension v4.x to Teamcenter Connector 2606, including pre-migration steps, breaking changes, deprecated microflows and Java actions."
---
-### Migrating from Teamcenter Connector 2512 and Extension v4.x
+## Introduction
-In version 2606 of the Teamcenter Connector contains both the TcConnector module and the extension, meaning that from this version onwards the Teamcenter Extension doesn't need to be downloaded seperately. If you have an existing app using Teamcenter Connector 2512 and Extension v4.x, you can migrate to version 2606. While this migration involves some breaking changes, the benefits—unified module, modern Extension framework, improved security, and better error handling—make it worthwhile.
+Teamcenter Connector 2606 contains both the Teamcenter Connector and the Teamcenter Extension. This means that, from this version onwards, the Teamcenter Extension doesn't need to be downloaded seperately. If you have an existing app using Teamcenter Connector 2512 and the Teamcenter Extension v4.x, you can migrate to version 2606.
-**Before you start: Pre-migration checklist**
+This migration involves some breaking changes, but they are outweighted by the benefits:
-⚠️ **Follow these steps carefully to avoid issues:**
+* Unified module
+* Modern Extension framework
+* Improved security
+* Better error handling
-1. **Upgrade to Mendix 11.12.1 or higher first** — Version 2606 requires Mendix 11.12.1+. If you're on Mendix 10, you must upgrade Studio Pro before importing the new connector. Mendix 10 cannot run 2606.
+## Pre-Migration Checklist
-2. **Have only one developer perform the migration** — If multiple developers migrate simultaneously, you'll end up with duplicate generated artifacts. Coordinate with your team and designate one person to handle the migration, then have others pull the updated code from version control.
+Follow these steps carefully to avoid issues:
-3. **Migrate from 2512** - If the project still contains an older version of the Teamcenter Connector (2506 or older) first follow the steps in: https://docs.mendix.com/appstore/modules/siemens-plm/upgrade-teamcenter-connector-2506-to-2512/
+1. Upgrade to Studio Pro 11.12.1 or above. If you are using Studio Pro 10, you must upgrade before importing Teamcenter 2606.
+2. Have only one developer perform the migration. If multiple developers migrate simultaneously, there will be duplicate artifacts. Coordinate with your team and designate one person to handle the migration, then have others pull the updated code from version control.
+3. Migrate from Teamcenter 2512. If the project still contains an older version of the Teamcenter Connector, such as 2506 or older, first follow the steps for [Upgrading Teamcenter Connector 2506.0.0 to 2512.0.0](/appstore/industry/teamcenter-connector/upgrade-teamcenter-connector-2506-to-2512/).
+4. Make a backup. Before starting, either create a full backup of your app or commit all current changes to version control. This gives you a safety net in case you need to roll back.
-4. **Make a backup** — Before starting, either create a full backup of your app or commit all current changes to version control. This gives you a safety net in case you need to roll back.
+## Migration Process
-**Step-by-step migration process**
+Follow these steps in this exact order to ensure a proper migration:
-**Step 1: Prepare your environment**
+1. Prepare your environment.
-1. Open your app in Studio Pro 11.12.1 or higher
-2. Make sure all changes are committed (if using version control) or backed up
+ 1. Open your app in Studio Pro 11.12.1 or above.
+ 1. Make sure all changes are committed, if using version control, or backed up.
-**Step 2: Move the Toolkit contents to the TcConnector module**
+2. Move the Toolkit contents to the TcConnector module.
-3. Remove the old TcConnector module from your project, ignore the errors for now
-4. Rename the old TeamcenterToolkit module to TcConnector, then remove the module. By doing this, the old Toolkit references in the project are now pointing to the TcConnector module.
-> [!NOTE]
-> This step doesn't change the BOMapping, we will fix this in a later step
+ 1. Remove the old TcConnector module from your project, and ignore the errors for now.
+ 1. Rename the old TeamcenterToolkit module to TcConnector module, then remove the module. By doing this, the old Toolkit references in the project are now pointing to the TcConnector module.
+ {{% alert color="info" %}} This step doesn't change the BOMapping. This will be fixed in a later step. {{% /alert %}}
-**Step 3: Import the new connector**
+3. Import the new connector.
-5. Remove the TeamcenterExtension module under add-ons, the old extension is not compatible with the new Teamcenter Connector 2606 module
-6. Download the Teamcenter Connector 2606 from the Mendix Marketplace, this now also contains the new version of the extension
-> [!NOTE]
-> The Teamcenter Extension is not found anymore under Extensions, but it can now be found as a new Service Document, similar as a microflow, it can be found by: Right click > Add other > Teamcenter service__
+ 1. Remove the TeamcenterExtension module under add-ons, as the old extension is not compatible with version 2606 of the Teamcenter Connector.
+ 1. Download the Teamcenter Connector 2606 from Mendix Marketplace. This now also contains the new version of the extension.
+ {{% alert color="info" %}} The Teamcenter Extension is no longer included in Extensions. It is available as a new Service Document, similar to a microflow. You can find it by right-clicking the module, selecting **Add other**, then selecting **Teamcenter service**. {{% /alert %}}
-**Step 4: Resolve breaking changes**
+4. Resolve breaking changes.
-7. Studio Pro will show you errors where your microflows or domain model reference things that have changed. Work through these systematically. The most common issues you'll encounter:
- - Errors in microflows that were generated by the Teamcenter Extension can best be re-created by the new version of the extension, see Step 9
- - Missing microflows/Java actions can be found in the deprecated table below
- - References to `TeamcenterToolkit.*` — Change these to `TcConnector.*` (because Toolkit was merged into TcConnector)
- - References to `FileType` — Change these to `NamedReference`
- - Microflows that handle the Boolean return value from `Login` — Remove this handling, as `Login` now throws an exception instead
- - See the breaking changes reference below
+ 1. Studio Pro will display errors where your microflows or domain model reference things that have changed. Work through these systematically.
+ The most common issues you will encounter are:
-**Step 5: Update security**
+ * Errors in microflows that were generated by the Teamcenter Extension can best be recreated by the new version of the extension. Refer to step 9 for details.
+ * Missing microflows/Java actions can be found in the [Deprecated Microflows and Their Replacements](#deprecated-microflows) and [Deprecated Java Actions and Their Replacements](#deprecated-java) tables.
+ * References to `TeamcenterToolkit.*` — Change these to `TcConnector.*`, because Toolkit was merged into TcConnector.
+ * References to `FileType` — Change these to `NamedReference`.
+ * Microflows that handle the Boolean return value from `Login` — Remove this handling, as `Login` now throws an exception instead.
+ * Refer to [Breaking Changes](#breaking-changes) on this page.
-8. Click "Update Security" in Studio Pro (open domain model → Update Security), make sure that all atrributes on persistent entities have read-rights
-9. Remember: the Administrator role now only has access to Teamcenter Configuration, so assign the User role to module roles that need entity access
+5. Update security.
-**Step 6: Enable React client**
+ 1. Click **Update Security** in Studio Pro.
+ 1. Make sure that all atrributes on persistent entities have read rights. The **Administrator** role now only has access to Teamcenter Configuration, so assign the **User** role to module roles that need entity access.
-10. Go to Project → Settings → Runtime
-11. Make sure "Use React client" is turned on
+6. Enable the React client.
-**Step 7: Create a Teamcenter Service Document**
+ 1. In your App Settings, go to the **Runtime** tab.
+ 1. Select **Yes** next to **Use React client**.
-12. In the module where your Teamcenter integrations live, right-click and select "Add others" → "Teamcenter Service"
-13. Give it a name (e.g., "MainIntegrations")
+7. Create a Teamcenter Service Document.
-**Step 8: Reconfigure your connection**
+ 1. In the module where your Teamcenter integrations live, right-click and select **Add others**, then click **Teamcenter Service**.
+ 1. Give it a name.
-14. Open the Teamcenter Service Document and go to the Settings tab
-15. Enter your Teamcenter URL and authentication settings
-16. Click "Sign In" and login to Teamcenter
+8. Reconfigure your connection.
-**Step 9: Recreate your integrations**
+ 1. Open the Teamcenter Service Document and go to the **Settings** tab.
+ 1. Enter your Teamcenter URL and authentication settings.
+ 1. Click **Sign In** and log in to Teamcenter.
-17. Your existing domain model entities and microflows are still in your app—they haven't been deleted. However, you'll want to regenerate them using the new Extension to take advantage of improvements and ensure they're compatible with the new connector
-18. In the Service Document, click on '+ Add integration' and start a journey that matches each of your existing integrations
-19. Configure it the same way as before (the journey types and options are the same)
-20. Click "Generate" to save and generate the integration
-21. Replace the old microflows with the new generated microflows
-22. You can use the "Duplicate" feature in the History tab to create variations of an integration without reconfiguring from scratch
+9. Recreate your integrations.
-**Step 10: Test thoroughly**
+ Your existing domain model entities and microflows are still in your app. However, you need to regenerate them using the new Extension to take advantage of improvements and ensure that they are compatible with the new connector. To do that, follow these steps:
-23. Run each generated microflow against your Teamcenter instance
-24. Verify that search, create, update, and retrieval operations work as expected
-25. Test error handling by triggering error conditions (e.g., invalid search criteria)
-26. If you have automated tests, run them to ensure integration behavior is correct
+ 1. In the Service Document, click **+Add integration** and start a journey that matches each of your existing integrations.
+ 1. Configure the integration the same way as before. The journey types and options are the same.
+ 1. Click **Generate** to save and generate the integration.
+ 1. Replace the old microflows with the newly generated microflows.
+ 1. You can use the **Duplicate** feature on the **History** tab to create variations of an integration without reconfiguring from scratch.
-**Breaking changes reference**
+10. Test thoroughly.
-Here's a comprehensive table of breaking changes and what you need to do about each one:
+ 1. Run each generated microflow against your Teamcenter instance.
+ 1. Verify that search, create, update, and retrieval operations work as expected.
+ 1. Test error handling by triggering error conditions, such as invalid search criteria.
+ 1. If you have automated tests, run them to ensure integration behavior is correct.
+
+## Breaking Changes {#breaking-changes}
+
+This is a comprehensive table of breaking changes and actions to take each one:
| Area | Change | Action required |
-|---|---|---|
-| **Teamcenter Toolkit Module** | Module merged into TcConnector; module no longer exists | Update all references from `TeamcenterToolkit.*` to `TcConnector.*` |
-| **Entity security** | Create and Delete rights removed from all entities | Remove any UI or microflow logic that relied on client-side Create/Delete; use microflows instead |
-| **Input parameter `ConfigName` renamed to `ConfigurationName`** | in generated microflows the input parameter is now called ConfigurationName and is optional | Set the ConfigurationName or leave it empty |
-| **Admin role** | Administrator no longer has entity access | Reassign to User role where needed |
-| **`FileType` / `File Type`** | Renamed to `NamedReference` / `Named Reference` | Update all references in microflows and mappings |
-| **`CreateBOMWindow_Generic`** | Moved to TcConnector; updated to use `CreateOrReconfigureBOMWindows`; pre-configured variants removed | Regenerate BOM microflows via the Extension or update manually to use `TcConnector.CreateBOMWindow_Generic` |
-| **`Login` Java action** | No longer returns Boolean; throws exception on failure | Remove Boolean result handling; wrap in error handler |
-| **`Logout` Java action** | Now returns Boolean | Update callers if return value was previously ignored |
-| **Error messages** | Connector no longer shows in-app messages; throws exceptions instead | Ensure calling microflows have error handlers |
+| --- | --- | --- |
+| Teamcenter Toolkit Module | The module was merged into TcConnector. The module no longer exists. | Update all references from `TeamcenterToolkit.*` to `TcConnector.*`. |
+| Entity security | The `Create` and `Delete` rights were removed from all entities. | Remove any UI or microflow logic that relied on client-side `Create`/`Delete`. Use microflows instead. |
+| Input parameter `ConfigName` renamed to `ConfigurationName` | In generated microflows, the input parameter is now called `ConfigurationName` and is optional. | Set the `ConfigurationName` or leave it empty. |
+| Admin role | The **Administrator** no longer has entity access. | Assign the **User** role where needed. |
+| `FileType` / `File Type` | This was renamed to `NamedReference` / `Named Reference`. | Update all references in microflows and mappings. |
+| `CreateBOMWindow_Generic` | This was moved to TcConnector, and was updated to use `CreateOrReconfigureBOMWindows`. Pre-configured variants were removed. | Regenerate BOM microflows via the Extension or update manually to use `TcConnector.CreateBOMWindow_Generic`. |
+| `Login` Java action | No longer returns Boolean. Throws exception on failure. | Remove Boolean result handling and wrap in error handler. |
+| `Logout` Java action | Now returns Boolean. | Update callers if return value was previously ignored. |
+| Error messages | Connector no longer shows in-app messages. It throws exceptions instead. | Ensure calling microflows have error handlers. |
-**Deprecated microflows — with replacements**
+## Deprecated Microflows and Their Replacements {#deprecated-microflows}
-These microflows still exist in the deprecated folder but can't be used anymore (excluded). Replace them with the recommended alternatives:
+These microflows still exist in the deprecated folder, but can no longer be used. Replace them with the recommended alternatives:
| Deprecated | Replacement |
-|---|---|
+| --- | --- |
| `AreMultipleTcConfigActive` | No replacement |
| `CloseBOMWindow`| `BOMWindow_Close` |
| `DownloadFile` | `DownloadFile` / `DownloadImage` Java action |
@@ -118,34 +125,33 @@ These microflows still exist in the deprecated folder but can't be used anymore
| `ExecuteLogout` | `Logout` microflow |
| `HandleActiveConfigErrors` | No replacement |
| `HandleServiceErrors` | No replacement |
-| `RetrieveConfigNameFromSingleActiveConfiguration` | Use `empty` for configurationName parameter in Java actions, Java actions now handles active configuration in the Java code |
+| `RetrieveConfigNameFromSingleActiveConfiguration` | Use `empty` for the `configurationName` parameter in Java actions. Java actions now handle active configuration in the Java code. |
| `RetrieveHttpHeaderList` | No replacement |
-| `RetrieveTcSessionBasedOnConfigName` | No replacement, TcSession should not be manually consumed; it is automatically handled by the TcConnector module. |
-| `RetrieveTeamcenterConifgurationByName` | Use `empty` for configurationName parameter in Java actions, Java actions now handles active configuration in the Java code |
-| `RetrieveTeamcenterConifgurationFromTcSession` | No replacement TcSession should not be manually consumed; it is automatically handled by the TcConnector module |
+| `RetrieveTcSessionBasedOnConfigName` | No replacement. `TcSession` should not be manually consumed. It is automatically handled by the TcConnector module. |
+| `RetrieveTeamcenterConifgurationByName` | Use `empty` for the `configurationName` parameter in Java actions. Java actions now handle active configuration in the Java code. |
+| `RetrieveTeamcenterConifgurationFromTcSession` | No replacement. `TcSession` should not be manually consumed. It is automatically handled by the TcConnector module. |
| `ShowPartialErrors` | No replacement |
| `UpdateSession` | No replacement |
-**Deprecated Java actions — with replacements**
+## Deprecated Java Actions and Their Replacements {#deprecated-java}
-These Java actions still exist in the deprecated folder but can't be used anymore (excluded). Replace them with the recommended alternatives:
+These Java actions still exist in the deprecated folder, but can no longer be used. Replace them with the recommended alternatives:
-|Java Action | Replacement |
-|---|---|
-| `PerformAction` | `PerformAction3` |
-| `GetWorkflowTemplates` | `GetWorkflowTemplates2` |
-| `CreateBOMWindows` | `CreateOrReConfigureBOMWindows` |
-| `CreateBOMWindows2` | `CreateOrReConfigureBOMWindows` |
-| `WhereUsed` | `WhereUsed2` |
-| `ExpandPSOneLevel` | `ExpandPSOneLevel2` |
-| `GetTcSessionInfo` | `GetTcSessionInformation` |
-| `GetItemFromId` | `GetItemAndRelatedObjects` |
+| Java Action | Replacement |
+| --- | --- |
+| `PerformAction` | `PerformAction3` |
+| `GetWorkflowTemplates` | `GetWorkflowTemplates2` |
+| `CreateBOMWindows` | `CreateOrReConfigureBOMWindows` |
+| `CreateBOMWindows2` | `CreateOrReConfigureBOMWindows` |
+| `WhereUsed` | `WhereUsed2` |
+| `ExpandPSOneLevel` | `ExpandPSOneLevel2` |
+| `GetTcSessionInfo` | `GetTcSessionInformation` |
+| `GetItemFromId` | `GetItemAndRelatedObjects` |
| `RetrieveCookie` | No replacement |
-**What carries forward automatically**
-
-The good news: not everything needs to be rebuilt from scratch.
+## Automatically Migrated Items
-✅ **Your domain model is preserved** — Entities and associations generated by the previous Extension remain in your module. They're part of your app, so they don't disappear during the migration.
+Not everything needs to be rebuilt from scratch. These items are automatically migrated as they are:
-✅ **Your microflows are preserved** — Generated microflows remain in your app. Only those affected by specific breaking changes (input entity naming, Toolkit module references) need regeneration or updates.
+* Domain model — Entities and associations generated by the previous Extension remain in your module. They are part of your app, so they don't disappear during the migration.
+* Microflows — Generated microflows remain in your app. Only those affected by specific breaking changes, such as input entity naming or Toolkit module references, need to be regenerated or updated.
diff --git a/static/attachments/appstore/industry-components/teamcenter/teamcenter2606/integrations-result.png b/static/attachments/appstore/industry-components/teamcenter/teamcenter2606/integrations-result.png
new file mode 100644
index 0000000000000000000000000000000000000000..52459a1d1415eb92ed50e170688b06118d1a6b19
GIT binary patch
literal 336956
zcmdqI2UAmv_cg2+5d}l=T0p7@3QDukLlIDEN>`97B1#X0UIHqHC`b_yRJwqGO0NMD
zgh-7Lq=ga)5Lze+JwOP&2k-s;+syL?-pnLS&PkX#XRp2YT5IpTF*48wvGcMYI&=u6
zt8>c)_|tyq(9sXajsiz!j4EA#KZm_dv^5VEb@5YxH%Fdn+|xL8s5F*i*Pa!4f80~&
zq4%LfqH_n&!!I3J`GJFf``othF@-+$@wbOL9@2(6I(m3JL49oR9|OL!kJP=TVHRM!
zIO$QBX1^oAIo?g;dzNWK~=jtcQw3@HR2pG?NyD0
z@p_1>`RsZfT+hnRzX3k5Q<&_dYkuF{-2Xnwrg~;y9x8L||NVHM-=cQ&|9#r*vdbdN
z|NHc<_n-fN{`Ewo?3gl*Z>rOVHal$*b#LRNIcx6At4-PuZPjo;Nf;|`zXZ=~yCfEB
zVHwZ`ylZJyp-AEGs1_%K{8PmFeAFJuJ5{Fa+K~w`x=kGxZ#hCFoWo~8frePxfjYM-G{bqWUe0@P9p
z$FIB9tsU;E>8}F)WlQU{@_BzR1uDYl@%!Oku`wGd)YydxMhU^xb4;3CM@mP=dcLfA
zlr<-fq6uSE@I^v?xLeI_v7wxY+(X}Qn>S*dND8+S8*1@HCLDXkcxSBwI1#th`zAkq
z0@5$Y5RiHX7L*{21?26L--Y2MiqRMC;LNny=*zUW?EMfukNOS4bBaExi?#HV(<`cP
zBM+c)T$VD=+AU9ERJmOrhlg26W!YdwnxdUtVp>b||yCYi~pNKR4&X
z=UY4JAw|DZ8oIf!e>m(BiMN3BX|tTfV*>F-lb=#
zIxLZ$u0=)uV8+d#vJGBj@oNx2v&aYl57Jprp0TY&Ono=os?Vk=YTYuE9QC78SSQE!
z$4@;(!R{Mem74kO$biGw@;dH22xT6NhTtL~pm+CnF!#BAAk!Q}>+3Yf^71dZnb}`S
zoornRokzQpJMlK>Q^1xrV;7u{gmVY+f^DZ1MAt}GCv3s{en?PD$N(PNtqGo?se;qj
zh}&h`KTu<3k3Pyn$iYMFiTH)TywP?EAb3u;^XZ3GE;1z*vm
z-5yj}+%u6Rf)_m1CG(giNT0c?YM(Jbp`oX2o1*50wbVgVWnYrEvU^>%8`@@c#?coJkP50LLRf=uU5~U)FH)V}QOg<@p
ziuT!Wxa9Cb0doVbpiT>%PiNW1#qUHpHeX*@h5G#H98(_J5dCjJJn|>eOJs~56xxPv
z+#~IrI(hJzW{Gx$xYxyUAH6A_<4uR>jC8SW{dEL%TkC`viZ@HxH>zmNZdWM!tN!oI
zPYnA@ROEDtkl^{Ws!;-c*a-W)Bvmk+EAbW+WraeAF{4p}b2TlQ;Duhd&0g~U$#PR5w^O`lB_~w5M>_YSR_@~q)NtQgfQFJ7&+H8!
zgqz>y38+AcG~Y&jjB3Z9Yy0zZaeYENW4q}||9m)DeWOtQ&p~6gZio1YLscG+(7vqB
za}%Qd$0pvMEhuUE(is_sg;J3pYlOb^jfB={fs3DAW7Ha9d))I_de9w}LqYzeJrk$l
zaONpU&8~nhiy|Fx5mt$p*7a}oLy0-KsS(1hx21eEI}9}?dFL;
z-eoUPpGkZp)DZ#UTq%_K@9WwgI{&b;e8KQfUrGFS$;w@3)NhQ$amjZqM)lHRtgbJY
zfu@7Y`jZOdgvrt66h@X19jlx>20q!dSjG&+5MJ?KTI5iawWWWI*O
z;a3x1>tzcgrXKaqj3nmxKe+JKmQP{HT4qAgwdL*5qHuXr-yoZK?@=kgql;4Yr;yxkg8x;NKztUDb0rc)Zq;Bt@UWppaG)DTIF91*(()c_gaw6w$O66b+BT5h*
z`3HFR;J{tp{r1buZX(?&$<`~^wE6F3cKYb2eijj9lqsP|nB
zN>~U)@7iTwNHzQKnB70gcj23#AM>9phP@bb>E04TPr22VtDo*Rx|TYXHxd1KeX^N(
zm4~j?(6fkC4Jl?l=`$vMX3~B5%QCv%z2jnI7?K`*6KnCPJcQNXdJ!=ZPTr1w$MxlHrr)LKby?is)Vl0Wr0yVQ;(A8gI?$(
z$R-+!GDnaN3-0HhxXnX@Lc|o!74Vgf_Da>-N($YxlIjDO`%{P`2mKrVFWmmb$Jg!k
z_u-)pu|EZ-HMzbnk?xHudlnblb`P*a)6@EpdV%a50~W-uoh$N0z9-&24iy?%s6npNp9b
z`F_v<59&UP*3)x`Q5zGo3g?kyWAj1LRtYEH_MW$1D0LYP>e_GZXOcj_+?AfD_2R5u
z#%yV@g>cv$T6#2_xNK(BMMxm-Ot;qB3+(sh#zOxM#{mlSWBwNa=lWFpB@FW1O~WoD
zfa?KyWQxhu2~9^a>;dS7UK|1w_AizxLm00|!&Yl7JFL`=OFM+NWi
z<;%o9D55eMBADsCRb!wlD)Uk0e=j(@_ujzJ*?tWmf6e~|bIo~p2Mqf%tJtfRdUT?S
zm)n7<=sTfww?X>M2Yt3_6MH2YafK@Yw4P_C?uC{2HqZyWur_zL|7~Y~(r12<>*2LR
ziC!}Y+6?sefxArK>$U?73mVeMxK+b^A_
zsgt0Dq5A&WYV#q4h;(<1A>S^JjAuOI)+am0BGa?T@Vi9afbJ$m-o!Cgu{89y8Dkp
ztsBZ!cJ|AUMz6FyENxPUXZ_d3A!H8S6pTptJj4{Y^JAE@)3Hu|>K)0Wd$)`i_Y!34
z!cG}GUlY~7b=vJmK{)(yh2FLC#74|U){eP@5KwB^hJ0yQ$HDxy>3E5vWLtRG^1ahf
zvM;4gbvqcuzu~qOPLQtE+Z=94hNhlRkzcqVc0#c=xajw(OZv$In;X%lb^xKBFw>!?
z4q%@KN+*N%2)QN@d9a=y}9V$)+g_Ki9Kwb~Ntm=!{ftM{Mu2t)^$&J5%MwQ%nA8aSEg$LU>r%X0rljWmRse
z_1u{9;Kt`2fE6n44kkD*)%s2jJhKat>KvwyrwsZoMf*Rw8@@9F@(;*@K#E+3p9XL5
zMit-q^03^mkbhtyr;VcLNOnkH|LaK#IJFK#uj~hs-$$qGc-xDS;8gB7@8DS6u@q*(IdR|6?F9h!)JIIkz#FUoZ8Qhv
z%&aw{ZFQqLnbamn7){#q;=dD}Az556->gs+wB3Js>>icq?15s2Zc`b~wuU}_yCH-B
zDSZg{b;HXi#BP@Zg>G>(?=%(pdoeUorjGgM^B_~q&Ts$H=N_Oa)C>QN_@Q6QzINvr
zUQMPl`HobbE~6;8?PGXLn}eZ>h<=i!KD4?yDmm%)msgRq2OQ$%Gn8emPoVN?ZZ`5T
z#ar%KmkKG!nEBOfKirn+c9V0XRVb{@S7DTrVzCrvA+$Z6Y`64e%z?##Z<5b0t5xaO
z$k~^$xz4T_JC~I8P^ta|;*V{L;1rkS$Yc0T0~V)a*(lXE$5-T*T69Yx?gaMUT}oyc
zp3%&xo~^HKb$czH?XRRDUaj^anH^UM?m!8nd}3j~s_pJ-o|x(w3-kYU>i^t8SgG3(
zEO7o~^3-CZL$7)ySkd=2F=PaN-F4HNv}OOrfN5NWp5UawCx5Jm+`=GB)3y`*48k=qdZzc?C{B})7a%hQWhOk*_3sM4*!QU1%IAzbzZk$)B
zE#gKEI1mCfQ1WDx;TSuKrAs-Qu(`_ySg)_-z>i$1o2knsT@LS2k08WgZrX-ygC14{yn*iKoRzi~
z-4C4)Jg4}?ItT;g^<9s;HQFjU_6D5%4EsNldVi-3|DqK)_$Il7vrb@=?}1Rq<pm4
zkrS7EHXX~Ey$NfUQwSWHttN#g&_X|4f?_u8P)sV@^rEms?udaZoSY0Y!+cVW%8o@eox4hi*u
zwmqJWua8KsCa(CCmUoN@MzwobUC5Hx>-Bl>h{Z4`A?KbT2yo`npW_Lzx`&ZYZx=sa55VLcC@OLkQLk38xa$%+Q9}&+V
z_D+1u8Crhd6Y^8f`P$>$3VxJ{Wn=#Po*H(3bOfd(?t=)Lao%e2wWg8f6L
zHd>S&keJ-4OEAT2`8Z{|vB9ch><-xy{>L2{LlAJ-7W%Sh<*!xM%p~`Ledla-j!h`%J&5=sn#>73W
zQe*DA+6_vX3x(~xhwcqEDc=ujE4S>c*>6nY^8dsn$Ex>04f=+C7p9(LceXA)&{^vG
z2vK+7JuO&Hu8mQikcEzUOrX>mldhzi4GpYA^iipGO~-qW6q}w(5boqNp5x
zkn`3KAMBQ!*Bc~YzpF<%M1G*h@RG@_wvJ{k5p0<7i=N=Qgh!`VxN2T&5exnIa|I^et9QSeIS};lpF`4Q6R4$&GRB;=|O%
zAWMPyP!;Z(!0`z<+IHUP#?!7OS7^P~r^?Yr1rN9mU3B)<)F;k;-B10}blGB?D^f1W
zI=G3b-2Ua;Wz);IdxEw!omE3#RGcgA?)96}bXI_6RS2PVhGT6d1zIHE#W*AfDM#y5
zRQ$ZYc$M5zb{O26PB$PY>9=~}a>zB)J@$*&4H?&PIcd*O6#{5$00UISnq{o@C94>V
zNoS>yH`Q-DU6XanhaG#|wqVYdbr;UW^Hs$Qqb>w78VaJmM{&z+fUl0FVjJ^!Frgy-v81pOt
zC=bNn-0`N`>hPC~^5a)Y>l=lG4B?>Q^2RF7k*cLl%&gSuKb3jkMGoE~Nvnx!@UxJw
z=sw%eDN!-KP`pvUKaq#A-}r}?`Mne0Xoz`K4CeG^nwElS-e1p=gEuFox^5sUESg
z_&wmmXS&hP7w&{
zH&L4VdJ)$BUVrL`L~`3lH05$160o7ee1pWG_bxQ%{X
z+kQ_NTLp=+H^uRvoQ@J!y72X>{H?P`HDoO?Aqb)`P0N<%zQeM0`Po2+L~+AKz)oMg
zmt2hC;Ko7r;dVReD&owLyo?(rf&p_Gw)x-aZ)UHGa$lfqCmg*=+@T_!$4Y{!VLwv@
z)nB?djA&q-^>5>B!52TzR}uEm^(3wCxyj8sp>>c9B0tW0X^x}bk+D5%H2`Z^$U*lsNmnndmPhaDAGTL~HCe%xB$4-=|1=~uk>k}QQE-~;)3@Tx)PG5y
zD5zbdp?F6h->%)xsS4ig%)H*9Erl#13rV-o#ox$t=IUxAujh^`B=Mb{;+Dt|6{|hg0tL~w$k>@
zcG;6@+G?xNN46@vFz%1ly9!E^Ujuu*e%{4j3rmqHPu{zvzVCA9>^r+qhSpQby?dMK
zDu&9j=_0Mxb=|?~l?}V^?E7ogr^Y4D>Wxfz=iFQ3A95LVQ)0$6m(3)rhp2sA`3980
z#X^>#1P2{yRuFf5(n$Uxbxvni)(M{YsN{tz{2eo$BE0TwQ1k;M*MXwsKdH@4K+EwFpc-nf;nKBADSCq}J79=$N<5!}R@
z%=nVqB(c6y%s=Wg0;f!$a7i_5-|MT%ew%)EXra`;e_oD)_mPsFd5ChUq+1R-U$)db
z){bf=yOH*9OL)p?mECvS|9qfNj|aNirrtGc@s!hx)W2^#u1Dnzt`81zH;m2B?7)aCq7kuV%Lyk
zHnHYmB7{E!ZfRi)ffqPkWTw*kXHNvunXzaiv94U=s%F@?2f?bRhAH_w=a)a~Bhb&T
zyc2W<6js_wjaA0<@8F!^LU~HC>}CG7O4)iV7volc^qA3G-(v7Frt?)^4Of*2yqFXu
z^rCpPTF!K6(n4vT+GbQE7N20K#^_;u_b!&1ue^PNPj2r5$!9$D=~Kq&5ypv7tvmg*
z{t+fh>mL%H3@oC?c0LQI33xa{LKDBZS0!KG4