From 15df0055f68491b051c2aaafb2fbc73ce9e5b5fb Mon Sep 17 00:00:00 2001 From: Bram Brink Date: Wed, 30 Sep 2026 11:28:54 +0200 Subject: [PATCH 1/2] Refer to Teamcenter documentation for standard TC procedures --- .../mendix-client/mendix-inside-teamcenter.md | 25 +++++++++++++------ 1 file changed, 18 insertions(+), 7 deletions(-) diff --git a/content/en/docs/refguide/runtime/mendix-client/mendix-inside-teamcenter.md b/content/en/docs/refguide/runtime/mendix-client/mendix-inside-teamcenter.md index b1f875a1378..97791f9446a 100644 --- a/content/en/docs/refguide/runtime/mendix-client/mendix-inside-teamcenter.md +++ b/content/en/docs/refguide/runtime/mendix-client/mendix-inside-teamcenter.md @@ -112,11 +112,18 @@ The Mendix-inside-Teamcenter Active Workspace component (`MendixEmbedded`) is a 4. Optionally, configure context passing. For more information, see [Passing Context from Teamcenter](#passing-context). 5. Rebuild Active Workspace using `awbuild.cmd`. -To verify the component was picked up correctly, check that its view model entry exists in the `src/repo/out/pathMap.json` registry file in the build output. + +{{% alert color="info" %}} +Installing a kit in the stage repository and rebuilding Active Workspace are standard Teamcenter procedures. If you have issues with these steps, refer to the Teamcenter documentation. +{{% /alert %}} ### Registering the Component on a Page -To display the Mendix app on an Active Workspace page, add its card definition to the relevant `layoutsViewModel.json` file in your Active Workspace stage repository. Set `declarativeKeyContext` to the URL of your Mendix runtime: +To display the Mendix app on an Active Workspace page, add its card definition to the relevant `layoutsViewModel.json` file in your Active Workspace stage repository. Set `declarativeKeyContext` to the URL of your Mendix runtime. + +{{% alert color="info" %}} +Adding a component to a PL Home page is a standard Teamcenter procedure. If you have issues with this step, or need more details on how and where to add an Active Workspace component to a PL Home page, refer to the Teamcenter documentation. +{{% /alert %}} ```json "Mendix": { @@ -138,14 +145,16 @@ To display the Mendix app on an Active Workspace page, add its card definition t * `view` is the name of the Mendix-inside-Teamcenter Active Workspace component obtained in the [previous section](#adding-component), that is "MendixEmbedded" -Add the **Mendix** JSON object (or the name you gave it) to the relevant layout handler grid and rebuild Active Workspace. If the Mendix card does not appear after rebuilding, clear the browser cache to ensure the new chunk is loaded. - -Detailed Active Workspace customization and build steps are outside the scope of this documentation. Refer to the Siemens [Active Workspace Customization](https://docs.sw.siemens.com/en-US/doc/282219420/PL20250520748650994.Configuration/yiv1688486682769) documentation for instructions (link requires authentication). +Add the **Mendix** JSON object (or the name you gave it) to the relevant layout handler grid and rebuild Active Workspace. ### Registering the Component on an XML Rendering Template (XRT) To display the Mendix app on an XRT, add the following to the document using the XRT editor: +{{% alert color="info" %}} +Editing an XRT document is a standard Teamcenter procedure. If you have issues with this step, or need more details on how to edit XRT documents, refer to the Teamcenter documentation. +{{% /alert %}} + ```xml Date: Wed, 30 Sep 2026 11:47:27 +0200 Subject: [PATCH 2/2] Make references a bit more specific --- .../runtime/mendix-client/mendix-inside-teamcenter.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/en/docs/refguide/runtime/mendix-client/mendix-inside-teamcenter.md b/content/en/docs/refguide/runtime/mendix-client/mendix-inside-teamcenter.md index 97791f9446a..4e7c38a274e 100644 --- a/content/en/docs/refguide/runtime/mendix-client/mendix-inside-teamcenter.md +++ b/content/en/docs/refguide/runtime/mendix-client/mendix-inside-teamcenter.md @@ -114,7 +114,7 @@ The Mendix-inside-Teamcenter Active Workspace component (`MendixEmbedded`) is a {{% alert color="info" %}} -Installing a kit in the stage repository and rebuilding Active Workspace are standard Teamcenter procedures. If you have issues with these steps, refer to the Teamcenter documentation. +Installing a kit in the stage repository and rebuilding Active Workspace are standard Teamcenter procedures. If you have issues with these steps, refer to the Siemens Teamcenter Active Workspace Customization documentation. {{% /alert %}} ### Registering the Component on a Page @@ -122,7 +122,7 @@ Installing a kit in the stage repository and rebuilding Active Workspace are sta To display the Mendix app on an Active Workspace page, add its card definition to the relevant `layoutsViewModel.json` file in your Active Workspace stage repository. Set `declarativeKeyContext` to the URL of your Mendix runtime. {{% alert color="info" %}} -Adding a component to a PL Home page is a standard Teamcenter procedure. If you have issues with this step, or need more details on how and where to add an Active Workspace component to a PL Home page, refer to the Teamcenter documentation. +Adding a component to a PL Home page is a standard Teamcenter procedure. If you have issues with this step, or need more details on how and where to add an Active Workspace component to a PL Home page, refer to the Siemens Teamcenter PL Home documentation. {{% /alert %}} ```json @@ -152,7 +152,7 @@ Add the **Mendix** JSON object (or the name you gave it) to the relevant layout To display the Mendix app on an XRT, add the following to the document using the XRT editor: {{% alert color="info" %}} -Editing an XRT document is a standard Teamcenter procedure. If you have issues with this step, or need more details on how to edit XRT documents, refer to the Teamcenter documentation. +Editing an XRT document is a standard Teamcenter procedure. If you have issues with this step, or need more details on how to edit XRT documents, refer to the Siemens Teamcenter XRT documentation. {{% /alert %}} ```xml @@ -183,7 +183,7 @@ Use the browser console CSP errors to identify any additional directives that st After updating the CSP, restart the Teamcenter Process Manager for the changes to take effect. {{% alert color="info" %}} -Editing the gateway configuration and restarting the Process Manager are standard Teamcenter procedures. If you have issues with these steps, refer to the Teamcenter Security documentation. +Editing the gateway configuration and restarting the Process Manager are standard Teamcenter procedures. If you have issues with these steps, refer to the Siemens Teamcenter Security Services documentation. {{% /alert %}} {{% alert color="warning" %}}