Connector for SAP Commerce Release Notes

  15 minute read  

You can view cumulative release notes on this page or download release notes for a particular release as a PDF file.

Note about PDFs: These files require Adobe Acrobat Reader.

Version 3.2.9
What’s New?
  • Added backward compatibility to Hybris 6.6
What’s New?
  • Http framework migrated from OkHttp3 to RestTemplate to improve cross compatibility with 3rd party integrations
  • Reintroduces proxy configuration through the connector settings UI
  • Introduced CRON configuration for both the Job Send and Status Updates from the connector settings UI
  • Changed CRON job saving mechanism, to guarantee older CRON jobs removes before saving frequency changes
  • Removed local HttpClient and HttpCore jars, to favor whatever jar versions are shipped with the java SDK and Hybris
  • Added socket factory timeouts to prevent the HttpClient bug described on HttpClient timing out
  • Added error handler in the excel classification import. This allows importing excels containing classifications that are not present in the Hybris instance, by skipping those that are not part of the Classifications catalog.
  • Added support for Object lists, to translate classification attribute values.
Known Issues
Description
XercesImpl causing build issues, the dependency has been removed.
Proxy not working for Content API V2 library.
Proxy not working for FMS library.
Regular users jobs gets stuck while sending for translation.
"Notes to Translator" is shown twice while creating jobs.
Requests from 3rd party plugins getting blocked and timing out when the connector is installed.
Change TUS client upload chunks web method from PATCH to POST, with the header X-HTTP-Overrid-Method=PATCH to overcome the limitation that comes from using the native java version shipped in Hybris..
Added recursive method to resolve all the classifications levels, to solve the issue related to missing classifications when exporting to excel.
Changed search parameter options to solve the issue with the search bar on the classifications mapping screen.
Validation needed to translate only string values and prevent translating classes names.
Prepare content from ClassificationAttributeValueModel in feature value, to support properly classification attribute values translation.
Removed support of Enum types as they are causing conflicts with Object Lists. This to support properly classification attribute values translation.
Fixed issue with a wrong classification attribute value copy, happening while creating the new target version of the classification attribute value.
What’s New?
  • Connector works on Hybris 2105, 2205 and Cloud version
Known Issues
Issue ID Description
1155650 When configuring Proxy, the connector doesn't use the configured settings to send the job through Content Api V2 and FMS.
1155650 The connector fails building on Hybris 2205 due to a deprecated Xerces library implementation.
Version 3.0.3
What’s New?

  • Admin users can now view jobs on Translation Queues from non-admin users.

  • Now “Submited On” contains, additionally to the the date, the time when the job was submited.

Known Issues
Issue ID Description
949924 SAP CC Connector v3.0 does not support specifying Freeway Analysis Code as part of job metadata.
Issues Fixed in This Release
Issue ID Description
1119210 Previously, when sending a job, the default Due Date was set to the Job Creation date at 3 A.M., leading to errors when that date was in the past. Now the default Due Date is set to Today + 2 Weeks.
Known Issues
Issue ID Description
949924 SAP CC Connector v3.0 does not support specifying Freeway Analysis Code as part of job metadata.
What’s New?

  • Lionbridge Connector for SAP Commerce now connects to language service providers via Lionbridge Content API. The license and LSP Configuration section has been updated to support connection to Lionbridge Content API.

  • Sending new jobs via legacy Clay Tablet Platform is no longer supported. LSPs connected to Clay Tablet Platform in previous connector versions are now displayed in the Legacy LSP Configuration section. They are maintained so that you can receive back jobs sent to those legacy LSPs.

  • Classification Content Mapping UI has been revamped to better support content mapping of multiple classifications.

  • Added Connector config UI change which displays details below:

    • SAP CC Version

    • Connector Version

    • Build

Issues Fixed in This Release
Issue ID Description
790662 Previously, the Classification Attribute Translation issue was caused by creating two different categories having the same feature. This issue has been resolved.
Known Issues
Issue ID Description
949924 SAP CC Connector v3.0 does not support specifying Freeway Analysis Code as part of job metadata.

Lionbridge Connector for SAP Commerce Release Notes ver. 3.0

What’s New?
  • Added the API capability to the Connector, which allows automatic translation jobs creation in SAP Commerce.
  • Added support for sending e-mail notifications at the following stages of the translation process:
    • When the translation job is submitted
    • When the translation is received
    • When the translation job has errors
  • Added the Translation URL Conversion functionality to convert the URLs in the translated content automatically.
  • The log file of the Connector now shows the Connector version at the beginning of each Cron job invocation.
Issues Fixed in This Release
Issue ID Description
480332 Previously, the Connector has thrown an error when the Classification Attribute value was sent for the translation. This issue has been resolved.
642456 Previously, when multiple jobs with multiple target languages were submitted for translation, the Connector has thrown an error. This issue has been resolved.
480011 Previously, when the Classification Attribute was added to the Product Feature, the Job translation was failed. This issue has been resolved.
599233 Previously, the Content Mapping menu was accessible for non-Admin users also. Now, this menu is accessible only for the Admin users.

Lionbridge Connector for SAP Commerce Release Notes ver. 2.4.3

Issues Fixed in This Release
Issue ID Description
257914 Previously, if the translated content of a content item exceeded the maximum length allowed by SAP Commerce, then the item was not imported. This issue has been resolved: If a content item has a maximum length, the Connector indicates this in an XML property, so that the translation provider can validate and enforce the length.
283011 Previously, if the translated content violated a constraint enforced by SAP Commerce, such as exceeding the maximum allowed length, then the user was not notified that the item was not imported. This issue has been resolved. If the translated content violates an enforced constraint, and SAP Commerce cannot import it, then:

The corresponding constraint violations error messages are written to the Connector log file.
 In the Job Details page:
The Error column displays the constraint violations error messages for the corresponding asset.
 The Status column displays Rejected.
290352 Previously, when users tried to add content items of unmapped item types to the Translation Queue or to send them out for translation, the Send to translation wizard displayed the following generic message: Error in adding items to Translation Queue. This issue has been resolved. In this scenario, the wizard now displays the items types that require mapping so that the Connector can process the content items selected by the user.

Lionbridge Connector for SAP Commerce Release Notes ver. 2.4.2

What’s New?
  • There have been back-end improvements to how the Connector saves content-mapping configurations.
Issues Fixed in This Release
Issue ID Description
LHYB-405 In earlier versions of the Connector, while adding more attributes to a previously mapped type, the previously added attributes were removed from the mapping. This issue has been resolved: Adding more attributes to a previously mapped type no longer removes the previously added attributes from the mapping.

Important: Upgrading the Connector database is required when updating your Connector installation from version 2.1.x-2.4.0 to the current version. This is required to support changes to how classification content mapping is saved in the Connector database. For detailed instructions, refer to the Lionbridge Connector for SAP Commerce Installation and Configuration Guide.
LHYB-409 In version 2.4.0 of the Connector, saving content mappings in SAP Commerce Cloud version 1905.2 displayed an error message. This issue has been resolved.

Lionbridge Connector for SAP Commerce Release Notes ver. 2.4.1

What’s New?
  • The Lionbridge Connector for Hybris has been renamed to the Lionbridge Connector for SAP Commerce.
  • The Connector now supports SAP Commerce and SAP Commerce Cloud.
  • For Product and Product descendant item types, the Asset Name column in the Job Details page now displays the article number alongside the product name and PK number, which were previously displayed.
Issue Fixed in This Release
Issue ID Description
LHYB-391 Previously, when the Connector packaged content to send for translation from the Hybris Backoffice version 6.6, there were duplicate entries for the same FieldContent items in multiple translation items. This issue has been resolved.

Lionbridge Connector for SAP Commerce Release Notes ver. 2.4.0

What’s New?
  • You can now include any keyword properties in content you send for translation. Previously you could include keyword properties only of the Product type.
  • The Item Type Attributes tab of the Content Mapping page now displays by default Relation type attributes and types that contain only Relation type attributes in search results. If you want to exclude these attributes and types from the search results, clear the new Include relations check box. By default the level of recursion of these type attributes is 1. You can modify the number of levels by editing the value of the contentextraction.requestsSourcesExtractionRecursivenessMaxDepth parameter in the {HYBRIS_HOME}/hybris/bin/custom/ctcore/project.properties file.

Warning: Changing the default value of 1 to a larger number may produce large process-consuming tasks that can affect system performance.

Issues Fixed in This Release
Issue ID Description
LHYB-379 In previous versions of the Connector, the Backoffice did not work properly in Hybris version 1808. This issue has been resolved.
LHYB-383 In version 2.2.2 of the Connector, if multiple classification attributes were assigned to a category to which a product was assigned, then when the Connector sent the product for translation, it sent only the product attributes and it did not send the product features. This issue has been resolved. In the previous scenario, the Connector now sends both the product attributes and product features for translation.

Lionbridge Connector for Hybris Release Notes ver. 2.3.0

Issues Fixed in This Release
Issue ID Description
LHYB-380 Previously, users could not send for translation previously mapped multi-value product classification attributes. When attempting to do this, a StringIndexOutOfBoundsException error was written to the log file. This issue has been resolved. You can now successfully send for translation multi-value product classification attributes that were previously mapped .
LHYB-381 Previously, when sending for translation a product that had both localized and non-localized product classification attributes, none of the attributes were translated. This issue has been resolved. In this scenario, the localized product classification attributes are now translated, and the non-localized product classification attributes are not translated.

Lionbridge Connector for Hybris Release Notes ver. 2.2.2

Issue Fixed in This Release
Issue ID Description
LHYB-377 In versions 2.1.0 and higher of the Connector, if a classification attribute had been removed from a product category, then the Connector did not send any other classification attributes of that product category for translation. This issue has been resolved.

Lionbridge Connector for Hybris Release Notes ver. 2.2.1

What’s New?
  • The Connector now supports Hybris version 6.7.
  • In the Translation Jobs page, when clicking the Translation Status column header to sort by this column, the jobs are now sorted by percentage completed. Previously, the jobs were sorted alphabetically by translation status.
  • When translating a keyword, the Connector now retains the keyword’s relationship with a product. Previously, a translated keyword did not retain the relationship of the source keyword to a product.
  • The Connector installation package for Hybris version 6.7 no longer includes the following folders:
  • ctbasecockpit
  • ctcockpit
  • ctwcms

These folders have been removed because Hybris version 6.7 does not include those cockpits. It includes only the Backoffice Cockpit.

Note: If you are using an earlier version of Hybris and require support for the old cockpits, please contact Lionbridge Support.

Issues Fixed in This Release
Issue ID Description
LHYB-267 Previously, the item count was incorrect in the following list pages of the Connector:

Translation Queue
 Translation Jobs page
* Archived Jobs page

This issue has been resolved. The item count on these pages is now correct.
LHYB-294 Previously, the issue described here occurred in Connector list pages with search functionality and with multiple items listed on multiple sub-pages, such as the Content Mapping page. When the current page was not the first sub-page, then after searching, if the search results spanned multiple sub-pages, the last sub-page of the search results was initially displayed, instead of the first sub-page of the search results. This issue has been resolved. In this scenario, the Connector now initially displays the first sub-page of the search results.
LHYB-336 Version 2.1.0 of the Connector did not support receiving multiple delivering of the same content items, for example, a revision of translated content. This issue has been resolved. The Connector now supports receiving revisions of translated content.
LHYB-360 In previous versions of the Connector, if the Cron job interval (minutes) setting was never saved in the Translation Settings section of the System Configuration page, then the CronJob was not created and it did not run. This prevented it from downloading and importing translations from the Clay Tablet Platform. This issue has been resolved. The CronJob is now created during the Connector installation.
LHYB-370 in New Features
LHYB-371 Previously, if the Connector used the Oracle or SAP database, then while mapping more than 900 classification attributes in the Classification Attributes tab of the Content Mapping page, an error message was displayed. This issue has been resolved. You can now map more than 900 classification attributes.
LHYB-372 Previously, when sending classification-attributes values for translation that were configured as Multi-valuedand that were previously translated and then updated, the Connector did not update the translated values. Instead, the Connector created new values for the updated translations that were hidden by default. This issue has been resolved. The Connector now updates the translated values, as expected.
LHYB-375 Previously, the following files were overridden by values from a custom Backoffice extension:

backoffice.cockpitng.mainpage.css=./cng/css/ctbackoffice.css
 backoffice.cockpitng.loginpage.css=./cng/css/loginpage_ctbackoffice.css

This issue has been resolved. A custom Backoffice extension no longer overrides these files.

Lionbridge Connector for Hybris Release Notes ver. 2.2.0

Issues Fixed in This Release
Issue ID Description
LHYB-364 In versions 2.1.0 and higher of the Connector, the Hybris language codes were not displayed in the expected format in the Language Mapping page. This issue has been resolved.
LHYB-365 In versions 2.1.0 and higher of the Connector, when configuring classification attributes for translation using the Classification Attributes tab of the Content Mapping page, you could not save classification attributes whose names contained square brackets ( [ ] ). This issue has been resolved, by changing how classification content mapping is saved in the Connector database,

Important: When upgrading from version 2.1.x of the Connector to the current version, you must upgrade your Connector database. For detailed instructions, refer to "Upgrading Your Connector Database" in the Lionbridge Connector for Hybris Installation and Configuration Guide.

Lionbridge Connector for Hybris Release Notes ver. 2.1.3

Issues Fixed in This Release
Issue ID Description
LHYB-143 In previous versions of the Connector, the Content Mapping page displayed Hybris objects that had no localized attributes. This issue has been resolved. The Content Mapping page no longer displays Hybris objects that have no localized attributes.
LHYB-319 In previous versions of the Connector, in the Language Mapping section of the System Configuration page, the Delete button was not fully displayed for each pair of mapped language codes. This issue has been resolved. The Delete button is now fully displayed for each pair of mapped language codes.
LHYB-344 In previous versions of the Connector, when sending out content for translation, the Connector did not send out the keyword property, and an error was displayed in the log file. This issue has been resolved. The Connector now sends out the keyword property for translation.

Lionbridge Connector for Hybris Release Notes ver. 2.1.2

What’s New?
  • The Lionbridge Freeway-specific fields in the Job Details tab of the Send to Translation wizard in the Hybris Backoffice are now displayed only when Lionbridge Freeway is selected as the translation provider.
  • The Connector uses the new license server, located at: https://api.clay-tablet.net/license/v1.

Tip: If you have a firewall, you must configure your ports so that the Connector can communicate with this server. For details, see the new “Configuring Network Settings for a Firewall” section in the Lionbridge Connector for Hybris Installation and Configuration Guide.

Issues Fixed in This Release
Issue ID Description
LHYB-315 When using Hybris 6.1 or 6.2, manual steps are required to support the Connector functionality in the Hybris Backoffice. However, the documentation for these steps has been enhanced.
LHYB-341 The installation and configuration guide now includes the following section: "Configuring Network Settings for a Firewall."
LHYB-342 When using the SAP HANA database with version 2.1.0 of the Connector, you cannot send out content for translation. This issue has been resolved. The SAP HANA database is now supported.
LHYB-345 Previously, in version 2.1.0 of the Connector, after sending a job to an LSP and then deleting that LSP from the Connector's configuration, according to the log file, the Connector checked the license key of the deleted LSP for messages. This issue has been resolved. The Connector no longer checks the license key of the deleted LSP for messages.

Warning: Do not delete an LSP with active jobs. If you delete an LSP when there are jobs out for translation to that LSP, then you will not see when the translated content returns.
LHYB-347 Previously, in version 2.1.0 of the Connector, opening pages in the Hybris Backoffice to select objects or website page for translation displayed an error, andd navigation within the Backoffice failed. This issue has been resolved.

Lionbridge Connector for Hybris Release Notes ver. 2.1.1

What’s New?
  • The Connector now supports Hybris versions 6.1 and higher.
  • You can now configure the Connector to send additional types of content for translation.
  • You can configure the Connector to send product classification attributes for translation.
  • You can configure the Connector to send any Hybris business objects and localized attributes for translation.
  • You can now send the following types of content for translation from the Hybris Backoffice:
  • products, from the Hybris Backoffice Product Cockpit (Hybris 6.4 and higher only)
  • products, from the Products page in the Hybris Backoffice
  • website pages, fromthe WCMS Pages page in the Hybris Backoffice

Lionbridge Connector for Hybris Release Notes ver. 2.1.0

Earlier versions of the release notes are available only as PDFs

Clay Tablet Connector for hybris Release Notes ver. 1.5.0

Clay Tablet Connector for hybris Release Notes ver. 1.0.0