login | sign up

Your session has timed out due to inactivity.

You can go back to the overview without login or use the login form to login again before redirect

Knowledge Base / Administrators – Preparing your one2edit™ Workspace / Workflow Templates

Workflow Actions > Commit Translations (one2edit TM)

Created on 15th November 2018 at 16:05 by Jamie O'Connell

'Workflow Actions' window

Actions can be added to a workflow from the 'Workflow Actions' window (accessed via 'File > Actions' in the workflow view).

This lesson details the 'Commit Translations (one2edit TM)' action.

The 'Commit Translations (one2edit TM)' action is used to store all current translations in the one2edit™ built-in translation memory (TM).

Commit Translations (one2edit TM)

After dragging the 'Commit Translations' action into the action field, you can double-click on it to open the 'Action Editor' window.

However, there are no options to set up - there is just an explanation of what the action does.

When the 'Commit Translations' action is called in the workflow, it will write all source and target segments into the 'permanent' translation memory for the Language Set.
Obviously, the system cannot know if the target segments have yet been translated (or, indeed, are required to be translated).
Therefore, if the 'Commit Translations' action is called before the document has been fully translated and/or approved, you may end up with "incorrect" translations in your TM.

For this reason, the 'Commit Translations' action should only ever be called from the 'Steps Completed' workflow action area, i.e., it should be with the actions that are called only when the entire job is 100% complete.

© 2009-2022 1io BRANDGUARDIAN GmbH · All rights Reserved · Legal / Privacy Policy