Welcome
Integrating
You can integrate DevOps Plan with other software by adding packages to existing schema.
Integrating with other products
You can integrate DevOps Plan with other software by adding packages to existing schema.
About integration packages, configuration, and testing
Before integration, you must ensure that the data from the integrated application is compatible with the code page for the DevOps Plan database. If you add additional record types after adding a package, you can enable the package functionality for those record types using the Designer.
Testing integrations
To avoid problems with your database, you should add integration packages in a test environment before modifying your production environment.

Overview
Learn general information about the product.
Install and deploy DevOps Plan
Find information about installing and deploying DevOps Plan client and server software.
Developing
Learn how to develop schemas by using the DevOps Plan Designer.
Integrating
You can integrate DevOps Plan with other software by adding packages to existing schema.
- Integrating with other products
  You can integrate DevOps Plan with other software by adding packages to existing schema.
  - About integration packages, configuration, and testing
    Before integration, you must ensure that the data from the integrated application is compatible with the code page for the DevOps Plan database. If you add additional record types after adding a package, you can enable the package functionality for those record types using the Designer.
    - Ensuring code page compatibility for DevOps Plan integrations
      All data in a DevOps Plan database must be from the same code page. For successful integration, make sure that data sent from the integrated product is compatible with the DevOps Plan code page.
    - Enabling record types for integrations
      Some packages enable existing record types in a schema. When you install these packages, you can select the record types to enable for the package. If you add a new record type after adding the package, you can use the Designer to enable the new record type with the package functionality.
    - Testing integrations
      To avoid problems with your database, you should add integration packages in a test environment before modifying your production environment.
    - DevOps Plan integration packages
      An integration package integrates an external product with DevOps Plan. Following is a summary of the DevOps Plan integration packages.
    - Aha! integration with DevOps Plan (unidirectional)
      Aha! is a comprehensive product management software that empowers teams to build and market products customers want, by providing robust tools for strategic planning, roadmapping, and collaboration. The integration between Aha! and DevOps Plan is designed to streamline the management of the records. The unidirectional sync ensures that the items (defined in the mapping configuration) created in Aha! are automatically reflected in DevOps Plan, enhancing visibility and coordination across platforms.
Extending product function
Learn how to extend the product.

Testing integrations

To avoid problems with your database, you should add integration packages in a test environment before modifying your production environment.

Once you add packages to a schema, check in the schema, and apply the schema to your user database, you cannot undo the changes. When performing a test integration, replicate both production environments: the DevOps Plan environment, and the environment of the application being integrated with DevOps Plan. For example, in a DevOps Plan and HCL VersionVault integration, you need:

A test DevOps Plan database
A test DevOps Plan schema
A test HCL VersionVault VOB