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.
You can use the new Custom Handler Classes field in the new Asset Preprocessing section in the Translation tab of the Site Configuration dialog box to specify a custom Java class for processing assets before the App sends them for translation. For example, you can create and specify the custom Java class to remove the Eloqua tracking ID from the URL of hyperlinks inside the content of an asset before the App sends it for translation.
- The App now uses the Lionbridge Content API to send out content for translation. Lionbridge Connector Support migrates your providers and configuration to the Lionbridge Content API.
- Site administrators can configure and connect the App's access to the Lionbridge Content API using the new Content API Token field and corresponding Connect button in the Site tab of the Site Configuration dialog box.
- In the Translation Jobs tab, site administrators can now change the job-creator record in the job. This facilitates translation management if the job creator is not available.
- In the Translation Jobs tab, site administrators or the job creator can now un-archive an archived job
- In the new Site Email Notification Group page, site administrators can now create groups of email addresses to facilitate receiving email notifications for jobs. The groups can contain manually added email addresses and email addresses of existing and imported Oracle Eloqua users. When sending out a job for translation, you can select the entire team, the job submitter, an email notification group, modify an existing group or add individual email addresses.
- When selecting assets to send to the queue or directly out for translation, you now select the translation provider before specifying the source and target languages. This prevents you from selecting languages that are not supported for a particular translation provider.
- The App now supports sending the ProgressiveProfile field type for translation.
- The App now supports alphabetically sorting a translated picklist before the translation returns to Oracle Eloqua.
- The new maxLength attribute in the translation XML file indicates any maximum-length limitations from Eloqua. This is a helpful indicator to translators not to exceed the maximum field length in translated content.
Issues Fixed in This Release
|OEL-137||In versions 1.6.4 and 1.6.5 of the App, selecting the Send for quote first check box while sending a job for translation did not actually request a quote from the translation provider. This issue has been resolved: Selecting the Send for quote first check box while sending a job for translation now requests a quote from the translation provider.|
|OEL-142||Previously, a completed translation job was not delivered if the access token for the job submitter had expired, for example if the job submitter had left the company or was on vacation. This issue has been resolved: A site administrator can now change the job-creator record for a job to prevent this scenario from causing a job to fail.|
Issue Fixed in This Release
|OEL-144||In version 1.6.5, the App did not update the target form with translations for complex process steps. This issue has been resolved.|
- In the new Translation Defaults page, you can now set the following default values:
- source language
- target languages
- team (if relevant)
- (translation) provider)
You can also set these default values while sending assets for translation:
- In the Languages tab of the New Translation dialog box, you can use the new Save selected button to save the selected source language and target languages as the default languages.
- In the Translation Job tab of the New Translation dialog box, you can use the new Save selected buttons to save the selected team and (translation) provider as the default values for those fields.
- In the Send Out Queued Items dialog box, you can use the new Save selected buttons to save the selected team and (translation) provider as the default values for those fields.
- The Site Users page now has the new Token and Last Login columns.
- When you translate any type of Landing Page that contains a Form, the App now updates the Form's name (elqFormName) and ID in the Landing Page.
- The App now uses the Async HTTP call to the Eloqua API to run faster. This call uses the following library:
https://www.baeldung.com/async-http-client, which is based on Netty:
- You can use the new Freeway Analysis Codes option in the LSP tab of the Site Configuration dialog box to configure the App to hide or display analysis-code fields when sending content for translation to Lionbridge Freeway.
- You can use the new Show Job Description check box in the UI tab of the Site Configuration dialog box to configure the App to hide the Job Description field when sending out content for translation. This is useful when sending content to Lionbridge Freeway, which instead uses the Special Instruction field for this purpose.
- The Translation Jobs tab now has the new LTM column, which indicates whether the Use Local TM check box was selected when a job was sent out for translation.
Note: The new LTM column is available only in the maximized version of this tab. This column is not available in the Lionbridge App that opens within Oracle Eloqua.
Issues Fixed in This Release
|OEL-116||In version 1.6.3 of the App, in the Select Eloqua Assets dialog box, trying to open a folder in the content tree containing many child folders and assets sometimes caused the App to freeze when Eloqua was very slow to respond. This issue has been resolved.|
|OEL-118||In version 1.6.3 of the App, the New Translation dialog box loaded very slowly. Sometimes, loading this dialog box timed out, and an error message was displayed. This issue has been resolved: the New Translation dialog box now loads as expected.|
|OEL-133||In previous versions of the App, if the asset JSON of the source asset and the item metadata had different asset IDs, then this mismatch prevented the job from completing. It also prevented the user from clicking the Reload icon in the Translation Details tab of the Translation Jobs page to successfully load the translated item into Eloqua. This issue has been resolved, because the App now automatically corrects this mismatch.|
|OEL-135||In version 1.6.4 of the App, if an email had header or footer cells that contained complicated HTML formats, then the App sometimes failed to save the translated email in Eloqua. This issue has been resolved: In the previous scenario, the App now always saves the translated email in Eloqua.|
|OEL-136||In version 1.6.4 of the App, if an email was created from a responsive email template with dynamic content in the subject, then the App could not save the translated email in Eloqua. This issue has been resolved: In the previous scenario, the App now saves the translated email in Eloqua.|