We created a project in WorldServer and exported it to a WSXZ package for translation. After opening the package in Trados Studio, the translator locked some segments, such as 100% or ICE Match segments. However, upon importing the translation back to WorldServer as a Return package, those locked segments do not display as locked when opening the task in Browser Workbench.

Interestingly, when these segments are viewed in the Online Editor, they correctly display as locked, just as they do in Trados Studio.

Why are we unable to see the locked segments in Browser Workbench?

The ability to view locked segments in Browser Workbench depends on the configuration of the manual workflow step from which the task is opened. Specifically, if the workflow step has the Static Locking enabled, the user will be able to view locked segments, but not to change their status. If the Dynamic Locking option is enabled, you can lock, unlock, and view segments that have been locked previously, i.e. in Trados Studio.

However, if the human step from which you open the task in Browser Workbench is configured with the No Locking option (which is the default option for ALL human steps), you will neither be able to view locked segments nor lock/unlock segments. This restriction does not apply to Online Editor, where you can view locked segments regardless of the workflow step configuration. However, Online Editor does not allow for locking or unlocking segments, as detailed in this article: