From 206fddad18c877d57e6b80bc9ccea3fda8b1e112 Mon Sep 17 00:00:00 2001 From: wanchoorohan <157635704+wanchoorohan@users.noreply.github.com> Date: Fri, 31 Jul 2026 12:46:36 -0400 Subject: [PATCH 1/6] Revise migration steps for Teamcenter Connector 2606 Updated migration instructions for Teamcenter Connector to reflect changes in module structure and deprecated entities. Clarified steps for removing old resources and testing integration. --- .../2606-configuration/migrate-to-2606.md | 54 ++++++++++++++----- 1 file changed, 41 insertions(+), 13 deletions(-) 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 22d385c42f1..b3140944799 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 @@ -34,11 +34,10 @@ Follow these steps in this exact order to ensure a proper migration: 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. -2. Move the Toolkit contents to the TcConnector module. +2. Remove resource files - 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 TeamcenterToolkit module. By doing this, the old Toolkit references in the project are now pointing to the TcConnector module. - {{% alert color="info" %}} This step does not change the BOMapping. This is fixed in a later step. {{% /alert %}} + 1. In your resources folder, remove the `OperationMapping`, `TeamcenterCommon`, `TeamcenterConnector` folders > these have moved to the `TcConnector` folder + 1. Keep the `TeamcenterExtension` folder for now, this can be removed once all the journeys are migrated to the new service document 3. Import the new connector. @@ -53,11 +52,13 @@ Follow these steps in this exact order to ensure a proper migration: The most common issues you will encounter are: * 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. + * Missing microflows/Java actions can be found in the deprecated table below. + * Deprecated microflows/java actions can be found in the internal>deprecated folder in the TcConnector module. These microflows are not used by the connector anymore, but you can include them and move them to your own module if needed. + * References to `TeamcenterToolkit.*` in BO mappings — Change these to `TcConnector.*` (the Toolkit module is 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. + * The `Login` microflow doesn't return a boolean anymore, as `Login` now throws an exception instead + * We have deprecated microflows that use the `TcSession` entity, please don't use the `TcSession` entity in your code, if you want to know if someone is logged in please use the `RULE_TeamcenterConfiguration_IsLoggedIn` + * See also the breaking changes reference below 5. Update security. @@ -90,12 +91,19 @@ Follow these steps in this exact order to ensure a proper migration: 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. -10. Test thoroughly. +10. Remove the Toolkit module from your project - 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. + 1. Before removing the Toolkit module, it is a good moment to commit your work. Right click on the Toolkit module and select "find usages of this module" + 1. Since we have merged the Toolkit module with the TcConnector module, all references to the toolkit should point to the TcConnector + - Tip: If there are still a lot of resources pointing to the toolkit, you can rename the toolkit to TcConnector2, remove the TcConnector2, rename the TcConnector to TcConnector2 and back to TcConnector. This trick connects the old resouces in the Toolkit to the new ones in the TcConnector. + 1. Search (ctrl+f) on "Toolkit", to see if there are any BO mappings left that reference the Toolkit, replace these with TcConnector. + +11. Test thoroughly + + 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 (e.g., invalid search criteria) + 1. If you have automated tests, run them to ensure integration behavior is correct ## Breaking Changes {#breaking-changes} @@ -150,6 +158,26 @@ These Java actions still exist in the deprecated folder, but should no longer be | `GetItemFromId` | `GetItemAndRelatedObjects` | | `RetrieveCookie` | No replacement | +## Deprecated Entities + +The following entities have been deprecated. To indicate this, the entities have been renamed with an underscore prefix: + +|Entity | +|---| +|CreateBomWindowInput| +|CreateBomWindowInput_CreateBomWindowResponse| +|CreateBomWindowResponse| +|ExpandPSOneLevelResponse| +|GetItemFromIdInput| +|GetItemFromIdResponse| +|GetWorkflowTemplatesInput| +|ItemRevisionOutput| +|RevisionIDs| +|SessionUser| +|TcServerInfo| +|WhereUsedInput| +|WhereUsedResponseInfo| + ## Automatically Migrated Items Not everything needs to be rebuilt from scratch. These items are automatically migrated as they are: From 9e57ccb975fe4cd08ba17de0577e91de89b134de Mon Sep 17 00:00:00 2001 From: katarzyna-koltun-mx <108737161+katarzyna-koltun-mx@users.noreply.github.com> Date: Mon, 3 Aug 2026 13:53:23 +0200 Subject: [PATCH 2/6] Update migrate-to-2606.md --- .../2606-configuration/migrate-to-2606.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) 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 b3140944799..b60b38ce2e4 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 @@ -34,10 +34,10 @@ Follow these steps in this exact order to ensure a proper migration: 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. -2. Remove resource files +2. Remove the resource files. - 1. In your resources folder, remove the `OperationMapping`, `TeamcenterCommon`, `TeamcenterConnector` folders > these have moved to the `TcConnector` folder - 1. Keep the `TeamcenterExtension` folder for now, this can be removed once all the journeys are migrated to the new service document + 1. In your *Resources* folder, remove the *OperationMapping*, *TeamcenterCommon*, *TeamcenterConnector* folders. The contents of these folders are now in the *TcConnector* folder + 1. Keep the *TeamcenterExtension* folder for now. You can remove it after all the journeys are migrated to the new service document. 3. Import the new connector. From 6060b2a360b57029883b012f4c13f8f9bd8cfd15 Mon Sep 17 00:00:00 2001 From: katarzyna-koltun-mx <108737161+katarzyna-koltun-mx@users.noreply.github.com> Date: Mon, 3 Aug 2026 14:19:34 +0200 Subject: [PATCH 3/6] Update migrate-to-2606.md --- .../2606-configuration/migrate-to-2606.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) 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 b60b38ce2e4..7a4b7a41304 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 @@ -52,13 +52,13 @@ Follow these steps in this exact order to ensure a proper migration: The most common issues you will encounter are: * 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 table below. - * Deprecated microflows/java actions can be found in the internal>deprecated folder in the TcConnector module. These microflows are not used by the connector anymore, but you can include them and move them to your own module if needed. - * References to `TeamcenterToolkit.*` in BO mappings — Change these to `TcConnector.*` (the Toolkit module is merged into TcConnector) - * References to `FileType` — Change these to `NamedReference`. - * The `Login` microflow doesn't return a boolean anymore, as `Login` now throws an exception instead - * We have deprecated microflows that use the `TcSession` entity, please don't use the `TcSession` entity in your code, if you want to know if someone is logged in please use the `RULE_TeamcenterConfiguration_IsLoggedIn` - * See also the breaking changes reference below + * Missing microflows and Java actions can be found in the deprecated table below. + * Deprecated microflows and java actions can be found in the *internal>deprecated* folder in the **TcConnector** module. These microflows are not used by the connector anymore, but you can include them and move them to your own module if required. + * References to `TeamcenterToolkit.*` in BO mappings should be changed to `TcConnector.*` The Toolkit module is merged into TcConnector. + * References to `FileType` should be changed to `NamedReference`. + * The **Login** microflow does not return a Boolean value anymore. **Login** now throws an exception instead. + * We have deprecated microflows that use the `TcSession` entity. Do not use the `TcSession` entity in your code. If you want to know if someone is logged in, use `RULE_TeamcenterConfiguration_IsLoggedIn` instead. + * For more information, refer to the [Breaking Changes](#breaking-changes) section. 5. Update security. From 9d5af55412c221f4faed998016958b052688c2bd Mon Sep 17 00:00:00 2001 From: katarzyna-koltun-mx <108737161+katarzyna-koltun-mx@users.noreply.github.com> Date: Mon, 3 Aug 2026 14:23:10 +0200 Subject: [PATCH 4/6] Update migrate-to-2606.md --- .../2606-configuration/migrate-to-2606.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) 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 7a4b7a41304..fac67c338b2 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 @@ -52,8 +52,8 @@ Follow these steps in this exact order to ensure a proper migration: The most common issues you will encounter are: * 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 and Java actions can be found in the deprecated table below. - * Deprecated microflows and java actions can be found in the *internal>deprecated* folder in the **TcConnector** module. These microflows are not used by the connector anymore, but you can include them and move them to your own module if required. + * For a list of deprecated microflows and Java actions, see [Deprecated Microflows and Their Replacements](#deprecated-microflows) and [Deprecated Java Actions and Their Replacements](#deprecated-java). + * Deprecated microflows and Java actions can be found in the *internal>deprecated* folder in the **TcConnector** module. These microflows are not used by the connector anymore, but you can include them and move them to your own module if required. * References to `TeamcenterToolkit.*` in BO mappings should be changed to `TcConnector.*` The Toolkit module is merged into TcConnector. * References to `FileType` should be changed to `NamedReference`. * The **Login** microflow does not return a Boolean value anymore. **Login** now throws an exception instead. @@ -91,14 +91,14 @@ Follow these steps in this exact order to ensure a proper migration: 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. -10. Remove the Toolkit module from your project +10. Remove the Toolkit module from your project. 1. Before removing the Toolkit module, it is a good moment to commit your work. Right click on the Toolkit module and select "find usages of this module" 1. Since we have merged the Toolkit module with the TcConnector module, all references to the toolkit should point to the TcConnector - Tip: If there are still a lot of resources pointing to the toolkit, you can rename the toolkit to TcConnector2, remove the TcConnector2, rename the TcConnector to TcConnector2 and back to TcConnector. This trick connects the old resouces in the Toolkit to the new ones in the TcConnector. 1. Search (ctrl+f) on "Toolkit", to see if there are any BO mappings left that reference the Toolkit, replace these with TcConnector. -11. Test thoroughly +11. Test thoroughly. 1. Run each generated microflow against your Teamcenter instance 1. Verify that search, create, update, and retrieval operations work as expected @@ -158,7 +158,7 @@ These Java actions still exist in the deprecated folder, but should no longer be | `GetItemFromId` | `GetItemAndRelatedObjects` | | `RetrieveCookie` | No replacement | -## Deprecated Entities +## Deprecated Entities {#deprecated-entities} The following entities have been deprecated. To indicate this, the entities have been renamed with an underscore prefix: From 484ff45c83f4494d314664ac43fd764ef269e5cd Mon Sep 17 00:00:00 2001 From: katarzyna-koltun-mx <108737161+katarzyna-koltun-mx@users.noreply.github.com> Date: Mon, 3 Aug 2026 14:27:12 +0200 Subject: [PATCH 5/6] Update migrate-to-2606.md --- .../2606-configuration/migrate-to-2606.md | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) 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 fac67c338b2..1c550853fae 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 @@ -93,17 +93,19 @@ Follow these steps in this exact order to ensure a proper migration: 10. Remove the Toolkit module from your project. - 1. Before removing the Toolkit module, it is a good moment to commit your work. Right click on the Toolkit module and select "find usages of this module" - 1. Since we have merged the Toolkit module with the TcConnector module, all references to the toolkit should point to the TcConnector - - Tip: If there are still a lot of resources pointing to the toolkit, you can rename the toolkit to TcConnector2, remove the TcConnector2, rename the TcConnector to TcConnector2 and back to TcConnector. This trick connects the old resouces in the Toolkit to the new ones in the TcConnector. - 1. Search (ctrl+f) on "Toolkit", to see if there are any BO mappings left that reference the Toolkit, replace these with TcConnector. + 1. Before removing the Toolkit module, commit your work by right-clicking on the Toolkit module and selecting **Find usages of this module**. + 1. Since the Toolkit module is merged with the TcConnector module, all references to the Toolkit should point to the TcConnector. + + If there are still many resources pointing to the Toolkit, you can rename the Toolkit to TcConnector2, remove the TcConnector2, rename the TcConnector to TcConnector2 and back to TcConnector. This trick connects the old resouces in the Toolkit to the new ones in the TcConnector. + + 1. Use **Ctrl+F** to search for *"Toolkit"*, to see if there are any BO mappings left that reference the Toolkit. If there are, replace them with TcConnector. 11. Test thoroughly. - 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 (e.g., invalid search criteria) - 1. If you have automated tests, run them to ensure integration behavior is correct + 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 (for example, invalid search criteria). + 1. If you have automated tests, run them to ensure integration behavior is correct. ## Breaking Changes {#breaking-changes} From c845349e31758e7f750626b95d743b2e3a3aa27d Mon Sep 17 00:00:00 2001 From: katarzyna-koltun-mx <108737161+katarzyna-koltun-mx@users.noreply.github.com> Date: Mon, 3 Aug 2026 14:28:54 +0200 Subject: [PATCH 6/6] Update migrate-to-2606.md --- .../2606-configuration/migrate-to-2606.md | 28 +++++++++---------- 1 file changed, 13 insertions(+), 15 deletions(-) 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 1c550853fae..6c5831a984e 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 @@ -164,21 +164,19 @@ These Java actions still exist in the deprecated folder, but should no longer be The following entities have been deprecated. To indicate this, the entities have been renamed with an underscore prefix: -|Entity | -|---| -|CreateBomWindowInput| -|CreateBomWindowInput_CreateBomWindowResponse| -|CreateBomWindowResponse| -|ExpandPSOneLevelResponse| -|GetItemFromIdInput| -|GetItemFromIdResponse| -|GetWorkflowTemplatesInput| -|ItemRevisionOutput| -|RevisionIDs| -|SessionUser| -|TcServerInfo| -|WhereUsedInput| -|WhereUsedResponseInfo| +* `CreateBomWindowInput` +* `CreateBomWindowInput_CreateBomWindowResponse` +* `CreateBomWindowResponse` +* `ExpandPSOneLevelResponse` +* `GetItemFromIdInput` +* `GetItemFromIdResponse` +* `GetWorkflowTemplatesInput` +* `ItemRevisionOutput` +* `RevisionIDs` +* `SessionUser` +* `TcServerInfo` +* `WhereUsedInput` +* `WhereUsedResponseInfo` ## Automatically Migrated Items