The Share Selected Entities command enables you to pick individual entities in your model and share them with some or all of the members of the workspace. This command is useful when you need to send different parts of your model to different members or if you only want to share specific entities in your model.
You can select specific entities either from the model or by picking them from the Specification Tree. When you share selected entities, the application adds to the briefcase all parents information with the update. Sending the parents information ensures that the entities are merged correctly into the models of recipients. For more information about sharing bodies and other type of entities, refer to the paragraphs below.
During sharing/merging of features, sharing of features depends on its
relationship roles with explicitly shared features. To assure the changes
are reflected in target document after you perform the
Share/Merge operation, it
is recommended to explicitly share the required feature.|
It is possible to insert GSD features into a briefcase. The Instant Collaboration is performed at the feature level. It means that each feature can be shared without its aggregating body.
Two designers can divide the initial geometrical body in 2 parts (blue and yellow curves).
Then each one will be able to create his own features (blue and yellow surfaces).
And finally, the created specifications can be merged together into the initial body (green surface).
When merging features into a different type of set, the behavior is identical to the creation: The result is similar to a manual creation of the involved features.
When merging a feature that does not exist already in the part, the following rules are used when applying a briefcase: if the destination part does not already contain the Geometrical set to which the feature belongs, the set will be created before inserting the feature. If the Set already exists, the feature will be added to it.
In an ordered geometrical set, merging is based on the "In Work Object" concept.
It is possible to insert Part Design features into a briefcase. Instant Collaboration is performed at the hybrid body level, because Part Design features are historic dependent.
Only sketches can be shared and merged explicitly without the aggregating hybrid body if it does not depend on other part design features.
It is possible to insert Functional Design features (created in the Functional Molded Part workbench) into a briefcase. Instant Collaboration is performed at the functional specification feature level. It means that a briefcase can contain functional specifications without any functional body or functional solid. If a sketch built on the result of a functional specification is shared, this functional specification and recursively its dependencies will be embedded into the message.
Datum features based on V4 geometry and V5 geometry are supported.
Sharing a datum feature means sharing "frozen geometry" without design specification and without links to the entities that were used to create this element (History mode deactivated). A Datum is always made up of a feature (a proxy), and of geometrical elements.
Sharing features containing links to external references, such as contextual links, copy with links and copy as result with link, the result of the link is inserted in the briefcase and the external reference is ignored. On the merge side, a datum is created. This method for sharing external references is referred to as deprecated share.
To protect the information about external references in a bi-directional exchange of briefcases, the following rules apply during the merge:
To better understand this rules consider the following example:
Normally when a briefcase containing a geometrical set or a functional set is merged in to a part that already has a copy of them, the list of features of the two versions are combined. For instance, if the briefcase contains a Geometrical Set named My Sketches that contains the sketches Sketch.1, Skecth.2 and Sketch.3 and the part contains the same set with the sketches Sketch.2 and Sketch.4, after the merge part will contain Sketch.1, Skecth.2, Sketch.3 and Sketch.4. More precisely: Skecth.1 is added to the part; Skecth.2 and Sketch.3 are replaced with the version form the briefcase; Sketch.4 is left untouched.
You can modify this behavior using the Share Assistant.