Concept Description

The workflow described in this section is applicable to all materials (project component and standard materials). The workflow is applicable to cases where one master record is being deleted.

The following points must be noted while performing the integration of delete operations:

• To ensure synchronisation between two applications, deletion performed in one application requires an "approval" from the other if the information has already been transferred.

• If the information has not been transferred, the application owning the data can delete the data without any approval workflow.

• The application that does not own the data cannot delete the data. For example, if AVEVA E3D Design (formerly known as AVEVA Everything3D) transfers standard materials to AVEVA Enterprise Resource Management (AVEVA ERM), AVEVA ERM cannot delete the standard materials, unless the user has admin rights.

The following diagram explains the delete workflow that is applicable when a component created in System 1 was transferred to System 2, and later, System 1 tries to delete the component.

Message topics CanDeleteRequest, CanDeleteAcknowledgement, CanDeleteError and Delete support the delete workflow. These messages contain information about the components and components can be identified by External Ref, when this has a value in the notification.