Welocalize OPAL (Orchestrator)

Content is machine translated from English by Phrase Language AI.

Welocalize’s OPAL Platform is a patented agentic system which is trained for an individual enterprise and includes machine translation and LLMs to translate, assess quality and auto-edit multilingual content. This approach enables OPAL to produce very high-quality multilingual content and dramatically increases the speed and efficiency of delivery.

The integration uses two Phrase Orchestrator workflows to automate an OPAL-driven editing stage inside a Phrase project. When content enters the process, it triggers edits within OPAL and reports back into the workflow which then uploads the content back to the project.

OPAL editions are only available in the CAT web editor and not the desktop editor.

The workflows can only be published and executed with the next-gen Phrase Orchestrator Workflow Engine.

Workflow A: Trigger AI processing
- Initiates on job event (i.e. when a job completes MT pre-translation), creates the OPAL project and transfers the required information to OPAL.
- Initiates on job event (i.e. when a job completes the last workflow step of the project) and feeds the final content back to OPAL to improve the AI based process.
Workflow B: Retrieve AI results
- Receives OPAL callback when edits are complete and continues downstream processing to ensure OPAL edits are displayed in the Phrase CAT web editor interface.

Pre-requisites

The Phrase TMS project has a workflow that includes a first workflow step to inject raw machine translation. This step is usually automatically completed after the pre-translation is finished.

The pre-translations options ensure that the first step in the workflow (signalling MT injection) is auto-completed. If this step is not complete, OPAL will not execute.
There is a dedicated second workflow step for OPAL editing and locking. This workflow step will be auto-completed by the integration workflows.
A completed human editing step.
A job level text custom field created in Settings to hold the OPAL project ID as a reference value.

Required variables

These values must be defined in Orchestrator workspace before implementing the workflows:

Variable	Purpose
`opal_custom_field_id`	Points to the job level custom field in Phrase TMS storing Opal project ID metadata
`opal_api_endpoint_url`	Base URL for calling the Opal edit API
`opal_api_token`	API token used to authenticate calls into Opal
`opal_callback_url`	The webhook/trigger URL that Opal will call when edits finish

Populate Variables

Create these variables using sensible naming and match exactly:

opal_custom_field_id
opal_api_endpoint_url
opal_api_token - For security reasons, this should be marked as secret
opal_callback_url

Install the Workflows

Import Workflow B

From the Workflow page, click Create and select Workflow via Templates.

The template selection page opens.
Click on the OPAL (pt. 2): Retrieve AI results template and click Use template.

The workflow is displayed.
Click Publish and confirm the publication.
Open the workflow and copy the Trigger URL.

This URL is the webhook that Opal will call after editing.
Set this URL for the opal_callback_url variable.

Import Workflow A with variables defined and callback set:

From the Workflow page, click Create and select Workflow via Templates.

The template selection page opens.
Click on the [PART 1] AI-driven Post-Editing and Quality Estimation template and click Use template.

The workflow is displayed.
Edit the ingest filter on the trigger (the top box of the action) to ensure only projects intended to run through Opal will trigger the workflow.

E.g. add {{ $.metadata.project.name }} match OPAL_PILOT.
Ensure that filter {{ $.jobParts[0].status }} equals COMPLETED_BY_LINGUIST remains unchanged.
Click Publish and confirm the publication.

OPAL in the CAT web editor

When opening a job that has been processed by OPAL, the CAT web editor displays the Job edited by OPAL notification toast.

OPAL post-editing can result in the following outputs:

Edited target

The segment text was modified by OPAL. This is indicated by the OPAL-specific edit icon and the Edited by OPAL tooltip in the origin column.
Locked segment

The segment was either edited or intentionally left unchanged by OPAL, and then locked. This is indicated by the OPAL-specific edit icon and the Locked by OPAL tooltip.

Users can review changes between workflow steps (such as the pre-translation step, OPAL processing step, and post-OPAL human editing step) in the translation changes pane of the CAT web editor or by exporting workflow changes from the project page.