WorldServer Project Workflows
In SDL WorldServer, most work is performed within a WorldServer Project that represents work associated with a translation effort for a single target locale. The WorldServer project consists of one or more tasks running through a specific WorldServer workflow. Each task represents a single file (known in WorldServer as an “asset”) that the workflow processes.
This workflow contains two automated steps (“Clear Segment” and “Segment Asset”) that prepare the file for translation. It also contains two human steps, “Translate” and “Review.” Most production WorldServer workflows contain many automated and human steps that may include quote preparation, pre-translation work, translation, review, quality assurance, file delivery, etc.
In the workflow definition, the workflow designer assigns each human step to one or more registered WorldServer users. During task processing, when WorldServer reaches a human step it notifies all assignees by sending each of them an email message that contains a link to the WorldServer task. To work on an assigned task, an assignee can click the link in this email message, log into WorldServer, and then create and download a WorldServer project package to use in Studio. Or, the assignee might send a WorldServer project package to a colleague or business partner as an attachment to an email message or via an FTP server. Once someone edits/translates online or exports the package, the task is automatically claimed by that user in WorldServer, so that no one else can alter it. Claiming is also important, as it is required in order to return the package and/or to make live TM updates, when that option is enabled. When the assignment is complete, the assignee creates a WorldServer return package, uploads it back on WorldServer from Studio or sends it to the project manager to manually import it into WorldServer and then move the task to the next step in the workflow.
Most WorldServer workflows include both a “Translate” step and a “Review” step. When the WorldServer user assigned to the “Translate” step completes that step in WorldServer, the workflow reaches the “Review” step, which it assigns to WorldServer users who are identified as reviewers for the target language of the project. As did the translator, a reviewer obtains a WorldServer project package to open in Studio.