Translations & Localizations

This is a "pre-process" required to utilize the Completion-Synchronization or Completion-Translation workflows. This pre-process attempts to gather all dependent content changes regardless of how deep they are in the content. The Completion creates a file that contains all of the dependent content for running the Synchronization or Translation workflow process using two workflows created for Completions.

While this process was initially intended to work with the Completion-Translation and Completion-Synchronization workflows it can be used with other workflows including Translation with ULG, Translation, and Copy Over. See those topics for specific instructions on how to use a Completion with those workflows as it is different than the original process with Completion-Translation and Completion-Synchronization workflows.

To create a Completion:

• Open the Control Room and click on the icon for starting a localization workflow in the control room window. Alternately you can right click on an item in the library and select start localization workflow
• For Workflow Type select "Completion"
• While the notes field is available, usually only the initiator of the Completion workflow will see these, so they may not be very useful but are optional if needed.
• Click "Start" to start the workflow process to create the completion file
• You will see a new Completion workflow appear in your Localization Inbox
• Click on the right arrow to open the workflow
• You will see a completion collection with a name similar to "14:24:763"
• Open that file in a tab by right clicking. You will want this file available for the second part of the completion process
• Click "Accept Task" then click "Apply"
• Go to the instructions for the specific localization workflow you are trying to run for the next steps.

This workflow should generally be used when translating small amounts of content. It works best when you have made changes to one or only a few components and know exactly what you need to send to translation. You can select each component individually and add it to the list of items in the workflow. This is also referred to as the "SFTP" translation workflow. This simply means this is the legacy batch process workflow for sending translations to ULG. It has been superseded by the "Translate with ULG" workflow also referred to as the "ULG Connector" which is a real-time API interface.  

For more complex translations that have many levels of dependent content changes, you should consider using the Completion-Translation workflow. If you don't wish to use the Completion-Translation workflow, but still wish to use a Completion, you can do so with this Translation workflow. See below on how to do this.

Creating a Translation Workflow:

• Open the Control Room and click on the icon for starting a localization workflow in the control room window. Alternately you can right click on an item in the library and select Start Localization Workflow
• Workflow - At the top of the workflow you can edit the information which defaults to the author's name, date and time. 
• Workflow Type - For Workflow Type select "Translation"
• Retranslate - A key function in the Translation workflow is the ability to override the default behavior in CoreMedia for what content will be sent for translation. There are many use cases where CoreMedia may not think a a content item has been modified, but the content author knows they wish to send the item for translation. If CoreMedia believes a content item is unmodified it will not send it to translation as the default behavior. An author can override this by selecting the retranslate checkbox
• Type - is an optional field that can be used to tag the content as a specific category for business use. While this is not a required field, the platforms may require this field for routing or tracking purposes.
• Content - However you started the workflow, you can add additional content by dragging it into the Content window. When CoreMedia believes other content is required to complete the chosen content localization properly it will appear as Dependent Content and also be sent for translation. If you wish to use content from a Completion Collection see the steps below.
• Notes - are optional and will be seen by the approver in Octave (the ULG translation system). The notes will also be available for ULG. It is up to the business to specify if this field is required and what should be entered.
• Target Locales - CoreMedia will show the available locales based on the content included. These will generally be the children of the locale you are pulling content from. You can select or deselect any of the locales. All content added to the workflow will be translated to the target locales that are selected.
• Click "Start" to start the workflow process to send the translation to ULG
• You will see a new Translation workflow appear in your Inbox for each target locale that you have selected.
• Hover over the workflow and click on the right arrow to open a workflow for processing. You will see your translation details and the number of items in your workflow. Note, not all of these items will be translated if they show as unmodified and you have not selected the retranslate box. Also note if you see any mixed language content generally "English" when you are translating another language, you will need to fix this before sending to ULG or your workflow will fail.
• Click "Accept Task". Make sure "Send to Translation Service" radio button is selected in the Workflow Steps before you click "Apply"
• The workflow will move to your pending folder until returned from ULG

Using a Completion Collection with a Translation Workflow:

• First, use the Completion Workflow instructions to build a completion collection.
• Start a Translation workflow
• Go to the tab for the completion collection you have open in Studio
• Click on the first item, then click Ctrl-A to select all items.
• Drag those items to your workflow
• Go back to instructions above and complete the Translation Workflow.

Once a workflow has returned from ULG and is in your inbox:

• When a workflow has returned to your inbox from ULG, hover over the far right of the workflow in the Control Room window. Click on the right carat that appears to open the workflow.
• Click "Accept Task"
• Important: If you wish to easily publish this content,
  • create a new publication workflow
  • select all of the items in the Content of the translation workflow
  • drag and drop those items into the content window of the publication workflow
  • leave the workflow open and return to complete the translation workflow before starting the publication workflow
• Click "Apply" on the translation workflow
• Go back to your publication workflow. Confirm it is set to "Direct Publication" then click "Start"

For larger translation needs or where changes have been made multiple levels deep in the content, you can use the Completion-Translation workflow. You will first run a Completion workflow to gather the content and then run a Completion-Translation workflow on the Completion Collection you created. This process attempts to gather all dependent content that needs to be translated regardless of how deep changes have been made in the content.

This is also referred to as the "SFTP" translation workflow. This simply means this is the legacy batch process workflow for sending translations to ULG. It has been superseded by the "Translate with ULG" workflow, although you cannot directly use a Completion in the Translate with ULG workflow, also referred to as the "ULG Connector" which is a real-time API interface.  

Creating a Completion-Translation Workflow:

• Open the Control Room and click on the icon for starting a localization workflow in the control room window.
• Workflow - At the top of the workflow you can edit the information which defaults to the author's name, date and time. 
• Workflow Type - For Workflow Type select "Completion-Translation"
• Retranslate - A key function in the Translation workflow is the ability to override the default behavior in CoreMedia for what content will be sent for translation. There are many use cases where CoreMedia may not think a a content item has been modified, but the content author knows they wish to send the item for translation. If CoreMedia believes a content item is unmodified it will not send it to translation as the default behavior. An author can override this by selecting the retranslate checkbox
• Type - is an optional field that can be used to tag the content as a specific category for business use. While this is not a required field, the platforms may require this field for routing or tracking purposes.
• Content - Drag and drop the Completion Collection you should have open in Studio from the Completion process.
• Notes - are optional and will be seen by the approver in Octave (the ULG translation system). The notes will also be available for ULG. It is up to the business to specify if this field is required and what should be entered.
• Target Locales - CoreMedia will show the available locales based on the content included. These will generally be the children of the locale you are pulling content from. You can select or deselect any of the locales. All content added to the workflow will be translated to the target locales that are selected.
• Click "Start" to start the workflow process to send the translation to ULG
• You will see a new Translation workflow appear in your Inbox for each target locale that you have selected.
• Hover over the workflow and click on the right arrow to open a workflow for processing. You will see your translation details and the number of items in your workflow. Note, not all of these items will be translated if they show as unmodified and you have not selected the retranslate box. Also note if you see any mixed language content generally "English" when you are translating another language, you will need to fix this before sending to ULG or your workflow will fail.
• Click "Accept Task". Make sure "Send to Translation Service" radio button is selected in the Workflow Steps before you click "Apply"
• The workflow will move to your pending folder until returned from ULG

Once a workflow has returned from ULG and is in your inbox:

• When a workflow has returned to your inbox from ULG, hover over the far right of the workflow in the Control Room window. Click on the right carat that appears to open the workflow.
• Click "Accept Task"
• Important: If you wish to easily publish this content,
  • create a new publication workflow
  • select all of the items in the Content of the translation workflow
  • drag and drop those items into the content window of the publication workflow
  • leave the workflow open and return to complete the translation workflow before starting the publication workflow
• Click "Apply" on the translation workflow
• Go back to your publication workflow. Confirm it is set to "Direct Publication" then click "Start"

This workflow is meant to supersede the Synchronization workflow. It is generally the preferred workflow for copy content directly from a parent to child locale using the identical content from the parent without going through translation. There are a few specific use cases where you may wish to use a Synchronization workflow. See those instructions for why you may still wish to use a Synchronization.

Use the Copy Over when you simply want to copy content from a parent locale to a child locale with the same language. This workflow does just what the name implies. It copies over all of the content you add to the workflow. It will grab dependent content (eg. changed components within a page if you add a page to the workflow) but may not pull all changed content if it is embedded in a rich text field or is on a dependent page. This workflow functions much like a translation workflow where you choose the child locales that you are doing the copy-over to. This means that you can copy content of a different language if the parent and child are different languages, although this would not be a standard use case. In most cases you would be copying English to English, German to German, etc.

Performing a Copy Over Workflow:

• Open the Control Room and click on the icon for starting a localization workflow in the control room window. Alternately you can right click on an item in the library and select Start Localization Workflow
• Workflow - At the top of the workflow you can edit the information which defaults to the author's name, date and time. Since this is a copy over and the author will most likely complete all of the steps, most of the optional fields may be unnecessary unless required by the business for reporting or other purposes
• Workflow Type - For Workflow Type select "Copy Over"
• Content - However you started the workflow, you can add additional content by dragging it into the Content window. When CoreMedia believes other content is required to complete the chosen content localization properly it will appear as Dependent Content and also be through the localization process. If you wish to use content from a Completion Collection see the steps below.
• Notes - are optional but may not serve any purpose for the copy over process. It is up to the business to specify if this field is required and what should be entered.
• Target Locales - CoreMedia will show the available locales based on the content included. These will be all of the children of the locale you are pulling content from. You can select or deselect any of the locales. All content added to the workflow will be copied over to the target locales that are selected even if they are generally intended to be a different language.
• Click "Start" to start the workflow process to copy over the content
• You will see a new Copy Over workflow appear in your Inbox for each target locale that you have selected. See "Finishing your Copy Over Workflow" below to complete and publish your content

Using a Completion Collection with a Copy Over Workflow:

• First, use the Completion Workflow instructions to build a completion collection.
• Start a Copy Over workflow
• Go to the tab for the completion collection you have open in Studio
• Click on the first item, then click Ctrl-A to select all items.
• Drag those items to your workflow
• Go back to instructions above and complete the Copy Over Workflow.

Finishing Your Copy Over Workflow:

• Hover over the workflow and click on the right arrow to open a workflow for processing. You will see your translation details and the number of items in your workflow. 
• Click "Accept Task"
• Important: If you wish to easily publish this content,
  • create a new publication workflow
  • select all of the items in the Content of the translation workflow
  • drag and drop those items into the content window of the publication workflow
  • leave the workflow open and return to complete the copy over workflow before starting the publication workflow
• Click "Apply" on the translation workflow
• Go back to your publication workflow. Confirm it is set to "Direct Publication" then click "Start"

***Updated 9/1/2021

This is a new workflow for ULG built on the CoreMedia API design used for Translate with Globalink. This is a real-time API and is sometimes referenced as "ULG Connector". It will be the preferred workflow for translations going forward and supersede the "Translation" workflow for most use cases. Currently there are many issues with this workflow and we are working to resolve them. For now, you may wish to continue using the Translation workflow for most translations. Important note: the retranslate function does not currently work with this workflow. There are other known errors occurring and these are being researched for fixing.

This workflow can generally be used when translating small amounts of content. It works best when you have made changes to one or only a few components and know exactly what you need to send to translation. You can select each component individually and add it to the list of items in the workflow. Additionally, for more complex translations that have many levels of dependent content changes, you can use the Completion workflow to create a Completion Collection to use with this workflow. See below on how to do this.

Creating a Translate with ULG Workflow:

• Open the Control Room and click on the icon for starting a localization workflow in the control room window. Alternately you can right click on an item in the library and select Start Localization Workflow
• Workflow - At the top of the workflow you can edit the information which defaults to the author's name, date and time. 
• Workflow Type - For Workflow Type select "Translation"
• Due Date - this field is sent to ULG to let them know the requested due date for this content. It defaults to 14 business days, but can be changed.
• Retranslate - This functionality is currently not available in the Translate with ULG workflow. If you need this functionality consider using a Translation workflow or Completion-Translation workflow. (A key function in the Translation workflow is the ability to override the default behavior in CoreMedia for what content will be sent for translation. There are many use cases where CoreMedia may not think a a content item has been modified, but the content author knows they wish to send the item for translation. If CoreMedia believes a content item is unmodified it will not send it to translation as the default behavior. An author can override this by selecting the retranslate checkbox.)
• Type - is an optional field that can be used to tag the content as a specific category for business use. While this is not a required field, the platforms may require this field for routing or tracking purposes.
• SNOW Ticket ID - used by some businesses to track the initial request for this translation. It is a mandatory field, but anything can be entered here including "N/A" or other text.
• Content - However you started the workflow, you can add additional content by dragging it into the Content window. When CoreMedia believes other content is required to complete the chosen content localization properly it will appear as Dependent Content and also be sent for translation. If you wish to use content from a Completion Collection see the steps below.
• Notes - are optional and will be seen by the approver in Octave (the ULG translation system). The notes will also be available for ULG. It is up to the business to specify if this field is required and what should be entered.
• Target Locales - CoreMedia will show the available locales based on the content included. These will generally be the children of the locale you are pulling content from. You can select or deselect any of the locales. All content added to the workflow will be translated to the target locales that are selected.
• Click "Start" to start the workflow process to send the translation to ULG
• You will not see a new Translation workflow appear in your Inbox. This step is bypassed in this workflow. The workflow will automatically move to your pending folder until returned from ULG

Using a Completion Collection with this Workflow:

• First, use the Completion Workflow instructions to build a Completion Collection.
• Start a Translate with ULG workflow as noted above
• Go to the tab for the completion collection you have open in Studio
• Click on the first item, then click Ctrl-A to select all items.
• Drag those items to your workflow
• Go back to instructions above and complete the Translate with ULG Workflow.

Once a workflow has returned from ULG and is in your inbox:

• When a workflow has returned to your inbox from ULG, hover over the far right of the workflow in the Control Room window. Click on the right carat that appears to open the workflow.
• Click "Accept Task"
• Important: If you wish to easily publish this content,
  • create a new publication workflow
  • select all of the items in the Content of the translation workflow
  • drag and drop those items into the content window of the publication workflow
  • leave the workflow open and return to complete the translation workflow before starting the publication workflow
• Click "Apply" on the translation workflow
• Go back to your publication workflow. Confirm it is set to "Direct Publication" then click "Start"

This sis an API that connects to translations.com for machine translation. Check with your CoreMedia lead or Enterprise IT if you wish to use this service.

In most cases you would choose to use the Copy Over workflow functionality rather than Synchronization. This is legacy functionality that existed before the copy over functionality. One still valid use case is when you wish to synchronize new content across all locales (regardless if they are children, grandchildren, etc.) that share the same language as the master. The synchronization allows you to synchronize (copy) content to all locales of the same language with a single workflow. This is an all-or-none workflow as the system determines which locales to include in the synchronization. You do not get to select individual locales as you do in the Translation or Copy Over workflows.

This workflow is best for smaller amounts of content as there may be deeper dependent content that is not pulled into the workflow. For more complex synchronizations that have many levels of dependent content changes, you should consider using the Completion-Synchronization workflow. If you don't wish to use the Completion-Synchronization workflow, but still wish to use a Completion, you can do so with this Synchronization workflow. See below on how to do this.

Creating a Synchronization Workflow:

• Open the Control Room and click on the icon for starting a localization workflow in the control room window. Alternately you can right click on an item in the library and select Start Localization Workflow
• Workflow - At the top of the workflow you can edit the information which defaults to the author's name, date and time.
• Workflow Type - For Workflow Type select "Synchronization"
• Content - However you started the workflow, you can add additional content by dragging it into the Content window. When CoreMedia believes other content is required to complete the chosen content localization properly it will appear as Dependent Content and also be sent through the localization process. If you wish to use content from a Completion Collection see the steps below.
• Notes - are optional. It is up to the business to specify if this field is required and what should be entered.
• Target Locales - CoreMedia will show all locales that will be included in the synchronization based on the content included. All content added to the workflow will be synchronized to all of the target locales and cannot be altered to select fewer target locales. This is an all-or-none workflow process.
• Click "Start" to start the workflow process
• You will receive no other indications of this workflow finishing. Since there is no other indication that a Synchronization is finished, there is no simple method for publishing the content. The author will have to review their "My Edited Content" or know exactly what content needs to be published.

Using a Completion Collection with a Synchronization Workflow:

• First, use the Completion Workflow instructions to build a completion collection.
• Start a Synchronization workflow
• Go to the tab for the completion collection you have open in Studio
• Click on the first item, then click Ctrl-A to select all items.
• Drag those items to your workflow
• Go back to instructions above and complete the Synchronization Workflow.

For larger synchronization needs or where changes have been made multiple levels deep in the content, you can use the Completions-Synchronization workflow. You will first run a Completion workflow to gather the content and then run a Completion-Synchronization workflow on the Completion Collection you created. This process attempts to gather all dependent content that needs to be synchronized regardless of how deep changes have been made in the content. Using the copy over is an alternative to this workflow, but you will need to determine which works best for your specific needs. You can use a Completion Collection with the Copy Over workflow.

Creating a Completion-Synchronization Workflow:

• Open the Control Room and click on the icon for starting a localization workflow in the control room window.
• Workflow - At the top of the workflow you can edit the information which defaults to the author's name, date and time.
• Workflow Type - For Workflow Type select "Completion-Synchronization"
• Content - Drag and drop the Completion Collection you should have open in Studio from the Completion process
• Notes - are optional. It is up to the business to specify if this field is required and what should be entered.
• Target Locales - CoreMedia will show all locales that will be included in the synchronization based on the content included. All content added to the workflow will be synchronized to all of the target locales and cannot be altered to select fewer target locales. This is an all-or-none workflow process.
• Click "Start" to start the workflow process
• You will receive no other indications of this workflow finishing. Since there is no other indication that a Synchronization is finished, there is no simple method for publishing the content. The author will have to review their "My Edited Content" or know exactly what content needs to be published.