One classical pitfall is to export models (libraries and projects) that are linked by “reference” relationship one by one. Rather, export of linked models must be done at the same time because doing it one by one may lead to the export of still exported models. For the sake of illustration, having two projects P1 and P2 referencing library L1 may lead to one re-export of L1 if one tries to export P2 after having exported P1. The following section describes the correct procedure.
We assume in this section that a Team for Capella Client is opened and its workspace contains a set of models (projects and libraries) that are interconnected by the way of reference links.
In that context, the export procedure is as follow:
Figure below illustrates the four steps described above in the given context:
Libraries can be accessed as classic remote projects with Team for Capella and have almost the same behavior as with Capella standalone:
It is allowed to open, in the same client, a project and some libraries it references. Thus it is possible to have 2 views (or more) of the same semantic elements:
If a library is referenced with a “readAndWrite” access policy, it is allowed to change its semantic model from the project connection, from P1.team in this example:
Even if the user is logged with the same login to L1 and to P1, if a change is done on one side, there will be a green lock on this side and a red lock on the other (so concurrent changes are forbidden on library’s elements).