![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
More on Private Check Out (Apex/Summit)A private check out does not obtain an exclusive reservation on the version history associated with a controlled file. This allows you to check out files privately, even if a file associated with the same version history is checked out in another view. This is useful when you want to make changes to a file that is already checked out.
Under private check out, a file carries the status of private. Its version number is the same as the number of the version from which it was created.
Checking in Files that Have Been Privately Checked Out
You can merge a private file back into the version history. The amount of effort depends on changes that have made to other versions of the file.
No Changes to Version History
If there was no reservation on the files history when you performed the private check out, if the private check out was based on the latest version and if the history has not been reserved since, then the version number of the privately checked out file coincides with the latest number in the version history. You can check in your private copy as though you had performed a normal check out. Follow these steps:
- 1. . Select Control > Check In (Apex/Summit).
- 2. . In the Check In dialog box, make certain the pathname of the private file appears in the selection (right) scroll list.
- 3. . Click on OK.
If Version History Has Changed
If the private file's version number is no longer the latest in the version history, follow these steps.
- 1. . Make certain the latest version is checked in.
- 2. . Select Control > Merge (Apex/Summit).
- 3. . In the Merge dialog box, make sure that the Object fields name the privately checked out files. The Version fields will specify, by default, that the current version (the private version) will be merged with the latest version. The Common Ancestor > Compute Automatically button will base the merge on the version from which the file was privately checked out.
- 4. . Click on OK.
- The result of the merge will be placed in filename.merged.
- The file filename.merged will be brought up in an editor that will allow you to review the results and resolve any conflicts.
Once the displayed merged file is satisfactory, choose File > Save and then Merge > Copy Onto Object 1 menu item to copy the merged result onto the privately checked out file.
Finally, check in the merged result by the following steps:
- 1. . Select Control > Check Out (Apex/Summit) and in the resulting Check Out dialog, set the options Upgrade private check-out to full and Keep the current version of each object. This will upgrade the private check out to a check out with a reservation and retain the merged contents.
- 2. . Select Control > Check In (Apex/Summit) to check in the merged version.
More information on private check out and version control can be found in Using and Customizing Summit/CM, and the Concepts Guide.
Additional Topics
Rational Software Corporation http://www.rational.com support@rational.com techpubs@rational.com Copyright © 1993-2001, Rational Software Corporation. All rights reserved. |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |