Home | Connectors | OpenText Content Metadata Service - Dictionary | OpenText Content Metadata Service - Dictionary - Microsoft Planner Integration and Automation
Use OpenText Content Metadata Service - Dictionary to define approved metadata fields such as document type, retention class, business unit, and confidentiality level, then sync those values into Microsoft Planner task labels, buckets, or checklist conventions. This helps teams manage content governance work with consistent terminology across legal, records, and content operations teams.
When content is classified in OpenText using dictionary-controlled metadata, the integration can automatically create Planner tasks for the right team based on the metadata values. For example, content tagged as ?HR policy? can trigger a review task for the HR operations team, while ?contract? content can route to legal reviewers.
Organizations can use the OpenText dictionary as the master source for controlled terms such as region, department, project stage, or content category, and expose those terms in Microsoft Planner to standardize how teams categorize tasks. This is especially useful when multiple departments manage content-related projects and need consistent reporting across plans.
If a content item?s metadata changes in OpenText, such as a status moving from ?draft? to ?approved? or a retention category being updated, the integration can update the related Planner task status or checklist. This keeps project teams informed without requiring them to check the content system manually.
When content is tagged with exception-related metadata in OpenText, such as ?missing owner,? ?policy conflict,? or ?expired review date,? the integration can create an escalation task in Microsoft Planner for the responsible team. This supports structured handling of content issues that require follow-up across compliance, records, and business owners.
During ECM, DAM, or information governance initiatives, OpenText metadata dictionaries can define the migration categories and target classification rules, while Microsoft Planner manages the execution tasks for migration teams. Tasks can be generated for activities such as metadata mapping, validation, quality review, and exception remediation.
When the OpenText dictionary is updated with new fields, revised definitions, or changed controlled vocabularies, Microsoft Planner can be used to assign change management tasks to data stewards, application owners, and training coordinators. This ensures downstream teams are notified, trained, and aligned before the new metadata model goes live.