This article describes the direction where BeLazy imports source content from the Content and Project Hub and creates and manages a project in Phrase TMS. BeLazy has two Phrase TMS integrations, the other one is picking up content already in the Phrase TMS and processing it in a business management system or allowing the translation to happen in another translation management system, which you can read about here.
Use cases:BeLazy supports setting up projects in Phrase TMS from any of the connectors available under the Content and Project Hub. You would typically use this integration if you receive source files from the customers in any of the systems (customer portal, Email Assistant, vendor portal, CMS integration, task tracker integration, or simply the project ingestion API), or if you are receiving projects in another TMS, and would like to process the content in Phrase TMS by exporting XLIFF from the other TMS and importing the translated steps back there automatically at the end of each workflow step.
In this integration use case you are setting up projects in a dedicated Phrase instance, which is typically your preferred TMS, or you are helping your customer with project creation in their system.
The integration:
- creates a project in Phrase based on a project template,
- imports the files received using the file import settings in the template,
- manages and synchronizes data and the workflow between Phrase TMS and the business management system or the Google Sheet project management tool (the Business Management Hub),
- reassigns vendors from Phrase TMS to the business management system you are using and records the Phrase TMS vendor assignment in the Google Sheet,
- reassigns vendors set from the business management system or the Google Sheet to Phrase TMS,
- monitors job delivery in both Phrase TMS and the business management system or the Google Sheet jobs, and closes the job in the other system (direction configurable),
- exports the entire content into XLIFF at each and every workflow step and stores it in BeLazy,
- imports the uploaded XLIFF content back into Phrase TMS when closing a business management system or Google Sheet job,
- allows manual and automated jobs in the workflow.
The integration:
- creates a project in Phrase based on a project template,
- imports the files received using the file import settings in the template,
- manages and synchronizes data and the workflow between Phrase TMS and the business management system or the Google Sheet project management tool (the Business Management Hub),
- reassigns vendors from Phrase TMS to the business management system you are using and records the Phrase TMS vendor assignment in the Google Sheet,
- reassigns vendors set from the business management system or the Google Sheet to Phrase TMS,
- monitors job delivery in both Phrase TMS and the business management system or the Google Sheet jobs, and closes the job in the other system (direction configurable),
- exports the entire content into XLIFF at each and every workflow step and stores it in BeLazy,
- imports the uploaded XLIFF content back into Phrase TMS when closing a business management system or Google Sheet job,
- allows manual and automated jobs in the workflow.
Integration type:
The Phrase TMS integration utilizes the official Phrase TMS APIs. The integration requires a user to be able to set up and manage projects.
Requirements:
You need your Phrase TMS username and password with appropriate permissions.
Adding a connection:
Under Manage my translation management system in the Profile menu, add a new TMS connection:

Under the TMS Connection Settings, select the data center (EU or US), choose a name for this connector, and enter your username and password, and click Add.

Automating a connection:
Click on the cogwheel icon to automate the connection. You will see the following dialog:

Analysis settings:
Choose between BeLazy analysis or external analyses (automatically executed by the project template or some other automation):
- Use BeLazy analysis: Projects without comprehensive analysis run an analysis before creating the project in the Business Management Hub. BeLazy uses the specified Phrase-specific analysis options to give you the right results.
- Use external analyses: BeLazy waits until all necessary analyses are ready in Phrase and does not create any analysis. Each analysis needs to be created within one hour from when the project becomes available.
In the case of Plunet, you can also separate the primary (receivable) analysis and the payable analysis settings.

File settings:
- Choose which segments should be saved in the translation memory: At the end of the project BeLazy can update the Phrase TMS translation memory assigned to the project via the project template. This way you can get all segments in the TM even if your translators do not update them, or you are working offline or via third-party AI processing. You can also decide not to update the TM or only enter the segments that have confirmed status.
- Choose which XLIFF format BeLazy should work with: Phrase can export and import MXLIFF which is XLIFF 1.2-compliant or XLIFF 2.0 output, choose the one you prefer.
Unit mapping, Rate mapping, Linguist mapping, Language mapping: Please see the generic article about these mappings.
Enabling the TMS project creation in a Content and Project Hub connection, and editing the automation:
For generic information, please read the TMS Hub Integrations - Overview article first.
Initial configuration - template mapping:
BeLazy always creates projects from Phrase TMS project templates. Project templates are a good way to describe every aspect of a project, so you will need to have as many project templates as the types of projects you need to create with BeLazy. BeLazy will change the project name, languages and will use the workflow of a template configured under the workflow configuration, not here. When selecting the template, focus on the file format support and the translation memory/terminology/machine translation settings.
You always need to set up a main, standard template, but you can create as many exceptions based on the origin project's metadata as you wish.

Initial configuration - name mapping:
For each of the Phrase TMS project templates selected, you can configure different project naming rules. The default setting is to overwrite the template project name with the name of the project coming from the source system. If you want to customize this further, you can use the same editor as the instructions editor in the Edit automation dialog to change the setup. By pressing @ you get all the metadata fields that you can insert into the name. Just like everywhere else, you can set up any number of exceptions based on metadata.

Workflow configuration:
Under each and every origin workflow (in this case Workspace, could be another TMS or vendor portal or any other integration), you need to select the Phrase TMS workflow. First, you select a template name, which can be different from the workflow template used for project creation. Here the only information we take from the templates is the workflow steps, and will apply them to the Phrase TMS project created. If you expand the workflow, you can place the actual TMS workflow steps that correspond to the BMS workflow steps in the appropriate boxes. Here, the Translation step in Phrase is assigned to the Translation step in Plunet, whereas the Revision step in Phrase is assigned to the Quality assurance step in Plunet. Read the overview article to understand the general working of TMS workflow mapping.
