Workflow

In the SDL Tridion CME, the business user selects the content item and clicks on Wordbee Translate, which launches Wordbee Translation Manager (short read: ‘WTM’) GUI extension. The translation option is limited to the following content types only:

WTM GUI extension, create jobs out of selected content items and allow the user to fill-in necessary details like translation job title, target languages, required date, priority, and other metadata.
The WTM GUI extension consists of WCF services (supported by Tridion as an OOTB feature), which stores translation job detail into Wordbee Translation Manager DB.
Wordbee Beebox SDL Tridion Connector windows service pings WTM DB at regular intervals and reads new translation job details. Upon the arrival of a new translation job, the connector windows service connects to SDL Tridion Core Services APIs to retrieve details of content items, for which translation has been requested. After reading the data, the connector windows service forwards content and meta-data to the Wordbee Beebox software by means of the Beebox web API.

The Wordbee Beebox software then sends items to Wordbee Translator TMS. This triggers the creation of translation jobs (or other pre-configured single or multi-stage translation workflows).
Once a translation workflow for content is completed in Wordbee Translator, translated content is retrieved by Wordbee Beebox. Beebox periodically polls Wordbee Translator for completed work.
Wordbee Beebox SDL Tridion Connector itself polls Beebox in periodic intervals. Once translated content is received, the connector uses the Core Services APIs to push translated content to SDL Tridion and updates translation job status into WTM DB.

Wordbee Translation Manager GUI extension consists of editor extension and WCF services. Editor extension posts the data to WCF services as and when key events occurred (like the creation of translation jobs, sending jobs to translation, etc.). And then the WCF service pushes translation jobs into Wordbee Translation Manager DB.

The WTM GUI extension and WCF services are hosted on the same server as SDL Tridion.
WTM DB is hosted on the same DB server as SDL Tridion.
Wordbee Beebox will be hosted in Wordbee Data Center.
Each connector installation provides localization support to a single SDL Tridion instance.
The solution seamlessly integrates with the blueprinting and localization capabilities of SDL Tridion.

Apart from the Translation request form, the GUI extension will also include two options that list all queued translation requests and all completed requests, respectively.
Beebox can handle any amount of translation volume of transactions per day.
Translation requests can include any custom metadata attached to content.
Through the configuration of the Beebox setup, translation requests can be routed into different translation workflows. In practice, this is done by first configuring one “Beebox project” per workflow (e.g. type of content, urgency, type of translators or vendors…). Then, again through configuration, we specify which metadata content routes content to which Beebox project (aka workflow).
Any metadata can be selected to be visible to the translator of the content (to give additional context).

Each Beebox project (workflow) can then be connected to a project in the Wordbee Translator platform of KLM (the TMS).

SDL Web