To check out hijacked files now

About this task

If you do not convert the hijacked files to checkouts now, you may lose the opportunity to automatically merge the changes in those files. When you load a file into your view, the version of the element that is copied into your view is recorded. A warning is displayed after the following sequence of events:
  • You hijack a file.
  • You update your view, and the following occurs:
    • The view config spec selects a different version of the file you hijacked.
    • The Update Tool update options are set to leave hijacked files in place.
  • Because of the options that you specified in the Update Tool, the version that the config spec selects is not copied into your view. (The version that the config spec selects is recorded.)
  • Because the version that you originally hijacked is no longer recorded, you cannot check out the hijacked file.

Take the following actions:

Procedure

  1. When the warning message is displayed, click No.
  2. In the Update window, click the Hijacked folder to display all the hijacked files in your view.
  3. In the right pane, compare the Old Version and New Version columns. If the versions in the two columns are different, move to the Name column and right-click the hijacked file.
  4. Do one of the following:
    • To keep your modifications, right-click the version and click Check Out. You are guided through the merging of the file with the version that the config spec selects.
    • To overwrite the hijacked file with the version your config spec selects, right-click the version and click Undo Hijacked File. The hijacked file is updated.
    • To keep the file hijacked in your view, take note of the version ID in the Old Version column and close the Snapshot View Update window. Check in the changes in the hijacked file. This involves checking in a version that your view no longer selects.