Welcome
Developing
Learn how to develop schemas by using the DevOps Plan Designer.
Developing Schemas
You can develop or modify schemas with the DevOps Plan Designer.
Packages and integrations
This topic explains the concepts of DevOps Plan packages and integrations.
Upgrading packages
This topic explains the concept of upgrading packages in DevOps Plan.
Upgrading schemas to new versions of packages
If you have applied a package to a schema, you can upgrade the schema to a newer version of the package when it is available.

Overview
Learn general information about the product.
Install and deploy DevOps Plan
Find information about installing and deploying DevOps Plan.
Developing
Learn how to develop schemas by using the DevOps Plan Designer.
- Developing Schemas
  You can develop or modify schemas with the DevOps Plan Designer.
  - Understanding the functions of the DevOps Plan schema developer
    This topic provides an overview of the tasks typically performed by a schema developer.
  - Overview of the DevOps Plan Designer interface
    The DevOps Plan Designer includes several different windows, or views, that you will use to perform your schema development tasks.
  - DevOps Plan schemas
    This topic explains the concept of a DevOps Plan schema.
  - Customizing a schema
    To modify how change requests are handled, you need to use the Designer to customize the records and fields of a schema.
  - Schemas and packages
    This topic explains the concept of using schemas and packages in DevOps Plan.
  - Packages and integrations
    This topic explains the concepts of DevOps Plan packages and integrations.
    - Precautions when applying packages
      Follow these guidelines when you apply a package to a schema.
    - Packages available
      This topic lists the DevOps Plan packages that are currently available, grouped by category.
    - Overview of package application process
      This topic explains the general steps involved in applying a package to a schema.
    - Examples: The Notes, Attachments, and Email packages
      The most commonly used packages are Notes, Attachments, and Email.
    - Checking which packages have been applied to a schema
      Before you apply new packages or package versions, you can check which package versions have already been applied to a schema.
    - Upgrading packages
      This topic explains the concept of upgrading packages in DevOps Plan.
      - Upgrading schemas to new versions of packages
        If you have applied a package to a schema, you can upgrade the schema to a newer version of the package when it is available.
    - The AuditTrail and eSignature packages
    - EmailPlus package
    - Attachments package
      The Attachments package stores record attachments on an external server instead of in the DevOps Plan application.
    - Visualization package
      The Visualization package helps to enable the creation of custom Kanban boards in DevOps Plan.
    - Exploratory package
      The Exploratory package helps to enable the use of the Exploratory Test Charter feature in DevOps Plan.
    - Capacity Planning package
      The Capacity Planning package helps to enable the use of the Capacity Planning feature in HCL DevOps Plan.
  - Test Management and Requests
    You can use the DevOps Plan TestManagement and Requests feature to create and track test plans and add approval processes to the record.
  - User privileges
    This topic describes the privileges that are available for DevOps Plan users and user groups.
  - Working with users
  - Working with user groups
  - Working with Forms
    You must create a record form for each record type in your schema. You can also define a submit form for each record type.
  - Working with charts
    Charts are essential tools for visualizing data and managing projects. You can use Gantt and timeline charts for project management based on availability in different schemas.
  - Working with approvals
    Users can use Approvals to view and manage approval requests that are either pending or completed using the Pending Requests and Completed Requests tabs.
  - Creating a security model
    This topic provides an overview of the process to create a security model.
  - Using hooks to customize your workflow
    This topic provides guidelines for using hooks to implement your workflow.
  - Record locking
    When multiple users attempt to simultaneously update a record, the database locking model ensures that the update from each user succeeds as a unit, but each update overwrites the previous update.
  - Customizing the Web
    The Designer provides many ways to customize the underlying schema and functionality that the DevOps Plan accesses.
  - DevOps Plan email
    This topic provides a description of the supported DevOps Plan email features.
  - Importing data into DevOps Plan using Import feature
    The Configuration > Import feature allows teamspace admins or userdb super-users to add data to the DevOps Plan application. There are two primary methods for bulk data import: using sample data and uploading a zip file.
  - Enhancing the Export to JSON feature
    You can use the Export to JSON feature to export detailed information related to a record into a JSON format.
  - Enhanced Subscribe feature
    You can now use the Subscribe toggle-button in a work item to subscribe yourself in one-click.
  - Cloning existing records
    By cloning existing records you can create an exact copy of an existing record. This ability is useful when you have to create similar records frequently, ensuring consistency and saving time.
Integrating
You can integrate DevOps Plan with other software by adding packages to existing schema.
Extending product function
Learn how to extend the product.
Reference
Review reference information for the product.

Upgrading schemas to new versions of packages

If you have applied a package to a schema, you can upgrade the schema to a newer version of the package when it is available.

About this task

To upgrade a schema to a new version of a package:

Procedure

Start the Designer.
Click Package > Upgrade Installed Packages.
In the Upgrade Installed Packages - Select a Schema to Upgrade window, select the schema to upgrade.
The DevOps Plan application checks out the schema, identifies the packages that need to be upgraded, and determines whether those packages have prerequisites.
On the Status page, list of packages that need to be upgraded indicates the newest version of each package that is compatible with the DevOps Plan data code page of the schema repository. For schema repositories with data code pages 932 or 60932 (Japanese) or 936 (Simplified Chinese), the latest translated version is displayed. For other schema repositories, the latest English version is displayed.

Packages are applied to the schema in the correct order and the status for each is displayed.
When the upgrade process is finished, read the status message to verify that the package upgrade was successful.
Validate your changes by clicking File > Test Work.
When you finish testing, check in the schema. Click File > Check In.

Results

After the new schema version is checked in, upgrade any user databases that use an earlier version of the schema.

You can then repeat this process for the other schemas. After you have completed this process, you can verify that the new package versions have been applied by following the procedure described in Checking which packages have been applied to a schema.