WorldServer - if I unlock a locked segment coming from a locked TM entry in Studio, change the translation, confirm and then import the Return package, will the locked TM entry be translated?

In our WorldServer project we have several segments (mostly ICE) that are automatically locked after segmentation. The reason for the locking is that the 100% or ICE Match translation comes from a locked TM entry.

Once I export the project or task to a WSXZ package, I can see the same locked segments in Studio. In Studio I can unlock them and update the translation. If I do so, will the translation be imported to WorldServer?
Will a new TM entry be created or will the locked TM entry be updated?

If the locked segment comes from a locked TM entry, if you unlock the segment in Trados Studio, change the translation, and import a Return package back, the changed translation will be imported and will display in the target segment if you open the Task in Browser Workbench or in Online Editor. It will also display in the target file created during the import or a Save/Save Target step.

However: the locked TM entry will NOT be updated with this change. That is because locked TM entries are not supposed to be changed.

If you need to make changes on locked segments coming from a locked TM entry, make sure that the TM entry is unlocked first. You can also prevent the locking of the TM entries in general by setting this property to false in tm.properties:

enable_tm_entry_locking_for_locked_segments=false

With this property set to false, a "normal" (unlocked) TM entry based on a new translation will always be created even if the translated segment it comes from is locked. The locked segment status will be ignored.
Remember that existing locked TM entries will still not be updated when changing a translation of a target segment whose translation comes from a locked TM entry, for instance as a 100% Match.

For example, if - after segmentation - some of your segments get a 100% or ICE Match from locked TM entries and are pre-translated normally during segmentation if you change the translation of those segments in Studio or Browser Workbench, the locked TM entries will not change or be updated. The change will only apply to the target segment and - after a Save - to the target file. Therefore, if you are not confident that locked TM entries should never be changed, you should set the property to false and - possibly - consider unlocking all existing locked TM entries, following this article:

WorldServer: How to unlock locked entries in a Translation Memory as Batch

 

These articles is relevant:

How are locked Translation Memory Entries created in WorldServer?

WorldServer: How to unlock locked entries in a Translation Memory as Batch