OpenText Core Signature - Nuxeo Integration and Automation

Common Integration Use Cases Between OpenText Core Signature and Nuxeo

1. Contract approval and execution workflow

Data flow: Nuxeo ? OpenText Core Signature ? Nuxeo

Legal, procurement, and sales teams can store draft contracts in Nuxeo, route them for signature through OpenText Core Signature, and automatically return the fully executed agreement to Nuxeo for final archiving and retention. This creates a controlled end-to-end contract lifecycle with version tracking, auditability, and faster turnaround times.

• Draft contract stored and versioned in Nuxeo
• Signature package sent to OpenText Core Signature for approval
• Signed document and audit trail returned to Nuxeo
• Final agreement indexed for search, retention, and downstream use

2. Employee onboarding document signing

Data flow: Nuxeo ? OpenText Core Signature ? Nuxeo

HR teams can manage onboarding packets in Nuxeo, including offer letters, policy acknowledgements, and tax forms, then send selected documents to OpenText Core Signature for legally binding signatures. Once completed, signed records are stored back in Nuxeo as part of the employee file, reducing manual handling and improving compliance.

• Onboarding packet assembled in Nuxeo
• Candidate signs offer and policy documents in OpenText Core Signature
• Completed forms automatically archived in Nuxeo
• HR gains a complete digital employee record

3. Customer onboarding and account opening

Data flow: Nuxeo ? OpenText Core Signature ? Nuxeo

Financial services, insurance, and B2B sales teams can use Nuxeo to manage customer onboarding files such as applications, disclosures, and supporting documents. OpenText Core Signature handles the signature step for agreements and consent forms, while Nuxeo retains the signed package and related evidence for audit and customer service follow-up.

• Application documents collected and organized in Nuxeo
• Signature request sent for terms, disclosures, or consent forms
• Signed documents returned to Nuxeo automatically
• Customer file remains complete and searchable

4. Supplier and procurement agreement management

Data flow: Nuxeo ? OpenText Core Signature ? Nuxeo

Procurement teams can manage supplier contracts, NDAs, and statements of work in Nuxeo, then route final versions to OpenText Core Signature for supplier approval. After signing, the executed documents are stored in Nuxeo with metadata such as supplier name, contract term, renewal date, and category, enabling better contract governance and renewal tracking.

• Procurement creates or reviews agreement in Nuxeo
• Supplier signs via OpenText Core Signature
• Executed agreement returned to Nuxeo
• Metadata supports renewal alerts and contract reporting

5. Policy acknowledgement and compliance attestation

Data flow: Nuxeo ? OpenText Core Signature ? Nuxeo

Compliance and internal communications teams can publish policies, code of conduct documents, or annual attestations in Nuxeo and send acknowledgement forms through OpenText Core Signature. Signed acknowledgements are then stored back in Nuxeo to provide a defensible record for audits, regulatory reviews, and internal controls.

• Policy document managed in Nuxeo
• Employees or contractors sign acknowledgement in OpenText Core Signature
• Signed attestations archived in Nuxeo
• Audit teams can retrieve proof of compliance quickly

6. Document package assembly for external review

Data flow: Nuxeo ? OpenText Core Signature ? Nuxeo

Project teams can use Nuxeo to assemble a controlled document package, such as a bid response, partner agreement, or regulated submission, and send only the required signature pages through OpenText Core Signature. This reduces errors by ensuring the correct version is signed and then preserved in Nuxeo as the authoritative record.

• Controlled document set assembled in Nuxeo
• Only signature-relevant documents routed to OpenText Core Signature
• Signed package returned to Nuxeo
• Final version retained with supporting materials

7. Signed document ingestion for downstream content workflows

Data flow: OpenText Core Signature ? Nuxeo

When documents are signed in OpenText Core Signature outside of a broader content process, the completed files can be automatically ingested into Nuxeo for classification, retention, and reuse. This is useful for organizations that want Nuxeo to serve as the central content repository while OpenText Core Signature remains the execution layer for approvals.

• Signed document and audit trail sent from OpenText Core Signature to Nuxeo
• Nuxeo applies metadata, retention rules, and access controls
• Document becomes available for search and downstream business processes
• Reduces duplicate storage and manual filing

8. Bi-directional status synchronization for approval visibility

Data flow: Bi-directional

Business users working in Nuxeo can see the real-time signature status from OpenText Core Signature, while signature completion events can trigger workflow updates in Nuxeo. This gives legal, HR, procurement, and operations teams a single view of document progress without switching systems, improving follow-up and reducing delays.

• Nuxeo displays signature status and signer progress
• OpenText Core Signature sends completion or reminder events
• Nuxeo workflow updates based on signature milestones
• Teams gain visibility into bottlenecks and pending approvals