View Source

The structure of your model may change when switching back and forth between local and server projects. Usually, this happens when the local project is added to the server, the server project is saved locally, or the server project is updated with local changes.

From Teamwork Cloud to local project

When the Teamwork Cloud project containing used projects is saved locally, packages from used projects are mounted under the model root () and marked with the(shared package) symbol. The original model structure (as it is in the server project) cannot be maintained due to model architecture limitations, i.e., the absence of the dedicated root node for used projects.

MagicDraw 19.0 LTR SP3 > Understanding differences in local and server project structure > projects_saved_from_TWC.png

In the local environment, only shared packages will be visible in the used project. Therefore, if the used project contains elements under the model root, a new package <userProjectName>_shared is created when you save the project to make it possible to share those elements.

MagicDraw 19.0 LTR SP3 > Understanding differences in local and server project structure > shared_package_local_project.png

From local project to Teamwork Cloud

Mount relationship

The Mount relationship may be created when the server project containing used projects is saved locally, modified, and then added back to the server.

It is used to recreate the same structure of the Containment tree as it was originally in the local project. This may be important for features that use a defined scope of the model. Only elements from used projects that are mounted under the Model root ( MagicDraw 19.0 LTR SP3 > Understanding differences in local and server project structure > model_root.png ) or any of its packages are considered part of the model scope (when no used projects are set as the scope).

In general, the Mount relationship enables you to create a visual copy/representation of the chosen package in any place in the model.

MagicDraw 19.0 LTR SP3 > Understanding differences in local and server project structure > mount_relationship.png

You can delete Mount relationships from your project if, for example, you do not want to have duplicate packages in the Containment tree of your server project.

Deleting Mount relationships may affect diagrams, elements or other options that require specifying the scope since packages from used projects will no longer be under the main project model root (they will still be available under Project Usages).

If you do not want Mount relationships to be created by default, remove the tick from the Maintain Mount Points of Used Projects checkbox in the Update from Local Project (Collaborate > Update from Local Project) dialog.

MagicDraw 19.0 LTR SP3 > Understanding differences in local and server project structure > update_from_local_project_dialog_structure_drift.png

Packages from used projects mounted under the model root or any of its packages via the Used Projects dialog are kept in their original locations by using Mount relationships. They are automatically created once the project is added to the server.

Project Usages

The root node Project Usages is created in the Containment tree in Teamwork Cloud projects to list all used projects. The entire used project version is visible in the project.
MagicDraw 19.0 LTR SP3 > Understanding differences in local and server project structure > project_usages_package_TWC.png

Symbols used

Symbol	Description
	Indicates that a package belonging to the used project is shared.
	Indicates that a shared package belongs to the opened project.
//	Indicates that there is a package/profile/model from the used project in the Teamwork Cloud project.
	Packages from used projects have the project name they come from written in brackets.

For additional markings that can be displayed in used projects, refer to pages Moving elements to other projects and Working with partially loaded projects.