Locking When Translating Worklists 

Use

The lock mechanism can only be used to coordinate translation worklists (see below, Functionality).

A worklist is not locked during translation. This means that a lock is not triggered when a translator works on a worklist. The worklist can be translated simultaneously by another translator, whereby the two translators can overwrite their translations when they are saved.

Features

The lock mechanism works in the usual way for worklist coordination: If you want to edit a worklist that is locked by another user, you can only open the worklist in read-only mode. With the Edit Mode pushbutton you can try to return to edit mode. See also Locking Objects (Lock Scenarios).

An object in a worklist can also be included in another worklist in parallel. An object is not locked when it is in a worklist. You should therefore create worklists whose objects do not overlap. When you create the worklists, you should make sure that each object is in one worklist only, and not in multiple worklists. If not, newly translated object texts might be overwritten with obsolete or undesirable versions when they are published. You can prevent this by assigning namespace prefixes. The worklist should have a certain namespace prefix and only contain objects belonging to this namespace.