OpenText Decision Service - Phrase Integration and Automation

Common Integration Use Cases Between OpenText Decision Service and Phrase

OpenText Decision Service and Phrase complement each other well in enterprise environments where content localization must follow governed business rules. OpenText Decision Service can determine what content should be localized, when it should be translated, which language variants are required, and who must approve it, while Phrase manages the translation workflow and multilingual content delivery.

1. Rule-Based Triggering of Translation Jobs for New or Updated Content

Direction: OpenText Decision Service to Phrase

When content is created or updated in a CMS, DAM, or product system, OpenText Decision Service can evaluate business rules to decide whether the asset requires localization. For example, only customer-facing content, regulated product descriptions, or region-specific campaign assets may be sent to Phrase for translation. This prevents unnecessary translation work and reduces localization costs.

• Automatically route only approved content to Phrase
• Exclude low-priority or internal-use content from translation
• Apply different rules by content type, market, or product line

2. Market-Specific Language Selection Based on Business Rules

Direction: OpenText Decision Service to Phrase

OpenText Decision Service can determine which target languages are required based on customer location, product availability, legal requirements, or channel strategy. Phrase then receives the language set and manages the translation workflow accordingly. This is especially useful for global organizations that do not translate every asset into every language.

• Translate only into languages supported in a specific market
• Apply country-specific language variants such as French for Canada or Spanish for Latin America
• Align translation scope with regional launch plans

3. Priority-Based Localization for Time-Sensitive Campaigns

Direction: OpenText Decision Service to Phrase

For marketing and digital commerce teams, OpenText Decision Service can classify content by business priority and assign expedited localization rules. High-value campaign pages, seasonal promotions, or product launch assets can be pushed to Phrase with rush handling, while standard content follows normal translation cycles. This improves launch readiness across regions.

• Fast-track high-revenue or launch-critical assets
• Assign different turnaround expectations by content category
• Support regional go-live dates with automated prioritization

4. Translation Approval and Compliance Gating Before Publication

Direction: Bi-directional

OpenText Decision Service can enforce approval rules before localized content is released to downstream systems. Phrase can return translation status, completion, or reviewer outcomes, and OpenText Decision Service can decide whether the content is ready for publication or requires additional review. This is valuable for regulated industries such as healthcare, financial services, and manufacturing.

• Block publication until required translations are completed
• Require legal or compliance review for specific content types
• Route exceptions to manual review when translation quality thresholds are not met

5. Automated Fallback Language and Content Substitution Rules

Direction: Bi-directional

If a translation is delayed or unavailable in Phrase, OpenText Decision Service can determine fallback behavior based on business policy. For example, the system may allow publication in a default language, substitute approved legacy content, or suppress the asset in a specific market. This helps maintain customer experience while avoiding incomplete or non-compliant content.

• Use fallback content when a translation is not ready
• Suppress content in markets where localization is mandatory
• Apply different fallback rules by channel or product category

6. Dynamic Routing of Content to Human or Machine Translation

Direction: OpenText Decision Service to Phrase

OpenText Decision Service can decide whether content should be sent to human translators or machine translation in Phrase based on content sensitivity, volume, urgency, and quality requirements. For example, internal knowledge articles may use machine translation, while legal disclaimers or customer-facing product copy may require human review. This optimizes cost and turnaround time.

• Use machine translation for low-risk, high-volume content
• Use human translation for regulated or brand-sensitive content
• Apply different workflows by content risk score

7. Localization Exception Handling and Escalation Workflow

Direction: Phrase to OpenText Decision Service

When translators, reviewers, or localization managers flag issues in Phrase such as terminology conflicts, missing source content, or quality concerns, those exceptions can be sent to OpenText Decision Service for rule-based routing. The decision engine can determine whether the issue should go to legal, product management, marketing, or a regional approver. This reduces manual coordination and speeds resolution.

• Route translation exceptions to the correct business owner
• Escalate blocked content based on SLA thresholds
• Standardize exception handling across teams and regions

8. Content Release Governance for Multilingual Product and Regulatory Updates

Direction: Bi-directional

For product updates, policy changes, or regulatory notices, OpenText Decision Service can govern the release sequence across languages and regions. Phrase provides the localized versions, while the decision engine ensures that no market receives the update until required translations, approvals, and dependencies are complete. This is useful for coordinated global launches and compliance-driven communications.

• Synchronize multilingual release readiness across markets
• Prevent partial publication of regulated updates
• Coordinate product, legal, and localization teams through a single decision framework

Together, OpenText Decision Service and Phrase create a controlled localization operating model where business rules determine translation scope, priority, approval, and release timing, while Phrase executes the multilingual workflow efficiently.