Project Update
When you add a new version of an asset (or assets) to an existing project, the corresponding assets will be canceled from the project and new tasks will be started for the project. You are able to leverage your previous work. The new assets are introduced to the project, the new versions will leverage against the updated translation memories, and the workflow process will proceed on the new versions of the assets just like any newly added tasks.
- all tasks with changed assets – This view shows all tasks whose assets have been updated since the task was segmented.
- active tasks with changed assets – This view shows all active (not completed or canceled) tasks whose assets have been updated since the task was segmented.
- finished tasks with changed assets – This view shows all completed or canceled tasks whose assets have been updated since the task was segmented.
When you select one of these views, tasks with assets that have changed since the task was segmented will have these assets marked in the Task List with an "Asset changed" icon.
Pending Update state. This dialog includes an Include in project cost calculation check box, which, if checked, causes all the work that has occurred in the tasks to be updated in the project cost calculation.
The following tasks may be restarted after the steps assigned to you have been completed:
<list of tasks>
true, so the default behavior of WorldServer is to restart tasks in a Pending update state once the current workflow steps have been completed. Tasks will either be restarted by a workflow engine once the current automatic step completes, or by WorldServer once a user completes a human step in the workflow.
In the default configuration, WorldServer allow updates to happen after any step in a workflow. However, if you have sophisticated workflows, you may want to create “protected regions” in your workflow during which no task updates can be performed.
For example, if you are not using live translation memory and your translators do not have direct access to Save and Update TM, then you would want to make sure that updates are not applied until after the Save step in the workflow. This would ensure that you don’t lose any work between the time the translation process started and the time the work was saved to translation memory.
To create a “protected region” of your workflow, you disable the Apply pending updates after completing step option on every step, except the last, in the protected region. Under this model, WorldServer waits until the task has exited the protected region before applying an update.
The most conservative approach would be to say that updates can never happen on an active task; updates can only happen when a task has completed or canceled. To achieve this, turn off the Apply pending updates after completing step option on every step in the workflow. Under this model, WorldServer waits until a task has completed or been canceled to apply an update. Note that if a task finishes of its own accord and is Pending update, WorldServer will also automatically restart the task.