OpenText Core Signature - Microsoft Planner Integration and Automation

Common Integration Use Cases Between OpenText Core Signature and Microsoft Planner

OpenText Core Signature provides legally binding electronic signature workflows for documents, while Microsoft Planner helps teams organize tasks, assign owners, track progress, and manage work execution. Together, they can connect approval milestones with operational follow-through, improving visibility from document signing to task completion.

1. Signature Completion Triggers Project Task Creation

When a contract, policy, or onboarding document is fully signed in OpenText Core Signature, the integration automatically creates a Microsoft Planner task for the responsible team to complete the next operational step.

• Data flow: OpenText Core Signature to Microsoft Planner
• Business value: Reduces delays between approval and execution
• Example: After a vendor agreement is signed, Planner tasks are created for procurement, IT access setup, and finance onboarding

2. Pending Signature Reminders Linked to Task Management

Documents awaiting signature in OpenText Core Signature can generate or update Planner tasks for legal, HR, or sales teams so they can track outstanding approvals and follow up on overdue signers.

• Data flow: OpenText Core Signature to Microsoft Planner
• Business value: Improves accountability for time-sensitive approvals
• Example: HR receives a Planner task when a new hire has not yet signed offer documents after two business days

3. Planner Task Completion Initiates Signature Requests

When a team completes a prerequisite task in Microsoft Planner, such as document review or internal approval, the integration can trigger an OpenText Core Signature workflow for formal execution.

• Data flow: Microsoft Planner to OpenText Core Signature
• Business value: Ensures documents are only sent for signature after internal readiness checks
• Example: Once a manager marks a compensation change review task complete, the signed approval packet is sent to the employee

4. Contract Approval Workflow Coordination

Legal and procurement teams can use Planner to manage contract review tasks while OpenText Core Signature handles the final signature step. The integration keeps both teams aligned on status and next actions.

• Data flow: Bi-directional
• Business value: Improves contract cycle visibility and reduces missed handoffs
• Example: Planner tracks redline review, compliance review, and executive approval, then OpenText Core Signature is used for final execution

5. Employee Onboarding Task Orchestration

After onboarding documents are signed in OpenText Core Signature, Microsoft Planner can automatically generate tasks for IT, facilities, payroll, and the hiring manager to complete onboarding activities.

• Data flow: OpenText Core Signature to Microsoft Planner
• Business value: Creates a coordinated onboarding process across departments
• Example: Signed employment forms trigger tasks to provision accounts, prepare equipment, and schedule orientation

6. Customer Onboarding Milestone Tracking

For customer onboarding, signed agreements in OpenText Core Signature can create Planner tasks for implementation, support, and account management teams to deliver the agreed services.

• Data flow: OpenText Core Signature to Microsoft Planner
• Business value: Speeds up customer activation and improves service handoff
• Example: Once a master service agreement is signed, Planner tasks are created for kickoff scheduling, environment setup, and training delivery

7. Audit and Exception Follow-Up Management

If a signature workflow in OpenText Core Signature is delayed, rejected, or requires correction, the integration can create a Planner task for the owning team to resolve the issue and maintain audit readiness.

• Data flow: OpenText Core Signature to Microsoft Planner
• Business value: Helps teams respond quickly to exceptions and compliance issues
• Example: A rejected signature due to missing initials generates a Planner task for the contract owner to correct and resubmit the document

These integrations are most effective when OpenText Core Signature is used for formal approval and Microsoft Planner is used for downstream execution, giving organizations a clear bridge between document authorization and operational delivery.