Checking out an object opens it for editing, and locks it for modification by other users. Checking in an object saves any changes in the repository and makes the modified object available for other users to view or make additional changes.
When you check out an unstructured file, the entire file is locked. You can check out a structured document, or you can use a fragment editor to check out locking units or elements contained by a structured document.
For the oXygen editor and XMetaL users, when you check out an object, a copy of that object is saved in the local file system Sandbox folder. You can save changes you make to the object in the sandbox while the object is open for editing. When you check in the object, the copy is removed from the Sandbox. See About the Oxygen Sandbox and About the XMetaL Sandbox.
The My Checkouts view lists all objects you have checked out. You may need to refresh the My Checkouts view to ensure it is in sync with the repository.
If a structured document is checked out by another user, and you view the object in the repository, you will see the last version of the object that was checked into the repository.
Assuming you don't specify any filtering, if an object is checked out, and you compose output from the object, the output will contain the last version of the object and referenced objects that are checked into the repository. However, if you have saved any objects to the repository, your repository saved data will also be included in your composition (but not saves from any other users).
The Global Substitution tool can check out candidate objects and modify them. When the process completes, the objects can either be left checked out so the changes can be validated, or checked in automatically. If an object is identified for modification using the Global Substitution tool, but the object is checked out, processing skips the object and issues an error in the job notification log. See About Checking In Global Substitution Changes.