Censhare - OpenText Decision Service Integration and Automation

Common Integration Use Cases Between Censhare and OpenText Decision Service

1. Rule-Based Content Approval and Publishing Routing

Data flow: OpenText Decision Service ? Censhare

Use OpenText Decision Service to evaluate business rules that determine how content items should move through approval and publishing workflows in Censhare. For example, a product brochure may require legal review if it contains regulated claims, while a regional campaign asset may need local brand approval based on market, language, or product category. The decision engine can automatically assign the correct workflow path, approvers, and publishing restrictions inside Censhare.

Business value: Reduces manual triage, improves compliance, and ensures content is routed consistently based on policy.

2. Automated Content Variant Selection for Markets and Channels

Data flow: Bi-directional

Censhare manages content variants, localization, and channel-specific assets, while OpenText Decision Service determines which variant should be delivered to which audience, market, or channel. For example, a retailer can use decision rules to select the correct product description, pricing disclaimer, or promotional banner based on country, customer segment, or sales channel. Censhare then publishes the approved variant to web, print, or partner portals.

Business value: Improves content relevance, reduces errors in localized publishing, and supports faster multi-market launches.

3. Regulatory and Compliance Checks Before Asset Release

Data flow: Censhare ? OpenText Decision Service ? Censhare

When a new asset is created or updated in Censhare, it can be sent to OpenText Decision Service for compliance evaluation against business rules such as mandatory disclaimers, restricted product categories, approved terminology, or market-specific legal requirements. The decision result is returned to Censhare to either approve release, trigger remediation, or block publication until issues are resolved.

Business value: Helps prevent non-compliant content from reaching customers and reduces legal and brand risk.

4. Dynamic Product Content Governance for Catalog and PIM Workflows

Data flow: OpenText Decision Service ? Censhare

In organizations using Censhare for product information and catalog production, OpenText Decision Service can govern which product data is eligible for use in specific publications. For instance, if a product is missing required attributes, has expired pricing, or is flagged for recall, the decision service can prevent it from being included in a catalog or brochure. Censhare can then exclude the item or route it for correction before production continues.

Business value: Improves data quality in published materials and reduces costly rework in print and digital production.

5. Campaign Asset Prioritization and Resource Allocation

Data flow: OpenText Decision Service ? Censhare

Marketing teams often manage competing campaign requests across regions, brands, and channels. OpenText Decision Service can apply rules to prioritize content production based on launch date, revenue impact, strategic importance, or market urgency. Censhare can use these decisions to automatically assign production tasks, allocate creative resources, and sequence asset delivery.

Business value: Helps teams focus on the highest-value work, improves throughput, and supports better campaign execution planning.

6. Personalized Content Assembly Based on Customer or Segment Rules

Data flow: OpenText Decision Service ? Censhare

OpenText Decision Service can determine which content components should be assembled in Censhare for a specific customer segment, account type, or buying stage. For example, a B2B manufacturer may use rules to decide whether a technical spec sheet, industry case study, or promotional offer should be included in a sales kit. Censhare then assembles the appropriate content package from reusable components.

Business value: Enables more targeted content delivery and improves conversion by matching content to audience needs.

7. Exception Handling for Content Workflow Escalations

Data flow: Censhare ? OpenText Decision Service ? Censhare

When content workflows in Censhare encounter exceptions such as missed deadlines, missing approvals, or conflicting version updates, OpenText Decision Service can determine the correct escalation path. Rules can define whether the item should be reassigned, escalated to a manager, paused for review, or fast-tracked based on business impact and content type.

Business value: Reduces workflow bottlenecks, improves accountability, and helps teams resolve exceptions consistently.

8. Content Lifecycle Decisions for Archiving, Renewal, and Reuse

Data flow: Bi-directional

Censhare stores content lifecycle metadata, while OpenText Decision Service applies rules to decide whether an asset should be archived, renewed, repurposed, or retired. For example, a seasonal campaign asset may be automatically archived after the promotion ends, while a high-performing evergreen asset may be flagged for reuse in future campaigns. The decision engine can also trigger review tasks in Censhare when content is nearing expiration.

Business value: Improves content governance, reduces clutter in the content repository, and increases reuse of approved assets.