Understanding Object Check In and Check Out

You can check out a UDO that resides in your projects provided that the token for the object is either available or held by the project in which the object currently resides. Only one user at a time can check out an object. Checkout fails if the object is already checked out or if the token is unavailable. If the token is unavailable, you can join the token queue for the desired object. If you join the token queue, you will be notified when the token is available and your project will receive the token.

Check in an object when you want to upload its specifications to the server and make it publicly available. When you check in an object, the system records the project in which the object resides and ensures that only changes made under the current project are transferred when the project is advanced to a status that triggers a transfer.

If an object is checked out, you can erase the checkout. When you erase a checkout, local changes are not uploaded to the server. Erasing the checkout for an object does not release its token, but it does enable other developers who are assigned to the same project to check out the object.

Note: Starting with Tools Release 9.2.7, you can use the web OMW to check in and check out data structure objects.