Issues resolved in WorldServer 11.2.0

An overview of the issues that have been resolved in WorldServer 11.2.0.

ComponentIDDescription
SDL Trados Studio integrationWSXI-7661SDL Trados Studio truncates the names of WorldServer translation kits that have more than 50 characters. If you export multiple translation kits with long names that have the same root, a unique numeric identifier is added at the end of each file, so that the names are still different after they are truncated.

Moreover, if you export a translation kit that contains files with the same name, but with a different casing (such as file.txt and File.txt), a unique numeric identifier is also added at the end of each file.

To benefit from this fix, you need to export the translation kits from WorldServer 11.1 or later and open them in SDL Trados Studio 2015 SR3 or later or in SDL Trados Studio 2017 CU5 or later. For more information about cumulative updates in SDL Trados Studio 2017, click here.
CRQ-5062In certain cases, when importing WSXZ translation kits into SDL Trados Studio, translation memories were not created in SDL Trados Studio due to the length of their names. To prevent this from happening, the names of the translation memories exported in WSXZ translation kits are now truncated.

To benefit from this fix, you need to open the translation kits in SDL Trados Studio 2017 CU6 or later.

For more information about cumulative updates in SDL Trados Studio 2017, click here.
CRQ-5248If you export WSXZ translation kits that contain invalid XML characters, you can now import them back into WorldServer successfully.
WSXI-7462After you upgrade from WorldServer 10.4.3 to WorldServer 11.1 or later, you can import translation kits from SDL Trados Studio that contain XML assets segmented with the Custom XML (Legacy Embedded Content) File Type.
CRQ-4174Culture codes have been added in the exchange.properties file for multiple languages, such as Arabic, Chinese, Dutch, English, French, German, Italian, Macedonian, Malay, Norwegian, Portuguese, Spanish, and Uzbek. You can only export translation kits for SDL Trados Studio if both languages in the language pair have a culture code.
File types and segmentationWS-7653If your instance of the File Type Support (FTS) Server is connected to an Oracle database, you can now make certain configurations to avoid ORA-01002: fetch out of sequence messages when the FTS Server processes your assets. For more information, see FTS Server configurations for Oracle databases.
WSXI-7237The number of situations where tasks remain stuck in a workflow during asynchronous automatic actions (such as Segment Asset or Save) has been reduced.
CRQ-3799In XML assets processed with the OASIS DITA XML file type, the spacing is now preserved properly before locked content that is in the same segment in WorldServer, but on different lines in the source asset. The same applies to the spacing before empty tag pairs that are in the same segment in WorldServer, but on different lines in the source asset.
WSXI-8326The <fn> elements are no longer duplicated in target files if the original element begins in one segment and ends in another and the source asset is in Japanese and has been segmented with one of the following file types: OASIS DITA XML or Custom XML (Embedded Content Processor).
LTB-461An issue with namespaces in XML assets with XPath rules that contain functions has been fixed.
LTB-1726When configuring Custom XML file types, if you set CDATA Section as a translatable rule under Parser and select Process embedded content found in CDATA sections under Embedded Content, the target assets segmented with those file types are valid and no longer contain unnecessary tags when you export them.
WSXI-8019Segments that come immediately after CDATA sections are no longer extracted for translation twice when the assets they are part of are segmented with the Custom XML (Embedded Content Processor) file type.
CRQ-4469The File Type Support (FTS) Server can now process translatable content when DOCX assets contain TW4winExternal/Internal Styles and are segmented with the Microsoft Word 2007-2016 File Type.
WSXI-8458XML assets containing single quotation marks (') inside of comments are now segmented successfully.
WSXI-7921Placeholders are no longer missing when XML assets are segmented with file types from the XML family.
LTB-1792An issue related to opening DITA files has been fixed.
CRQ-4126, CRQ-4216Certain issues related to how the File Type Support (FTS) Server processes locked content in XML assets have been fixed.
User assignmentsWSXI-8619If none of the users assigned to a human step in a workflow can be assigned to a task, the task is assigned automatically to all the administrators in the system and the task history now indicates the reason of this assignment. To be assigned to a task, users need to match the target locale of the task and to be part of the workgroup of the project type.
CRQ-4114If a workflow reaches a step assigned both to specific users and to workflow roles, some tasks are no longer assigned only to the workflow roles; they are now assigned to the users as well.
CRQ-4255After a workflow reaches a human step assigned to specific users or workflow roles, the number of projects and tasks assigned to them is updated and the new projects and tasks are displayed correctly when selecting projects assigned to me and tasks assigned to me.
WSXI-8604Project tasks are now assigned properly if the Submitter role is used in multiple human steps from the same workflow.
User interfaceWSXI-7838The information in the new Create Project wizard for WorldServer TransPort is now displayed properly when the Compatibility View is enabled in Internet Explorer 11.
CRQ-4352Quotes and other characters are no longer converted to HTML entities on the terminology pages.
CRQ-5061A missing flag image has been added for the Spanish (Latin America) locale.
Upgrade scriptsCRQ-4533Added a performance improvement to the Microsoft SQL Server upgrade script from WorldServer 11.1.0 to WorldServer 11.1.1 (WS-Upgrade-11.1.0-to-11.1.1.ms.sql).
CRQ-4526The order in which operations are executed in the Microsoft SQL Server upgrade scripts from WorldServer 11.0.1 to WorldServer 11.1.0 (WS-Upgrade-11.0.1-to-11.1.0.ms.sql) and from WorldServer 11.1.0 to WorldServer 11.1.1 (WS-Upgrade-11.1.0-to-11.1.1.ms.sql) has been improved.
CRQ-4535When upgrading from WorldServer 11.1.0 to WorldServer 11.1.1 on Microsoft SQL Server environments, the issuesST index created in the database is no longer unique.
CRQ-4554The workgroupid column is now included in the taskStepRoles table when you upgrade from versions earlier than 11.1.0 to WorldServer 11.1.1 on Oracle environments.
Project creationCRQ-4928An issue related to projects not being created through the wizard due to a potential database deadlock that only occurred in certain circumstances has been fixed.
CRQ-4048You can now upload nested ZIP files successfully when you use the WorldServer11.x user interface to create projects on Amazon Web Services (AWS) environments running on Linux.
PerformanceCRQ-5010Database operations such as deleting multiple users from workgroups or workflow roles now take less time to complete.
Project attributesWSXI-4941On Mozilla Firefox and Google Chrome, custom project attributes are not displayed in search results if they contain extra spaces. Thus, all the extra spaces found at the beginning or at the end of newly created custom project attributes are now removed automatically. To have these spaces removed from existing attributes as well, you need to open each attribute and save it without making any changes.
Project typesCRQ-4214The Please provide all required values for advanced MT configuration mappings message is no longer displayed when you save new or updated project types that include advanced options for machine translation configurations.
QuotesCRQ-3950You can now remove files added to the Quote Document(s) section when you create or modify quotes.
Translation memoriesCRQ-5247A more specific message is displayed when you try to save assets that contain 100% matches with out of order placeholders. The new message indicates the exact segments that contain invalid TM entries, so that you can fix them.
APICRQ-5121An issue related to improper POST requests and unreturned connection leases on the login page of newly upgraded systems has been fixed.