OpenText DAM (OTMM) - ServiceNow Integration and Automation

Common Integration Use Cases Between OpenText DAM (OTMM) and ServiceNow

OpenText DAM (OTMM) is used to manage rich media assets such as product images, marketing content, museum collections, and broadcast video. ServiceNow is typically used to manage enterprise workflows, service requests, approvals, incidents, and operational tasks. Together, they can connect content operations with business process execution, improving speed, governance, and accountability across teams.

• Digital asset request and fulfillment workflow: Employees or business users submit requests in ServiceNow for product images, campaign assets, or video files. ServiceNow routes the request for approval, then triggers OTMM to locate, package, and deliver the approved assets. Direction: ServiceNow to OpenText DAM, with status updates back to ServiceNow. Business value: Faster asset fulfillment, fewer manual emails, and better request tracking.
• Asset access and permission requests: Teams needing access to restricted media, such as licensed broadcast footage or museum collection images, submit access requests in ServiceNow. OTMM provides the asset metadata and usage constraints, while ServiceNow manages approval workflows and audit trails. Direction: Bi-directional. Business value: Stronger governance, controlled access, and compliance with usage rights.
• Incident management for missing or incorrect media assets: If a product image is missing from a channel, or a campaign asset is incorrect, users log an incident in ServiceNow. The incident can automatically reference the related OTMM asset record, version, or metadata, helping support teams resolve issues quickly. Direction: ServiceNow to OpenText DAM. Business value: Reduced resolution time and better visibility into content-related issues.
• Content lifecycle task management: When assets in OTMM require review, re-tagging, expiration, or rights renewal, OTMM can create tasks in ServiceNow for marketing, legal, or content operations teams. ServiceNow tracks completion, escalations, and SLA compliance. Direction: OpenText DAM to ServiceNow. Business value: More reliable content governance and fewer expired or non-compliant assets in circulation.
• Campaign launch coordination: Marketing teams use OTMM to store approved campaign images and videos, while ServiceNow coordinates launch tasks across creative, legal, web, and regional teams. Asset readiness in OTMM can trigger ServiceNow tasks for downstream teams to publish or localize content. Direction: OpenText DAM to ServiceNow, with updates back to OTMM. Business value: Better launch coordination and fewer delays caused by asset readiness gaps.
• Product content distribution support: When product images or videos are updated in OTMM, ServiceNow can notify downstream support or operations teams that rely on those assets for portals, catalogs, or field service materials. This helps ensure teams are working with the latest approved content. Direction: OpenText DAM to ServiceNow. Business value: Improved content consistency across channels and reduced use of outdated media.
• Rights and compliance exception handling: If OTMM detects that an asset is nearing license expiration or has restricted usage terms, it can open a ServiceNow workflow for review, renewal, or removal. ServiceNow then coordinates legal, procurement, or compliance actions and records the outcome. Direction: OpenText DAM to ServiceNow. Business value: Lower compliance risk and better control over licensed media.
• Operational reporting for media services: ServiceNow can aggregate operational metrics such as request volume, turnaround time, and SLA performance for asset-related workflows, while OTMM provides asset usage and availability data. Together, they support reporting for content operations and service performance. Direction: Bi-directional. Business value: Better management insight and more informed resource planning.