Using Options (Logical > Physical)
The combination of the "Take account of optimizations" and "Take account of deletions" options varies depending on the scope of objects you wish to update.
Take account of optimizations
When this option is selected, synchronization proposes all creations, deletions and modifications, including optimizations not selected by default at the validation step.
When the option is cleared, only the modifications selected by default are proposed at the validation step.
This option enables filtering of the synchronization result to present only those modifications that have a real impact on target data.
Take account of deletions
When this option is selected, synchronization includes entities, associations and diagrams that have been deleted. Consequently, deletion of corresponding target objects and links is proposed.
When this option is cleared, the entities, associations and diagrams that have been deleted are not included. Consequently, the corresponding target objects are not modified.
This option only applies to entities, associations and diagrams. For other deleted object types (attributes, identifiers, etc. ), the impact on target objects and links is conditioned not by this option, but by the object that contains them.This option enables limitation of impact of a synchronization strictly to the source scope defined by the user, excluding any object not explicitly declared in the scope. This option can be associated with synchronization scope for use case types.
Possible option combinations
1. "Take account of deletions" option selected and complete synchronization scope
This is a use case that favors complete synchronization between source and target. In this case, all objects have a valid mapping on completion of each synchronization wizard operation. This mode should be used when source and target should be totally consistent.
2. "Take account of deletions" option selected and partial synchronization scope
This use case enables working on the selected scope, while including impact of deleted objects. In particular it enables confirmation of deletions of target objects following the deletion of source objects of entity, association or diagram types: as these source objects have been deleted, it is theoretically not possible to include them in the synchronization scope. Selecting this option makes this choice possible. This mode should be favored when the scope is wide, and the few objects excluded from the scope are only excluded temporarily (for example, new objects for which we wish to delay the impact on the target).
3. "Take account of deletions" option selected and empty synchronization scope
This is a special mode enabling "cleanup" of target objects whose mapping is no longer valid, with no other impact.
4. "Take account of deletions" option not selected and partial synchronization scope
This use case enables working strictly on the selected scope, excluding any impact outside this scope. In particular it avoids deletions of target objects following the deletion of source objects of entity, association or diagram types: as these source objects have been deleted, it is theoretically not possible to exclude them in the synchronization scope. Clearing this option makes this choice possible. This mode should be favored for a specific synchronization on a restricted scope, which does not include total consistency of source and target. In addition, it is the fastest mode.
5. "Take account of deletions" option not selected and complete synchronization scope
This combination is in principle an infrequent use case. It corresponds to a work mode in which deletion of source objects has no effect on the target; in other words no target object created is ever deleted when this mode is activated.
6. "Take account of deletions" option not selected and empty synchronization scope
This combination has no effect.