Repository Guide

10.5.7
- 10.5.6
- 10.5.4
- 10.5.1
- 10.5
- 10.4.0

Back Next

Example of a Frequently Checked-Out Composite Object

You update the mapping m_Payroll often, and you frequently check it in and out. Five checked-in versions of the mapping exist. You rarely modify the source and target objects in the mapping. There are three checked-in versions of the source and one checked-in version of the target.

At the repository level, you purge versions based on criteria, and you indicate that you want to keep the last two checked-in versions of objects.

The following figure shows the history of versions 1 through 5 of the mapping:

M_Payroll version 1 has version 1 of the source and target. M_Payroll version 2 has version 2 of the source and version 1 of the target. M_Payroll version 3 has version 2 of the source and version 1 of the target. M_Payroll version 4 has version 2 of the source and version 1 of the target. M_Payroll version 5 has version 3 of the source and version 1 of the target.

The advanced purge produces the following results:

Object	Purged Versions
Mapping m_Payroll	Versions 1 through 3, assuming that no Session task or other composite object uses m_Payroll.
Source	Version 1. Because you purge the version of m_Payroll that uses source version 1, you also purge that version of the source. The purge keeps the last two checked-in versions of objects, so you do not purge versions 2 and 3 of the source.
Target	None. The purge keeps the last two checked-in versions of objects. Only one checked-in version of the target exists.

Rename Saved Search

Table of Contents

Repository Guide

Repository Guide

Example of a Frequently Checked-Out Composite Object

Example of a Frequently Checked-Out Composite Object