Home | Connectors | OpenText Core Case | OpenText Core Case - OpenText Core Signature Integration and Automation
OpenText Core Case and OpenText Core Signature complement each other well in workflows that require both structured case management and legally binding document approval. Core Case provides the controlled process, task tracking, and case visibility, while Core Signature adds secure electronic signing to finalize documents and approvals.
Flow: OpenText Core Case to OpenText Core Signature and back to OpenText Core Case
When a customer complaint escalates to a formal resolution, the case manager can generate a settlement letter or agreement from the case record and send it for electronic signature. After signing, the executed document is automatically returned to the case file and attached to the customer case history.
Flow: OpenText Core Case to OpenText Core Signature
In insurance or service claims workflows, the case team can route claim approval forms, release authorizations, or final payout documents for signature once the investigation is complete. The signed documents are then used to close the case and trigger downstream processing.
Flow: OpenText Core Case to OpenText Core Signature and back to OpenText Core Case
HR teams can manage employee-related cases such as policy exceptions, disciplinary actions, or leave approvals in Core Case. If a signed acknowledgement is required, the relevant document is sent to Core Signature and the completed signature record is stored in the employee case.
Flow: OpenText Core Case to OpenText Core Signature
When a contract deviates from standard terms, the exception can be managed as a case with tasks for legal, procurement, and business approvers. Once the exception is approved, the final contract or addendum is sent for signature and the executed version is linked back to the case.
Flow: OpenText Core Case to OpenText Core Signature and back to OpenText Core Case
Compliance teams can use Core Case to manage investigations, evidence collection, and corrective actions. If a remediation plan or attestation must be formally approved, it is routed through Core Signature and then stored with the compliance case as proof of completion.
Flow: OpenText Core Case to OpenText Core Signature
During onboarding, Core Case can manage the checklist of required steps such as identity verification, account setup, and service validation. Once the onboarding package is ready, the service agreement or consent form is sent to Core Signature for execution before the case is marked complete.
Flow: Bi-directional between OpenText Core Case and OpenText Core Signature
For operational requests such as policy exceptions, special pricing approvals, or service waivers, Core Case manages the request, review tasks, and decision history. If approval requires a signed document, Core Signature captures the signature and returns the signed record to the case for final disposition.
These integrations help organizations connect case-driven work with legally binding signatures, reducing manual handoffs while improving compliance, traceability, and cycle time.