Drupal - OpenText Decision Service Integration and Automation

Common Integration Use Cases Between Drupal and OpenText Decision Service

1. Dynamic content approval routing based on content type and risk level

Data flow: Drupal ? OpenText Decision Service ? Drupal

When editors submit new pages, articles, or policy updates in Drupal, OpenText Decision Service evaluates the content type, author role, region, and compliance sensitivity to determine the required approval path. For example, a standard blog post may go directly to publishing, while a regulated service page may require legal, security, and communications review. Drupal then applies the returned decision to route the item to the correct workflow stage.

Business value: Reduces manual triage, enforces governance consistently, and shortens publishing cycles for low-risk content.

2. Personalized service eligibility decisions on public-facing forms

Data flow: Drupal ? OpenText Decision Service ? Drupal

Drupal can host application or eligibility forms for government services, education programs, or customer onboarding. Submitted form data is sent to OpenText Decision Service, which applies business rules such as residency, age, account status, or document completeness. Drupal then displays the outcome immediately, such as eligible, needs review, or not eligible, and can present the next action or required documents.

Business value: Improves user experience, reduces back-office screening effort, and ensures consistent eligibility decisions.

3. Content personalization based on audience segment and policy rules

Data flow: Drupal ? OpenText Decision Service

Drupal can request decision logic to determine which content variant, call to action, or service message should be shown to a visitor. OpenText Decision Service evaluates attributes such as user role, geography, account tier, language preference, or campaign eligibility and returns the appropriate content rule. Drupal uses the result to tailor page components, banners, and navigation options.

Business value: Enables controlled personalization without hardcoding rules into Drupal, making marketing and service updates faster and safer.

4. Automated case creation for exceptions and policy breaches

Data flow: Drupal ? OpenText Decision Service ? case management or workflow system, with status returned to Drupal

When a Drupal form submission, content request, or user action violates a policy rule, OpenText Decision Service can classify the exception and trigger a case for manual review. For example, a request for restricted information, a suspicious account registration, or a high-risk content change can be escalated. Drupal can show the user a reference number, pending status, or instructions for follow-up.

Business value: Creates a controlled exception-handling process and reduces the risk of policy violations going unnoticed.

5. Multisite governance with centralized decision rules

Data flow: Multiple Drupal sites ? OpenText Decision Service ? multiple Drupal sites

Enterprises often run several Drupal sites for brands, regions, or departments. OpenText Decision Service can centralize shared rules for publishing approvals, content classification, retention, or audience restrictions across all sites. Each Drupal instance sends relevant metadata to the decision engine and receives standardized outcomes, ensuring consistent governance while allowing local site teams to operate independently.

Business value: Standardizes policy enforcement across the organization and reduces duplicated rule maintenance across sites.

6. Product or service offer eligibility in Drupal commerce or catalog experiences

Data flow: Drupal ? OpenText Decision Service ? Drupal

For Drupal sites that present product catalogs, service bundles, or enrollment options, OpenText Decision Service can determine whether a visitor is allowed to see, request, or purchase a specific offering. Decisions can be based on customer segment, contract terms, location, age restrictions, or internal approval thresholds. Drupal then filters catalog items or enables the correct next step in the journey.

Business value: Prevents ineligible offers from being shown, reduces downstream rework, and supports compliant selling or enrollment processes.

7. Editorial exception handling for regulated or time-sensitive updates

Data flow: Drupal ? OpenText Decision Service ? Drupal

For regulated industries, some content changes require special handling, such as emergency notices, policy updates, or public safety announcements. Drupal can send the change request to OpenText Decision Service, which checks whether the update qualifies for expedited publishing, requires additional sign-off, or must be blocked until supporting evidence is attached. Drupal then routes the content accordingly and records the decision for audit purposes.

Business value: Speeds urgent publishing when appropriate while maintaining control and auditability for sensitive updates.

8. Rule-driven multilingual or regional content access control

Data flow: Drupal ? OpenText Decision Service

Drupal manages multilingual and regional content, while OpenText Decision Service can determine which language, region, or legal disclaimer should be presented based on visitor attributes and policy rules. This is especially useful for government portals, global corporate sites, and education platforms where content availability varies by jurisdiction. Drupal uses the decision output to show the correct localized content and suppress restricted material.

Business value: Improves compliance, reduces content errors across regions, and ensures users receive the right information for their location or audience segment.