OpenText Core Transformation Publication Service - LionBridge Integration and Automation

Common Integration Use Cases Between OpenText Core Transformation Publication Service and LionBridge

1. Multilingual regulated document publishing

Data flow: OpenText Core Transformation Publication Service ? LionBridge ? OpenText Core Transformation Publication Service

Managed source documents such as policy notices, product inserts, or compliance statements are published from OpenText for translation in Lionbridge, then returned for controlled rendering into approved output formats. This supports regulated publishing where both linguistic accuracy and format consistency are mandatory.

• Reduces manual rework across legal, compliance, and localization teams
• Ensures translated versions follow the same approved layout and structure as the source
• Speeds release of multilingual regulated content across regions

2. Automated translation of customer communications

Data flow: OpenText Core Transformation Publication Service ? LionBridge

Customer-facing letters, statements, claims notices, and service communications generated in OpenText can be automatically routed to Lionbridge for translation before final publication. This is useful for organizations that produce high volumes of personalized communications in multiple languages.

• Improves turnaround time for outbound communications
• Reduces dependence on manual file handling and email-based translation requests
• Supports consistent messaging across languages and channels

3. Localization of controlled templates and document variants

Data flow: Bi-directional

OpenText manages the master document template and publication rules, while Lionbridge provides translated text for localized variants. The integration can maintain a single controlled template set while enabling language-specific versions for different markets.

• Preserves governance over approved document structures
• Allows reuse of the same publication logic across multiple languages
• Supports faster rollout of new markets without rebuilding document templates

4. Translation workflow for product documentation and manuals

Data flow: OpenText Core Transformation Publication Service ? LionBridge ? OpenText Core Transformation Publication Service

Technical manuals, installation guides, and product documentation can be published from OpenText in source language, sent to Lionbridge for translation, and then re-ingested for final output generation in PDF, HTML, or print-ready formats. This is especially valuable for manufacturing, life sciences, and industrial organizations.

• Improves consistency across multilingual product documentation
• Supports faster publication of updated manuals and revisions
• Helps reduce risk of publishing outdated or incomplete translations

5. Global content distribution for marketing and sales collateral

Data flow: OpenText Core Transformation Publication Service ? LionBridge

Approved brochures, datasheets, and sales kits can be transformed in OpenText and sent to Lionbridge for localization before being published to regional teams or digital channels. This enables centralized control of source content while allowing local market adaptation.

• Shortens localization cycles for campaigns and launches
• Improves brand consistency across regions
• Enables regional teams to receive publication-ready assets in their language

6. Translation of compliance and policy updates

Data flow: OpenText Core Transformation Publication Service ? LionBridge ? OpenText Core Transformation Publication Service

When policies, procedures, or regulatory notices are updated in OpenText, the revised content can be routed to Lionbridge for translation and then republished in controlled formats. This is useful for enterprises that must distribute synchronized policy updates across multiple countries.

• Ensures all language versions are updated from the same source revision
• Supports auditability and version control in regulated environments
• Reduces the risk of inconsistent policy communication

7. Multilingual document production for shared service operations

Data flow: OpenText Core Transformation Publication Service ? LionBridge ? OpenText Core Transformation Publication Service

Shared service teams can use OpenText to generate standardized documents such as onboarding packs, HR letters, or service notifications, then send them to Lionbridge for translation and final publication. This creates a repeatable workflow for high-volume enterprise document operations.

• Improves operational efficiency for centralized document services
• Supports service delivery across diverse employee and customer populations
• Reduces manual coordination between content, translation, and publishing teams

8. Continuous localization for content updates

Data flow: Bi-directional

As source content changes in OpenText, only the updated sections or documents can be sent to Lionbridge for translation, then returned for republishing. This supports continuous localization for organizations with frequent content changes and multiple language requirements.

• Minimizes translation effort by focusing on changed content
• Accelerates release of updated multilingual materials
• Helps maintain alignment between source and translated versions over time