Object Locking

To prevent multiple authors from trying to modify the same object at the same time, objects are locked when they are opened or checked out.

• A local lock is placed on an object when it is opened, and removed when the object is closed. Other authors will be able to open the object during this period but will not be able to edit it. If the computer that has an object locked does not close the object correctly (crash, power off without correctly exiting, network problem etc) then the lock should clear after five minutes. Failing that, the administrator can clear the object locks.

  A local lock is indicated by in the object list.

• An offline lock is placed on an object when it is checked-out to an offline library and removed when the library is checked back in. In the offline library, all objects that were not checked-out have locks placed on them so that they may not be modified. The administrator may clear the object locks associated with an offline library, which will free up the objects but prevent the offline library being checked-in again.

  An offline lock (checked-out object) is indicated by in the object list.

• A lock is also placed on an object in a Target library when it is exported as part of a translation job and removed once the job is imported. The administrator may clear the object locks associated with a translation job but this will prevent the translation job from being imported.

To see who has an object locked, open the object and the locking information is displayed as part of the title bar.