Workflow

The connector can be configured to work in different ways. Your workflow can be manually or automated. In this documentation we will describe the default workflow and the mechanism used for this.

Default workflow

This is the steps in a manually translation workflow:

1. Select Content

Content in the PIM system equals "Entities". The entities contains a number of fields, and normally translation is performed on multi-language text fields. (LocaleString). To select what content you like to translate, you can use a number of methods. Eg:

  • Manually select Entities

  • Entities with a specific completeness value

  • Entities with a field, equals a specific value

  • or any other condition that can be detected by a "Query"

The default method is to select the entities that have the field Translation status = Need Translation, but you can select any entity you like.

2. Create Job

A job is a container for one or many entities, that need to be translated. Like a batch of content. In addition to this the job also have some meta data (fields) that describes the translation Job. For example the source and target languages, the creation time and status, etc. The job also have a Job status that indicates where in the process the translation are. A job can contain one, or many types of entities, normally it contains Products and Items.

3. Send

When a job is created and contains some entities, it can be sent to Lionbridge Freeway. After the job is sent and confirmed, the Job changes status to "Job Sent" and the included entities changes status to "In translation".

Translation

All translation is taking place in the Lionbridge Freeway platform and most of the actions are not including any activity in the PIM. When the content is translated the Job status will be be changed to "Ready for Import"

4. Receive

Translated content will be received. After this the Job status will be set to "Imported" and the included entities changes status to "Translated"

PreviousArchitectureNextInstall - inRiver PMC