On this page
An integrated MDZipX plugin helps you improve the display of diagrams on the 3DEXPERIENCE platform by exporting them to an MDZipX file. You can use different export options for different types of projects as described below.
You can export diagrams from a local project to an MDZipX file either with or without used project data.
Publishing diagrams to an MDZipX file works only with local projects. |
To export diagrams to an MDZipX file

The exported MDZipX file is saved in the specified target directory.
When working with Teamwork Cloud projects, you can publish all model diagrams to Teamwork Cloud as an MDZipX file. During publishing, each diagram from every project version is saved as an SVG file.
Publishing MDZipX files to Teamwork Cloud works only with Teamwork Cloud projects. |
To publish MDZipX to Teamwork Cloud

When working with projects stored on the 3DEXPERIENCE platform, you can export model diagrams to the SVG format and store them as auxiliary resources inside the model. The SVG files are then retrieved from the model and displayed in the CATIA Systems Traceability Application.
|
To publish diagrams as project assets to the 3DEXPERIENCE platform

You modify the behavior of the MDZipX plugin by changing the environment options under the CATIA Systems Synthesis Analysis group. For example, you can include diagrams from used projects to exported MDZipX files or choose to publish an MDZipX file to Teamwork Cloud automatically upon every project commit.
You can specify the diagram export options, such as dimensions and building time (the latter applies only to tables and matrices), in the Project Options dialog. See the Diagram image export page to learn more. |
To include diagrams from used projects to an MDZipX file or project assets
Publish an MDZipX file to Teamwork Cloud automatically upon project commit
| For more information, please refer to MagicDraw and NoMagic Teamwork Cloud Connectors Configuration. |