Automated usages of other projects in the main project are the usages fully managed by our modeling tool. For example, it can create, remove, and rearrange as necessary without user intervention.

Version 17.0.3 and later

Version 17.0.3 introduces a new type of project usages, automated project usages. Our modeling tool fully manages them. It creates, removes, and rearranges as necessary without user intervention. Automated project usages are not shown in the Used Project dialog as only user-defined usages are shown there.

Before version 17.0.3

In earlier versions of our modeling tool, there was only one type of project usage. The user created these user-defined usages and they carried additional parameters; i.e., whether the used project was used in read-only or read/write mode, the used project loading options, which used project version was required, etc.

When modifying projects with complex composition, always keep the following condition in mind:

Whenever there are model level references from elements in resource A (either a used project or the main project) to elements in resource B, there is a used project usage A → B.

In earlier versions of our modeling tool, you could see this condition in action when working with used projects in read/write mode. Whenever you modified the contents of a used project so that it started to refer to another used project, and then you attempted to save it, our modeling tool would add an additional usage. You would then see the messages: “Used project B was directly attached to A” or “Mounts were updated ...”.

However, in some cases, this system behavior caused undesirable consequences, as shown in the following pages: