Salesforce

WorldServer - proposed TD entries are not being exported to Studio package

« Go Back

Information

 
Article TypeSolution Article
Scope/EnvironmentWorldServer
Symptoms/Context
A WorldServer project is associated with a Term Database that includes both Active (Approved) and Proposed terms. After exporting the project to a WSXZ package for translation and opening it in Trados Studio, we noticed that proposed terms are not being displayed.
Resolution
If you want Proposed term entries to be exported with the WSXZ package, uncomment the relevant property multiterm.export.proposed.terms in exchange.properties file and set it to true, as follows:
 
multiterm.export.proposed.terms = true

Remember to restart the Idiom service for the change to take effect. Usually, you would not want rejected terms to be exported, but if you want them to be exported as well, uncomment and set the appropriate property to true as well as displayed here:
 
multiterm.export.rejected.terms = true

Note: if - for some reason - through an upgrade from earlier versions to version 11.1.0 or later (which is when these properties were introduced) you do not see these properties in your exchange.properties file, just add them to the file as explained above. 

Moreover, if your environment is a clustered/multi-server environment, make sure that this property is enabled on all servers where Idiom is running.
Root Cause
Per default, WorldServer exports only Active (Approved) terms. However, starting from WorldServer 11.1.0, these 2 properties were added to exchange.properties, allowing you to export terms in different statuses as well, if required:
#Export terms in wsxz kits

#export proposed TD terms
#multiterm.export.proposed.terms = false
#export rejected TD terms
#multiterm.export.rejected.terms = false

These properties are set to false per default, but they can be changed to true if you want terms in Proposed and/or in Rejected status to be exported as well.

Note: even if the properties are called multiterm.export.xxxx, these properties are related to both Worldserver native Term Databases and Multiterm Databases.
Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by