OpenText Core Content - Metadata - OpenText Core Signature Integration and Automation

Common Integration Use Cases Between OpenText Core Content - Metadata and OpenText Core Signature

1. Metadata-driven contract approval and signing workflow

Use OpenText Core Content - Metadata to classify contracts by type, region, business unit, risk level, and approval threshold before sending them to OpenText Core Signature. The metadata values determine the correct signing route, approvers, and required signature order. This reduces manual routing errors and ensures each agreement follows the right governance process.

• Data flow: OpenText Core Content - Metadata to OpenText Core Signature
• Business value: Faster contract turnaround and stronger compliance with approval policies

2. Controlled document preparation for electronic signature

Before a document is released for signature, metadata rules in OpenText Core Content - Metadata can validate that required fields are complete, such as document category, effective date, legal entity, and retention class. Only documents that meet the metadata standard are passed to OpenText Core Signature. This prevents incomplete or misclassified documents from entering the signing process.

• Data flow: OpenText Core Content - Metadata to OpenText Core Signature
• Business value: Improved data quality and fewer signing exceptions

3. Signed document capture with metadata enrichment

After signing is completed in OpenText Core Signature, the executed document is returned to OpenText Core Content - Metadata with signature status, signer identity, signing date, agreement type, and workflow reference. The content repository then stores the signed version with consistent metadata for search, audit, and retention management. This creates a reliable record of the final executed document.

• Data flow: OpenText Core Signature to OpenText Core Content - Metadata
• Business value: Better auditability, easier retrieval, and stronger records management

4. HR onboarding document classification and signing

HR teams can use metadata to classify onboarding documents such as offer letters, policy acknowledgements, tax forms, and confidentiality agreements. Based on the document type, OpenText Core Content - Metadata can trigger the correct signing package in OpenText Core Signature for the new hire. Once signed, the completed documents are stored back with metadata that supports employee file organization and compliance reporting.

• Data flow: Bi-directional
• Business value: Faster onboarding, reduced HR administration, and consistent employee records

5. Customer onboarding package orchestration

For customer onboarding, OpenText Core Content - Metadata can classify forms and agreements by product, customer segment, geography, and regulatory requirement. That metadata can drive the signature sequence in OpenText Core Signature, ensuring the right documents are signed in the right order. After completion, signed files are returned with metadata for customer file management and downstream service activation.

• Data flow: Bi-directional
• Business value: Shorter onboarding cycles and fewer compliance gaps

6. Policy acknowledgement and compliance attestation

Organizations can manage policy documents in OpenText Core Content - Metadata with controlled vocabularies for policy type, audience, version, and review cycle. When a policy requires employee acknowledgement, the metadata can initiate a signature workflow in OpenText Core Signature. Signed acknowledgements are then stored with the policy record, making it easy to prove compliance during audits.

• Data flow: OpenText Core Content - Metadata to OpenText Core Signature, then back to OpenText Core Content - Metadata
• Business value: Stronger compliance evidence and simplified audit preparation

7. Audit-ready retention and legal hold support for signed records

Once a document is signed, OpenText Core Content - Metadata can apply retention labels, legal hold indicators, and classification tags based on document type and jurisdiction. This ensures signed records are managed according to corporate policy and regulatory requirements. The integration helps legal and records teams maintain control over executed documents throughout their lifecycle.

• Data flow: OpenText Core Signature to OpenText Core Content - Metadata
• Business value: Improved records governance and reduced legal risk

8. Search and reporting on signature status across content repositories

By storing signature-related metadata in OpenText Core Content - Metadata, business users can search for documents by signing status, signer, completion date, department, or agreement category. This supports operational reporting for procurement, legal, HR, and sales teams. Leaders gain visibility into where documents are stuck and which processes need attention.

• Data flow: OpenText Core Signature to OpenText Core Content - Metadata
• Business value: Better operational visibility and faster issue resolution