OpenText Extended ECM - Business Workspaces - OpenText Developer Admin - IM Developer Administration Integration and Automation

Common Integration Use Cases Between OpenText Extended ECM - Business Workspaces and OpenText Developer Admin - IM Developer Administration

1. Provision integration-ready business workspaces from approved development configurations

Data flow: OpenText Developer Admin - IM Developer Administration ? OpenText Extended ECM - Business Workspaces

When integration teams finalize APIs, credentials, and messaging artifacts in the developer administration environment, approved configuration details can be used to automatically provision or update business workspaces in Extended ECM. This ensures each workspace is created with the correct integration endpoints, security settings, and metadata mappings for the related business object.

Business value: Reduces manual setup effort, speeds deployment of new business processes, and ensures workspaces are consistently configured across projects, customers, or cases.

2. Synchronize workspace metadata with integration environment settings

Data flow: Bi-directional

Extended ECM business workspaces can expose business context such as customer ID, project code, or case number, while Developer Admin maintains the corresponding integration artifacts and environment parameters. A bi-directional integration can keep workspace metadata aligned with the correct development or test environment, helping teams validate integrations against the right business records.

Business value: Improves traceability between business content and technical configuration, reducing errors during testing, release validation, and support.

3. Control workspace access based on integration roles and credentials

Data flow: OpenText Developer Admin - IM Developer Administration ? OpenText Extended ECM - Business Workspaces

Developer Admin can manage credentials, API access, and environment permissions for integration services that interact with Extended ECM. These controls can be used to determine which systems or service accounts are allowed to create, update, or retrieve workspace content and metadata.

Business value: Strengthens governance by ensuring only approved integration services can interact with sensitive business workspaces, supporting compliance and separation of duties.

4. Automate workspace creation for integration projects and release cycles

Data flow: OpenText Developer Admin - IM Developer Administration ? OpenText Extended ECM - Business Workspaces

When a new integration project is registered in Developer Admin, a corresponding workspace can be created in Extended ECM to store design documents, interface specifications, test evidence, and release approvals. This gives developers, testers, and business owners a single governed location for all project-related content.

Business value: Improves collaboration across technical and business teams, shortens onboarding for new projects, and creates a controlled audit trail for integration delivery.

5. Link business workspaces to messaging and API artifacts for operational support

Data flow: OpenText Extended ECM - Business Workspaces ? OpenText Developer Admin - IM Developer Administration

From a business workspace, support teams can reference the exact API definitions, message routes, or credentials managed in Developer Admin that support a customer, project, or case. This makes it easier to troubleshoot integration issues without searching across separate tools.

Business value: Accelerates incident resolution, improves handoff between business support and integration teams, and reduces downtime caused by configuration ambiguity.

6. Maintain audit-ready documentation for integration changes

Data flow: Bi-directional

Changes made in Developer Admin, such as credential updates, endpoint changes, or messaging configuration revisions, can be documented in the related Extended ECM workspace. In return, business approvals, change requests, and implementation notes stored in the workspace can be linked back to the technical configuration record.

Business value: Creates a complete audit trail for change management, supports regulatory and internal compliance requirements, and improves accountability across teams.

7. Support controlled promotion from development to production

Data flow: OpenText Developer Admin - IM Developer Administration ? OpenText Extended ECM - Business Workspaces

Developer Admin can manage the promotion of integration artifacts from development to test and production environments. Extended ECM business workspaces can store the business approval records, test sign-offs, and deployment checklists required before promotion occurs.

Business value: Reduces deployment risk, enforces release governance, and ensures production changes are backed by approved business documentation.

8. Provide a single business context for integration-driven customer or project operations

Data flow: Bi-directional

For customer onboarding, project delivery, or case management, Extended ECM can serve as the business-facing workspace while Developer Admin manages the technical integration layer behind it. Integration status, environment health, and configuration changes can be surfaced in the workspace, while business decisions and document approvals can be used to trigger updates in the integration environment.

Business value: Aligns business operations with technical execution, improves visibility for stakeholders, and helps teams manage complex processes with fewer handoffs and less duplication.