OpenText Developer Admin - IM Developer Administration - Microsoft Planner Integration and Automation

Common Integration Use Cases Between OpenText Developer Admin - IM Developer Administration and Microsoft Planner

1. Integration project task creation from OpenText environment changes

Direction: OpenText Developer Admin - IM Developer Administration ? Microsoft Planner

When integration administrators create or update APIs, credentials, or messaging artifacts in OpenText Developer Admin, a corresponding Planner task can be created for implementation, testing, or review. This helps project teams track environment-related work in the same place they manage delivery tasks.

• Automatically create a Planner task when a new integration artifact is registered
• Assign tasks to developers, testers, or release managers
• Include environment details, artifact names, and due dates in the task description

Business value: Improves visibility into integration work and reduces missed handoffs between platform administration and delivery teams.

2. Approval workflow for credential and API access requests

Direction: Microsoft Planner ? OpenText Developer Admin - IM Developer Administration

Teams can use Planner to manage requests for new API credentials, access to integration environments, or changes to messaging configurations. Once a task is approved in Planner, the request can trigger an update or provisioning action in OpenText Developer Admin.

• Planner task used as the intake and approval record
• Approved requests trigger configuration updates in OpenText
• Task status reflects whether access has been provisioned

Business value: Creates a controlled, auditable process for access management and reduces manual coordination.

3. Release readiness tracking for Trading Grid integration changes

Direction: OpenText Developer Admin - IM Developer Administration ? Microsoft Planner

When integration teams prepare changes in OpenText, such as new mappings, endpoints, or credentials, Planner can be used to track release readiness activities. Tasks can be generated for validation, peer review, documentation updates, and deployment approval.

• Link OpenText configuration changes to release checklist tasks
• Track dependencies across development, QA, and operations teams
• Use Planner buckets for stages such as build, test, and deploy

Business value: Supports disciplined release management and reduces production deployment risk.

4. Incident follow-up and remediation task management

Direction: OpenText Developer Admin - IM Developer Administration ? Microsoft Planner

If an integration issue is detected in OpenText, such as a failed credential update or messaging configuration problem, a Planner task can be created for remediation. This ensures operational issues are assigned, tracked, and resolved within the team workflow.

• Create tasks from integration exceptions or admin events
• Assign ownership to support or engineering teams
• Capture root cause, corrective action, and resolution date in Planner

Business value: Improves incident accountability and shortens time to resolution.

5. Environment onboarding for new integration projects

Direction: Microsoft Planner ? OpenText Developer Admin - IM Developer Administration

When a new integration project is launched, Planner can manage onboarding tasks such as environment setup, credential requests, API registration, and artifact configuration. Once tasks are completed, the corresponding actions can be executed or recorded in OpenText Developer Admin.

• Use Planner as the project onboarding checklist
• Track completion of environment prerequisites
• Synchronize task completion with OpenText setup activities

Business value: Standardizes project startup and reduces delays caused by missing technical prerequisites.

6. Change request coordination across integration and business teams

Direction: Bi-directional

Business teams can raise change requests in Planner for new partner connections, API updates, or messaging changes. Integration administrators can then update the OpenText environment and feed status back into Planner so stakeholders can monitor progress without needing direct access to the platform.

• Planner captures business demand and approval status
• OpenText reflects technical implementation progress
• Both teams share a single view of request status

Business value: Aligns business priorities with technical execution and improves transparency.

7. Compliance and audit task tracking for integration administration

Direction: OpenText Developer Admin - IM Developer Administration ? Microsoft Planner

Administrative actions in OpenText, such as credential rotation, environment segregation checks, or API access reviews, can generate recurring Planner tasks for compliance teams. This helps ensure required reviews and controls are completed on schedule.

• Schedule recurring review tasks in Planner
• Track evidence collection and approval steps
• Link tasks to specific environments or integration assets

Business value: Strengthens governance and supports audit readiness for integration operations.

8. Cross-functional delivery coordination for integration enhancements

Direction: Bi-directional

For larger integration enhancements, OpenText Developer Admin can provide the technical source of truth for APIs, credentials, and messaging artifacts, while Microsoft Planner manages delivery tasks across development, QA, operations, and business stakeholders. Status updates can flow both ways to keep work aligned.

• Technical milestones in OpenText drive task updates in Planner
• Planner task completion can trigger next-step configuration work
• Useful for multi-team integration programs and recurring releases

Business value: Improves coordination across teams and reduces delivery friction in complex integration programs.