Home | Connectors | Acquia DAM (Widen) | Acquia DAM (Widen) - OpenText Decision Service Integration and Automation

Acquia DAM (Widen) - OpenText Decision Service Integration and Automation

Integrate Acquia DAM (Widen) Digital Asset Management (DAM) and OpenText Decision Service Business Transaction Management 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 Acquia DAM and OpenText Decision Service

  • Brand asset approval routing based on business rules
    Acquia DAM can send new or updated assets to OpenText Decision Service to determine the required approval path based on metadata such as asset type, region, product line, campaign, or intended channel. For example, a regulated product image may require legal and compliance review, while a standard social graphic may only need marketing approval. This reduces manual routing, shortens review cycles, and ensures the right stakeholders approve the right content.
  • Automated asset publishing eligibility decisions
    When an asset is ready for distribution in Acquia DAM, OpenText Decision Service can evaluate whether it meets publishing rules before it is released to portals, CMS, or e-commerce systems. Rules can check for approved status, usage rights, expiration dates, language variants, and required metadata completeness. This helps prevent unapproved or non-compliant assets from being published and reduces downstream rework.
  • Region-specific content access and distribution control
    Acquia DAM can pass asset and user context to OpenText Decision Service to determine which assets a user, partner, or distributor is allowed to access based on geography, business unit, contract terms, or campaign eligibility. The decision engine can return allow, deny, or restricted access outcomes, enabling consistent enforcement of distribution policies across portals and external sharing channels.
  • Dynamic asset transformation rules for channel-specific delivery
    When Acquia DAM delivers assets to downstream systems, OpenText Decision Service can decide which rendition, crop, format, or version should be used based on the target channel, device type, or market. For example, it can direct the DAM to provide a square image for social media, a high-resolution version for print, or a localized version for a regional website. This improves content relevance and reduces manual asset preparation.
  • Compliance and rights management decisioning for expired or restricted assets
    Acquia DAM can trigger OpenText Decision Service when an asset approaches expiration or has usage restrictions. The decision engine can determine whether the asset should be archived, flagged for review, automatically removed from portals, or replaced with an approved alternative. This is especially valuable for organizations managing licensed photography, seasonal campaigns, or regulated product content.
  • Priority-based workflow escalation for high-value assets
    Acquia DAM workflow events can be evaluated by OpenText Decision Service to assign priority and escalation rules. For example, assets tied to a major product launch, executive campaign, or retail promotion can be routed to expedited review paths with tighter service-level expectations. This helps marketing teams focus attention on business-critical content and avoid launch delays.
  • Automated partner portal personalization and entitlement decisions
    Acquia DAM portals can use OpenText Decision Service to determine which collections, folders, or asset types should be visible to each external partner. Decisions can be based on partner tier, contract status, product authorization, or campaign participation. This creates a more controlled self-service experience for agencies, resellers, and distributors while reducing administrative overhead for the DAM team.
  • Metadata-driven exception handling for incomplete or nonstandard assets
    When Acquia DAM receives assets with missing or inconsistent metadata, OpenText Decision Service can decide whether the asset should be rejected, sent for enrichment, or allowed into a limited review state. For example, a product image without a usage-rights field may be blocked from distribution until the required information is added. This improves asset quality and keeps governance rules consistent across teams.

How to integrate and automate Acquia DAM (Widen) with OpenText Decision Service using OneTeg?