Automatic actions required for SDL Online Editor

The final step towards installing SDL Online Editor is to include two automatic actions in your workflows: Enable Online Editing and Save Online Asset. Enable Online Editing prepares an asset to be modified in SDL Online Editor by uploading it online, whereas Save Online Asset ensures that the asset is synchronized in WorldServer and can be modified in WorldServer after a human step has been completed.

Add the Enable Online Editing automatic action before each human step that you want users to perform in SDL Online Editor and the Save Online Asset automatic action after each such human step. Always make sure that the Enable Online Editing automatic action comes after the Segment Asset automatic action.
If you configure a human step to be performed in SDL Online Editor, users can no longer open tasks in Browser Workbench or export translation kits while working on that step. To let your users decide which translation tool they want to use, consider a branching workflow such as the following:A screen shot that shows a branching workflow with the Use Online Editor human step in it.
In this workflow, translators and reviewers decide what tool to use during the Use Online Editor step. For example, to work on a task in SDL Online Editor, a translator must select the Yes transition when completing the Use Online Editor step. Then, the Enable Online Editing automatic action processes the task and prepares it for being translated in SDL Online Editor. After the translation is completed, the Save Online Asset automatic action removes the requirement of working on it only in SDL Online Editor.
Make sure that each human step that you want users to perform in SDL Online Editor has either the Translate or the Review step type in the step's advanced options. To check this, select the step in the workflow, and then, in the Human Step Properties pane, select Advanced. The value selected in the Step Type list should be either Translate or Review.A screen shot that shows the advanced options of a step. The step type is Translate.
This is important for two reasons:
  1. In steps configured with the Translate step type, the Assessment tab is not displayed in SDL Online Editor and users cannot assess translations. The Assessment tab is displayed only in steps configured with the Review step type and only if you granted the Quality Assessment permission in WorldServer to the user types who are supposed to perform those steps.
  2. Different statistics are displayed on the SDL Online Editor status bar depending the step type, as shown in the following table:
    Step typeStatistics displayed
    Translate
    • The number of words in the asset.
    • The total number of segments in the asset.
    • The number of untranslated segments in the asset.
    • The completion rate of the translation.
    Review
    • The number of penalty points assigned to existing assessments. This number is usually 0, because WorldServer does not support penalty points.
    • The total number of segments in the asset.
    • The number of segments that have the Not Translated, Draft, or Translated status.
    • The completion rate of the translation.