Home | Connectors | OpenText Extended ECM - Business Workspaces | OpenText Extended ECM - Business Workspaces - Phrase Integration and Automation

OpenText Extended ECM - Business Workspaces - Phrase Integration and Automation

Integrate OpenText Extended ECM - Business Workspaces Document Management and Phrase Artificial intelligence (AI) apps with any of the apps from the library with just a few clicks. Create automated workflows by integrating your apps.

Common Integration Use Cases Between OpenText Extended ECM - Business Workspaces and Phrase

OpenText Extended ECM - Business Workspaces and Phrase complement each other well when organizations need governed business content management alongside scalable multilingual localization. Extended ECM provides the contextual workspace for business records, documents, and workflows, while Phrase manages translation, linguistic review, and multilingual content delivery. Together, they support controlled content handoffs, faster global publishing, and better collaboration between business, legal, and localization teams.

1. Localize customer, project, or case workspace documents

Direction: OpenText Extended ECM - Business Workspaces to Phrase

When business users store customer-facing documents in an Extended ECM workspace, selected files such as proposals, contracts, onboarding guides, or case communications can be sent to Phrase for translation. Phrase manages the translation workflow, while the translated versions are returned to the same workspace with the correct metadata and version history.

Business value: Reduces manual file handling, speeds up multilingual delivery, and keeps translated content tied to the original business record.

2. Translate regulated or approved content only after workspace approval

Direction: OpenText Extended ECM - Business Workspaces to Phrase

Content can be routed from an Extended ECM workflow only after legal, compliance, or product approval is completed. For example, a product specification or policy document is approved in the workspace, then automatically sent to Phrase for localization. This ensures translators work only on finalized content and avoids rework caused by late-stage changes.

Business value: Improves governance, prevents translation of unapproved drafts, and shortens localization cycles.

3. Return translated assets into the same business workspace for controlled publishing

Direction: Phrase to OpenText Extended ECM - Business Workspaces

After translation and review in Phrase, localized documents are pushed back into the originating Extended ECM workspace. The workspace can store each language version alongside the source file, with metadata such as language, status, reviewer, and publication date. Business teams can then use the workspace as the single controlled location for multilingual content.

Business value: Creates a reliable audit trail, simplifies content retrieval, and supports consistent publishing across regions.

4. Manage multilingual customer case communications

Direction: Bi-directional

In customer service or claims operations, case files in Extended ECM often contain correspondence, attachments, and response templates that need translation. Agents can send outbound communications to Phrase for localization, then store the translated response in the case workspace. Incoming customer documents in other languages can also be translated in Phrase and attached back to the case for review.

Business value: Improves response quality in global support operations and helps teams handle multilingual cases faster.

5. Localize project deliverables for global rollout programs

Direction: OpenText Extended ECM - Business Workspaces to Phrase

For enterprise rollout projects, such as ERP deployment, HR policy updates, or regional training programs, project workspaces in Extended ECM can hold source deliverables that need localization. Project managers can trigger translation of training guides, rollout checklists, and regional communications in Phrase, then track localized versions in the same workspace.

Business value: Keeps global rollout content organized by project, improves coordination across regional teams, and reduces missed translation dependencies.

6. Localize controlled templates and standard operating procedures

Direction: OpenText Extended ECM - Business Workspaces to Phrase

Organizations often maintain approved templates, standard operating procedures, and policy documents in Extended ECM. These controlled documents can be sent to Phrase whenever a new language is required or when a source update is approved. Phrase handles translation memory and terminology consistency, while Extended ECM preserves the governed master record.

Business value: Ensures consistent terminology across languages and reduces translation effort for recurring content.

7. Synchronize multilingual content status for operational reporting

Direction: Bi-directional

Phrase can send translation status updates such as in progress, reviewed, or completed back to Extended ECM workspace metadata. Business users can then see localization progress directly in the context of the customer, project, or case. This makes it easier for operations teams to monitor whether a document is ready for regional release.

Business value: Improves visibility, supports better planning, and reduces the need to check multiple systems for status updates.

8. Support global compliance and audit requirements for translated records

Direction: Bi-directional

For regulated industries, translated versions of policies, notices, contracts, or case records must be traceable to the source content. Extended ECM can store the governed record and its approval history, while Phrase manages translation workflow and linguistic review evidence. Together, they provide a complete chain of custody from source document to localized output.

Business value: Strengthens auditability, supports regulatory compliance, and reduces risk associated with unmanaged translations.

How to integrate and automate OpenText Extended ECM - Business Workspaces with Phrase using OneTeg?