OpenText Extended ECM - Business Workspaces - OpenText Core Signature Integration and Automation

Common Integration Use Cases Between OpenText Extended ECM - Business Workspaces and OpenText Core Signature

1. Contract approval and execution workspace

Data flow: OpenText Extended ECM - Business Workspaces to OpenText Core Signature, then back to OpenText Extended ECM - Business Workspaces

Legal and procurement teams manage contract drafts, redlines, supporting documents, and approval tasks inside a business workspace tied to a supplier, customer, or project. Once the final version is approved, the document is sent to OpenText Core Signature for legally binding signatures. After completion, the signed agreement and audit trail are automatically returned to the same workspace for retention, search, and downstream process use.

Business value: Faster contract turnaround, reduced manual handoffs, and a complete governed record in one business context.

2. Customer onboarding package signing

Data flow: OpenText Extended ECM - Business Workspaces to OpenText Core Signature

During customer onboarding, a workspace is created for each new customer and contains application forms, compliance documents, service terms, and supporting evidence. Customer-facing documents that require signature are routed to OpenText Core Signature directly from the workspace. Once signed, the documents are stored back in the onboarding workspace and linked to the customer record for operational teams to continue setup.

Business value: Improves onboarding speed, reduces incomplete paperwork, and gives sales, operations, and compliance teams a shared view of progress.

3. HR employee document signing and personnel file management

Data flow: OpenText Extended ECM - Business Workspaces to OpenText Core Signature, then back to OpenText Extended ECM - Business Workspaces

HR creates a workspace for each employee or hiring case containing offer letters, policy acknowledgements, tax forms, and onboarding checklists. Documents requiring employee signature are sent to OpenText Core Signature. After signing, the completed documents are automatically filed in the employee workspace, preserving version history, metadata, and access controls for HR and audit purposes.

Business value: Streamlines hiring and employee administration while maintaining a compliant personnel record.

4. Project change order approval

Data flow: OpenText Extended ECM - Business Workspaces to OpenText Core Signature

Project managers maintain a workspace for each project with schedules, deliverables, budgets, and change requests. When scope changes require formal approval, the change order is generated from the workspace and sent to OpenText Core Signature for customer or internal stakeholder signatures. Signed change orders are then retained in the project workspace alongside the related project documents.

Business value: Reduces project delays, improves traceability of scope changes, and helps prevent disputes over approvals.

5. Supplier onboarding and compliance acknowledgements

Data flow: OpenText Extended ECM - Business Workspaces to OpenText Core Signature, then back to OpenText Extended ECM - Business Workspaces

Procurement teams use a supplier workspace to manage tax forms, insurance certificates, code of conduct acknowledgements, and banking details. Required documents are routed to OpenText Core Signature for supplier signatures and acknowledgements. Once completed, the signed records are returned to the workspace and linked to the supplier master data for ongoing compliance monitoring.

Business value: Speeds supplier setup, improves compliance control, and creates a reliable audit trail for procurement.

6. Sales proposal and order acceptance workflow

Data flow: OpenText Extended ECM - Business Workspaces to OpenText Core Signature, then back to OpenText Extended ECM - Business Workspaces

Sales teams manage proposals, pricing approvals, product sheets, and customer-specific terms inside a customer workspace. When the customer is ready to proceed, the proposal or order form is sent to OpenText Core Signature for acceptance. The signed order is returned to the workspace and can trigger follow-on activities such as fulfillment, invoicing, or account setup.

Business value: Shortens sales cycles, reduces order processing errors, and connects signed commitments to the customer record.

7. Policy acknowledgement and annual attestation management

Data flow: OpenText Extended ECM - Business Workspaces to OpenText Core Signature

Compliance or HR teams maintain a workspace for policy distribution, annual code of conduct attestations, and regulatory acknowledgements. Employees receive the required documents through OpenText Core Signature for signature or acknowledgement. Completion status is tracked back in the workspace, giving managers and auditors visibility into who has signed and who still needs follow-up.

Business value: Improves policy compliance, simplifies tracking, and reduces manual chasing of acknowledgements.

8. Case-based approval of regulated documents

Data flow: Bi-directional between OpenText Extended ECM - Business Workspaces and OpenText Core Signature

In regulated environments such as finance, healthcare, or public sector operations, a case workspace holds the full record for a claim, application, or exception request. Documents that require formal approval are sent to OpenText Core Signature, while the signed result and signature evidence are returned to the case workspace. This creates a complete, governed case file with both content and approval history in one place.

Business value: Strengthens auditability, supports regulatory requirements, and gives case workers a single source of truth.