Optimizely - update 414

Logging was improved for Optimizely PIM:

• Info-level logging for:
  • successful create/modify/delete operations (refresh/publish jobs)
  • summary of models synced, list of content types, each with list of properties (sync job)
• Error-level logging for:
  • unsuccessful create/modify/delete operations, with reason for failure

If a product has content for multiple languages in PIM, it will be pulled into Commerce Cloud by the refresh job.

• Translations for products - stored in translation property or content (long description)
• Translations for images - stored in translation property
• Translations for specifications - part translation property (description - part of the property) and part content

Extended the functionality to synchronize data jobs to validate the catalog using the same languages.

Translations associated with properties are posted to Commerce from PIM.

Within the Product Publishing Job, PropertyAudits is retrieved and updates the related translations that come with the API call under the PropertyTranslation table. If translations are not provided in the payload, those translations are cleared for that specific property.

If a category has content for multiple languages in PIM, it will be pulled into Commerce  Cloud by the publish function which uses the GetApprovedCategoryTreesForPublishing API.

Fixed an issue that said there were no children of a selected type when you tried to convert pages with multiple languages.