About Check-Ins

Document may automatically prompt you to check in a file when you close it. If you are not prompted to check in a file, you can check in the file manually. The factors that determine whether Document prompts you to check in a file automatically are the Check-in file user option and the location where you open the file.

  • The Check-in file user option allows you to select whether Document prompts you to check in a file when you close it. Any time you open a file directly from Document, this option is applied. See Setting Document User Options for more information.
  • Tip: We recommend that you select the Document user option that allows checked-out files to be checked in automatically. This user option streamlines the check-in process. See the Frequently Asked Questions about Check-ins, below, for more information.

  • Document will not prompt you to check in a file if you open it from the Drafts folder on your computer. When you open a file from this location, you must use the manual check-in procedure below.

The file is deleted from your Drafts folder when you check it in. Files stored in managed storage will be assigned a new version number in the file history. Files in extended storage do not receive version numbers. Once the check-in is complete, other staff members will be able to check out and edit the file.

Frequently Asked Questions About Check-Ins

Listed below are some of the most common errors that occur when users check in files. If you receive an error other than these, we recommend contacting your Document administrator.

Error Likely Causes and Suggested Solutions
Check in failed. Error detail: The socket connection was aborted. There may have been a temporary server or network connection issue. First, verify that the file did not check in. (It may have checked in despite the error. )

If it did not check in, check in the file manually.

If the error persists, contact your Document administrator, as there might be a network issue.

The following errors have similar causes and solutions:

  • The process cannot access the file because it is being used by another process.
  • FileName: <Filename> [Direct edit in progress.]
  • FileName: <Filename> [The file is in use by another program. You must close the file before proceeding.]

The file is still open on your local workstation, or the native applicationClosed has not yet released the file. Verify that the file is closed, and then try to manually check in the file.