Document Mendix inside Teamcenter (public Beta, 11.12)#11384
Conversation
|
Jonathan Diehl seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
wanchoorohan
left a comment
There was a problem hiding this comment.
Provided few suggestions.
|
@jdiehl |
MarkvanMents
left a comment
There was a problem hiding this comment.
I started reviewing this, but realize that there are a lot of things which are still awaiting confirmation/more documentation.
Can you let me know when this is ready for me to do more work on it?
|
I resolved all comments. @MarkvanMents can you continue your review? |
|
Thanks. Working on this. I'll let you know if I have any questions. |
Fixes grammar, punctuation, formatting, and clarity in the Mendix Inside Teamcenter feature documentation and cross-reference in the Teamcenter Connector page. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
MarkvanMents
left a comment
There was a problem hiding this comment.
Thanks for this PR @jdiehl, @brambrink, and @wanchoorohan
I've done some proofreading and have a number of questions/suggestions.
I have also asked @NicoletaComan to have a quick look as she is familiar with the Teamcenter documentation.
Please let me know if you have any questions about my changes in ad233c0.
|
|
||
| | | Mendix | Teamcenter | Teamcenter Connector | | ||
| | --- | --- | --- | --- | | ||
| | **Beta** | 11.12 | 2512 | 2606.0.0 or above | |
There was a problem hiding this comment.
I still don't see this connector version in the Marketplace.
There was a problem hiding this comment.
This is planned for release in a few weeks. We could either explain that here (and remove the comment when it is released) or wait with the release of this PR until it is available.
|
|
||
| #### CORS for TcSSO Published REST Service | ||
|
|
||
| Configure the [CORS settings](/refguide/cors-settings/) for the TcSSO Published REST Service that is included in the Teamcenter Connector and add your teamcenter host `https://your-teamcenter.example.com` to the Allowed Origins. |
There was a problem hiding this comment.
Imported the Teamcenter Connector but couldn't find where to change this setting. I couldn't see a Published REST Service as part of TcConnector 2512.1.1. Is it in 2606, or am I looking in the wrong place?
There was a problem hiding this comment.
@wanchoorohan Is the TcSSO published rest service added in 2606?
There was a problem hiding this comment.
The PRS is under Internal\Resources\ServiceHandlers\TCSSO
| To display the Mendix app on an Active Workspace page, add a card definition for it to the relevant `layoutsViewModel.json` file in your Active Workspace stage repository. Set `declarativeKeyContext` to the URL of your Mendix runtime: | ||
|
|
||
| ```json | ||
| "Mendix": { |
There was a problem hiding this comment.
I assume this is just an example name? I think we should make it clearer that this is an example.
There was a problem hiding this comment.
@brambrink Can you explain which part developers can customize and which part they cannot? I assume the key name and Title can be changed.
There was a problem hiding this comment.
Developer can choose any name they want, as long as it is not in use already. This key is used for referencing this 'card' in the layout later. Technically, it is an example, but there is not really a good reason to change 'Mendix' to something else in my opinion.
| } | ||
| ``` | ||
|
|
||
| Add `"Mendix"` 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. |
There was a problem hiding this comment.
Is this "Mendix" as in the json object, or "Mendix" as in the "title" of the json object?
There was a problem hiding this comment.
'Mendix' as in the JSON object
|
|
||
| ## Known Limitations (Beta) | ||
|
|
||
| * **Cross-site cookies:** The browser must allow cross-site cookies for the Mendix domain. This is required because the Mendix app runs on a different origin than Active Workspace. Configure this per-domain via organization policy (for example, Intune). |
There was a problem hiding this comment.
Is this really a limitation? It is not something that we can even change so I would say it is a prerequisite.
…eamcenter.md Co-authored-by: Mark van Ments <35492184+MarkvanMents@users.noreply.github.com>
|
|
||
| ```json | ||
| "Mendix": { | ||
| "title": "Mendix", |
…n Mendix Inside Teamcenter documentation

Description
New reference page under
/refguide/mendix-client/mendix-inside-teamcenter/documenting how to embed a Mendix web app as a native component inside Siemens Teamcenter Active Workspace using the embedded client.This builds on the embedded client documentation added by @WimJongeneel in #11204 and is tied to the 11.12 release.
Changes
refguide/runtime/mendix-client/mendix-inside-teamcenter.mdrefguide/runtime/mendix-client/_index.mdwith a cross-reference to the new pageCoverage
The new page covers:
MendixEmbeddedAWC component and registering it on a pagegateway/config.jsondirectives)