The Automation features of Beebox are among the most exciting. While you can control each translation workflow step manually with the user interface, you can also automate some or even all operations. This includes operations such as detecting new source file, machine translation, creating new human translation jobs, exchanging jobs with translators or a TMS and creation of translated files.
Read this chapter on automation
In the following we discuss all automation options:New to Beebox: About automating workflows
Access the settings
The automation settings are accessible from the project Settings pages:
...
Specify the time interval in which Beebox will run all enabled automatic operations. When testing you may choose 10 seconds or 1 minute5 minutes. In production you would opt for 30 minutes or more. If you have a lot of projects, then your Beebox may become unresponsive if all projects are configured with very short time intervals such as 10 seconds.
...
Note: If you send files via the API you should not tick the first option.
Machine Translation
With new or changed files you can instruct the Beebox to translate any content not pretranslated from memories with a machine- or pseudo-translation system.
...
Preliminary translations mean that Beebox creates translated files from the memory and machine translated content. These preliminary files are saved to the project "OUT" directory with ".prelim" inserted into the file name. For example source file "folder\marketing.docx" will be saved as "folder\marketing.prelim.docx".
Jobs
Jobs refer to human translation work. Translations that are not approved at this workflow stage can automatically be sent to a translation team, a Wordbee Translator platform or a third party TMS.
In this screen we have disabled automatic job creation:
For an explanation of all options continue here: Configure Automation - Jobs
Target Files
This step is to automatically create and save translated files once all its content (segments) are approved.
...
The following option simply deletes files older than a few months from disk. The translated content is NOT removed from the project memory.
The option below lets you dispose of old and no longer required jobs. We recommend setting this option as keeping a large number of completed or cancelled jobs slows down overall system performance:
Scripting
You can develop a Powershell script to do custom work whenever source files are added/changed or translated files are created. For example, your script could transfer translated files to another location.
...
- For more information on Powershell scripting read: Powershell Scripts
- Beebox also lets you execute C# code to post-process translated files. See: Translated File Action
...