How elements are checked out from dynamic views

When you check out an element from a dynamic view, the request is handled as follows:

1. If you are checking out in a UCM view, the view must be set to a UCM activity.
2. If a view-private object already exists with the same name as the element being checked out, you see an error message telling you that it is not a VOB object. Rename or remove the view-private object with a standard operating system command and try the checkout again.
3. If the version being checked out is a derived object (DO version), the checkout attempts to wink in the DO to your view. If the checkout cannot perform the winkin, it copies the DO data instead. For more information about checked-out DO versions, see the DevOps Code ClearCase Guide to Building Software manual.
4. By default, the checkout command selects the most recent version on a branch. If the version-selection rules of your view do not select the latest version in the VOB and you use the command line with the -query option with the checkout command, you are prompted to choose a version to check out.

   Your view may not select the latest version in the VOB if, for example, your config spec selects versions based on labels or time rules.

   If you do not use the -query option, the latest version is checked out without a notification. Use the -version option of the checkout command to check out the version that your view selects, even if it is not the latest in the VOB.

5. The VOB is notified which version of the element that you checked out.
6. For files, an editable view-private file, which is a copy of the checked-out version, is created in the view. For directories, you can add new elements to source control.