OpenText Decision Service - OpenText Developer Admin - IM Developer Administration Integration and Automation

Common Integration Use Cases Between OpenText Decision Service and OpenText Developer Admin - IM Developer Administration

1. Rule-Driven API Access Approval for Integration Developers

Data flow: OpenText Developer Admin - IM Developer Administration ? OpenText Decision Service

When developers request access to APIs, messaging endpoints, or integration artifacts, OpenText Developer Admin can send the request details to OpenText Decision Service for automated approval decisions. The decision engine evaluates criteria such as environment, role, project classification, data sensitivity, and request history. Approved requests can be provisioned automatically, while exceptions are routed for manual review.

• Reduces manual approval delays for integration access
• Enforces consistent security and governance rules
• Supports separation of duties across development and production environments

2. Dynamic Credential and Environment Provisioning Based on Policy

Data flow: OpenText Decision Service ? OpenText Developer Admin - IM Developer Administration

OpenText Decision Service can determine which credentials, certificates, or environment settings should be assigned to a developer or integration project. OpenText Developer Admin then applies the approved configuration to the correct development, test, or production integration environment. This is useful when access rules vary by team, geography, application criticality, or compliance requirements.

• Improves control over sensitive integration credentials
• Reduces configuration errors during onboarding
• Speeds up environment setup while maintaining governance

3. Automated Exception Handling for Failed Integration Deployments

Data flow: OpenText Developer Admin - IM Developer Administration ? OpenText Decision Service

When an integration deployment fails due to missing artifacts, invalid mappings, expired credentials, or policy violations, OpenText Developer Admin can pass the failure context to OpenText Decision Service. The decision engine evaluates whether the issue can be auto-remediated, should be retried, or must be escalated to an integration support team.

• Shortens resolution time for deployment issues
• Standardizes incident triage across teams
• Reduces operational disruption in release cycles

4. Policy-Based Promotion of Integration Artifacts Across Environments

Data flow: Bi-directional

Integration artifacts such as API definitions, message routes, and transformation assets can be managed in OpenText Developer Admin and evaluated by OpenText Decision Service before promotion to higher environments. The decision engine can apply release policies based on test results, change risk, business criticality, and approval status. OpenText Developer Admin then executes the promotion only when policy conditions are met.

• Supports controlled release management for integration assets
• Improves auditability of environment promotions
• Helps prevent unauthorized or incomplete deployments

5. Risk-Based Access for Production Support and Emergency Changes

Data flow: OpenText Developer Admin - IM Developer Administration ? OpenText Decision Service ? OpenText Developer Admin - IM Developer Administration

During urgent incidents, OpenText Developer Admin can submit a request for temporary elevated access or emergency configuration changes. OpenText Decision Service evaluates the request against business rules such as incident severity, time window, approver identity, and asset ownership. If approved, OpenText Developer Admin grants time-bound access and logs the action for audit purposes.

• Enables faster response to production incidents
• Maintains governance over privileged access
• Creates a clear audit trail for emergency actions

6. Compliance Enforcement for Integration Development Standards

Data flow: OpenText Developer Admin - IM Developer Administration ? OpenText Decision Service

OpenText Developer Admin can send metadata about integration projects, such as endpoint type, data classification, and deployment target, to OpenText Decision Service. The decision engine checks whether the project complies with internal standards, such as encryption requirements, approved connectors, naming conventions, or segregation rules. Non-compliant projects can be blocked or flagged for remediation before deployment.

• Improves adherence to enterprise integration standards
• Reduces compliance risk in regulated environments
• Helps integration teams catch issues earlier in the lifecycle

7. Automated Onboarding for New Integration Teams and Projects

Data flow: OpenText Developer Admin - IM Developer Administration ? OpenText Decision Service ? OpenText Developer Admin - IM Developer Administration

When a new integration team or project is created, OpenText Developer Admin can initiate onboarding workflows that request required permissions, environments, and artifacts. OpenText Decision Service determines the onboarding path based on project type, business unit, and risk profile. OpenText Developer Admin then provisions the approved setup, reducing manual coordination between platform, security, and integration teams.

• Accelerates onboarding for new projects and teams
• Improves consistency in setup and governance
• Reduces dependency on manual administrative tasks

8. Change Impact Assessment for Integration Rule and Configuration Updates

Data flow: Bi-directional

When integration administrators update credentials, endpoints, or messaging configurations in OpenText Developer Admin, the change details can be evaluated by OpenText Decision Service to determine business impact. The decision engine can decide whether the change requires additional approvals, testing, or scheduling restrictions. This is especially valuable for high-volume Trading Grid environments where configuration changes can affect multiple downstream systems.

• Helps prevent unintended service disruption
• Aligns technical changes with business risk controls
• Supports safer maintenance of complex integration landscapes