About Site Ownership

This section explains how the delegation process works using the Export and Import commands, and how the site ownership of the entities is managed using the Detach and Revoke commands.

Using the delegation process, the receiver can temporarily access the repository for modifying objects. Site ownership allows you to determine the site ownership status of the selected entity.

Note: When the Site Management command is launched from the search, only the selected object is taken as input for the command. When it is launched from another workbench, all visible objects are taken as input for the command. Therefore, there can be different behaviors depending on where you launched the command from.

This page discusses:

See Also
About 3D XML

Delegate

The Export command enables you to export, and delegate the selected objects as a 3D XML file. You can revoke that delegation once the data is sent with a delegation. The repository that imports this 3D XML with authoring can modify the Core Data (CD), and the Extended Enterprise (EE) attributes of the object. You must have the Author and Leader baseline access roles to delegate objects.

You need permission to modify the object on a distant site to execute the delegation process. The PLMBriefcase (3D XML with authoring) carries this permission and later adds the permission to the PLMBriefcase while exporting a 3D XML file with the authoring command (export with delegation). The receiver of a PLMBriefcase containing the delegation can edit the data (import a delegation). Only the modifications done under this permission can be imported into a grantor repository.

You can import the required permission to several repositories, as the permission is not restricted to a specific receiver.

Edit Token Status

The edition token status explains the data modification rights.

The edition token status is specified as LOCAL for a created data, and DISTANT for a data imported as a reference. You can edit the CD and EE attributes for the created data. But, for the imported data, the CD attributes of the data are not editable. You can modify the EE attributes.

You cannot apply Export with delegation for an object, whose edition token status is set as FORWARD.

Note: You can edit the CD attributes of the object, if the edition token status is specify to either LOCAL or DELEGATED.

The following table explains the edition token status for implementing the delegation:

Status Description
LOCAL The edition token is owned locally, no transfer.
DELEGATOR The object is owned locally, and the edition token is delegated to another repository.
RESERVED The edition token owned is still local, but the transfer is reserved.
FORWARD The ownership of the object is owned in another repository, and the edition token is delegated to an another repository.
DELEGATED The ownership of the object is owned in another repository, and the edition token is owned locally by a delegation.
DISTANT The edition token is not owned locally, no transfer.

Detach and Revoke

The Detach command enables you to remove the selected components that are not owned by the local site from the database. The Revoke command enables the emitter to revoke the delegation without any notification. You must have the Author and Leader baseline access roles to detach and revoke objects.

You can save the Detach operation to all the aggregated components if the Propagate to all Children option is selected. Aggregated components can be aggregated instances (representations and products), aggregated representations, connections, and ports.

If you detach the references (representations and products), all the instances of the references are detached. As a result, the links referring to the detached components are broken, and the components are physically removed from the repository.

If a delegation is revoked, the import operation fails and requests the receiver to detach his own modifications from its repository. The delegation operation fails if you delegate an already delegated object, without revoking the previous delegation.

The following objects can be detached:

  • 3DPart Reference (Aggregating Ref)
  • Aggregated Product RepReference
  • Applicative Connections (composed)
  • Publications (composed)

The following objects can be transferred:

  • 3DPart Shape (Aggregated)
  • PrivateRep (Related)
  • Publications (composed)

The Delegation / Waive / Revoke commands enable you to modify the ownership of objects. These modifications are done independently from the session. Therefore, if the objects stay in session during these operations, the modifications are not reported to the session. When you save, the Delegation/Waive/Revoke transaction modifies the data state, which is independent from what happens in the session.

To avoid these issues, do a "Global Refresh" after each delegation / waive / revoke operation to update the session.

For more information about Detach and Revoke, see Working with Immersive Site Ownership.

Your administrator can repair the site ownership of objects by forcing them to the Local or Distant status. For more information, see Administration: Repairing the Site Ownership of Objects.

Waive

The Waive operation automates the revoke action at the OEM side when a 3D XML file is received from a supplier. The supplier waives the object during an export started by the supplier. When a waive operation is in process, the data state is specified as WAIVED on the delegated site. The state changes to DISTANT only after an acknowledgement from the delegator site. You must have the Author and Leader baseline access roles to waive objects. You (Supplier) can abandon the write access on the objects if:

  • You are not supposed to get privilege on the objects.
  • You have done your modifications, and want to stop working on the objects.