Viewing Files That are Checked Out—Perforce Helix Core

You can use the Source Control Explorer to view all of the files that you have checked out and need to submit.

How to View Files That You and Others Have Checked Out—Pending Changes Window Pane

  1. Select Source Control > Pending Changes.
  2. The Pending Changes window pane opens.

  3. (Optional) You can use the Filter field to limit the files that are displayed.

    • All Files Displays all translatable files.
    • Topic Files Displays only the topic (HTM and HTML) files.
    • Page Layout Files Displays only the page layout (FLPGL) files.
    • Snippet Files Displays only the snippet (FLSNP) files.
    • Stylesheet Files Displays only the stylesheet (CSS) files.
    • Template Page Files Displays only the template page (FLMSP) files.
    • Image Files Displays only the image files.
  4. (Optional) You can use the following toggle buttons in the local toolbar to limit the files that are displayed.

    This filters the Pending Changes window pane to show or not show files that other users have checked out.

    This filters the Pending Changes window pane to show or not show files that are out of date.

    This filters the Pending Changes window pane to show or not show files that have been deleted.

    This filters the Pending Changes window pane to show or not show files that are locked.

  5. Take note of the Status and User columns. (You may need to use the scroll bar to view these columns.)

    • Status Displays the status of the file, such as whether you have it checked out. You can also see if another user has a file checked out.

      • Checked Out This indicates that the file has been checked out from source control. You can submit the file when you are ready (if you are the user who has checked it out).
      • Pending Add This indicates that you have a file in your project but have not yet added it to Perforce Helix Core. This might occur, for example, if you create a new topic and do not add the file to source control during the topic creation process. To resolve this, simply right-click on the file and select Source Control > Add.
      • Out of Date This indicates that the file is not current (i.e., the local copy of the file is older than the source control copy). This might happen if another user checks out the file, makes changes to it, and checks it back in to source control. If this occurs, you can check the file out or get the latest version of the file from source control.
      • Locked This indicates that a file has been locked by you or another user.

      Note You can click the refresh button Refresh the active window pane. in the local toolbar to make sure you have the most recent status for each file. Another option is that you can use a feature to automatically ping the source control repository periodically, thus refreshing this information frequently. However, you may experience slower performance with this automatic status update option set.

    • User Displays the user name. If you see the name of another user in this column, it means that the file is checked out by that user through source control.

How to View Files That are Checked Out by Others—File List Window Pane

  1. Do one of the following, depending on the part of the user interface you are using:
    • Ribbon Select View > File List.
    • Keyboard Shortcut Press CTRL+SHIFT+J.
  2. (Optional) You can use the Filter field to limit the files that are displayed.

    • All Files Displays all translatable files.
    • Topic Files Displays only the topic (HTM and HTML) files.
    • Page Layout Files Displays only the page layout (FLPGL) files.
    • Snippet Files Displays only the snippet (FLSNP) files.
    • Stylesheet Files Displays only the stylesheet (CSS) files.
    • Template Page Files Displays only the template page (FLMSP) files.
    • Image Files Displays only the image files.
  3. Take note of the Status and User columns. (You may need to use the scroll bar to view these columns.)

    • Status Displays the status of the file, such as whether you have it checked out. You can also see if another user has a file checked out.

      Note You can click the refresh button Refresh the active window pane. in the local toolbar to make sure you have the most recent status for each file. Another option is that you can use a feature to automatically ping the source control repository periodically, thus refreshing this information frequently. However, you may experience slower performance with this automatic status update option set. See Enabling Source Control Status Checks—Perforce Helix Core.

    • User Displays the user name. If you see the name of another user in this column, it means that the file is checked out by that user through source control.

How to View Files That You Have Checked Out—Source Control Explorer

  1. Select View > Source Control Explorer.

    The Source Control Explorer opens.

  2. From the drop-down or the Home pane, select Pending Changes.

    The Pending Changes pane opens. Files that you have changed appear in the Included Changes or Excluded Changes section (depending on whether you are going to include or exclude them in your next submit).

  3. Take note of the file's status. The status is written in brackets next to the file name (e.g., edit, add).

    Note You can click the refresh button Refresh the active window pane. in the local toolbar to make sure you have the most recent status for each file. Another option is that you can use a feature to automatically ping the source control repository periodically, thus refreshing this information frequently. However, you may experience slower performance with this automatic status update option set. See Enabling Source Control Status Checks—Perforce Helix Core.

What’s Noteworthy?

Note When you check out a file from source control, you are actually checking out the file's corresponding XLF file. You will see the XLF file if you open the Source Control Explorer. This is because you need the XLF file available in order to make changes, view the file's history, or view differences.

Note When you modify a file in source control, you may sometimes see a SKL file alongside the XLF and original files. This skeleton file is a placeholder file. Be sure to check in all three associated files together. Checking in just the SKL file may result in errors.