Deletion Policy

Introduction

This feature manages the update between the Source and Target environments via three main methods:

• None
• Full
• Partial

IMPORTANT: Each method defines a specific behaviour for updating and handling objects in the two environments.

Note: This feature is accessible via the Deletion Policy button, which allows you to select the preferred update method.

Update methods

Below is a description of the available update methods.

Method	Description
None	It updates the Target only with insertions and updates, without deleting any data in the latter. - Objects that exist on both Source and Target are updated on Target; - Objects that exist in the Source but are missing in the Target are added to the Target; - Objects that exist on Target but are missing in Source are kept on Target (not deleted).
Full	It performs insertions, updates and deletions based on the difference between Source and Target. - Objects that exist on both Source and Target are updated on Target. - Objects that exist in the Source but are missing in the Target are added to the Target. - Objects that exist on Target but are missing in Source are deleted from Target.
Partial	Deletions are limited to objects originating from the use of CDT/MDM - Objects that exist on both Source and Target are updated on Target. - Objects that exist in the Source but are missing in the Target are added to the Target. - Objects that exist on Target but are missing in Source are only deleted if they originate from the use of CDT/MDM.

IMPORTANT: Any changes at the node level will automatically affect settings at a lower level. The settings on the lower elements of the hierarchy can later be changed individually by selecting the specific function.