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.
Customizing the Web
The Designer provides many ways to customize the underlying schema and functionality that the DevOps Plan Web client accesses.
Using Hooks in Web
DevOps Plan Web software supports a subset of the full hook functionality, which a schema developer can set up.
Enabling Dependent Fields for Web using the packageutil command
If you want to use dependent fields in DevOps Plan Web client, you can also use the packageutil setwebdependtfields command. When using the setwebdependentfields command, you do not have the form controls limitations that you have when using depending fields in the Designer.

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.
- 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.
  - 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.
  - 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 Web client accesses.
    - Testing Schema Modifications in Web
      This topic provides guidelines for testing changes to your forms with the DevOps Plan Web client Web client.
    - Using Hooks in Web
      DevOps Plan Web software supports a subset of the full hook functionality, which a schema developer can set up.
      - Displaying Messages on the Web Client
        This topic provides guidelines that you should follow when displaying messages on the DevOps Plan Web client.
      - Enabling Dependent Fields for Web using the Designer
        If you want to use a form with dependent fields in DevOps Plan Web client, you must enable dependent fields.
      - Enabling Dependent Fields for Web using the packageutil command
        If you want to use dependent fields in DevOps Plan Web client, you can also use the packageutil setwebdependtfields command. When using the setwebdependentfields command, you do not have the form controls limitations that you have when using depending fields in the Designer.
      - Using Hooks to Detect a Web Session
        When writing hooks, you can use the DevOps Plan API to detect whether a user is using a Web client.
  - DevOps Plan email
    This topic provides a description of the supported DevOps Plan Web client email features.
  - Importing and exporting data
    This topic describes how to import and export data between DevOps Plan databases, and how to import data into a DevOps Plan database from another defect tracking system.
  - 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.
  - 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.

Enabling dependent fields for DevOps Plan Web using the packageutil command

If you want to use dependent fields in DevOps Plan Web client, you can also use the packageutil setwebdependtfields command. When using the setwebdependentfields command, you do not have the form controls limitations that you have when using depending fields in the Designer.

About this task

The configuration steps described in this section are performed using the packageutil command.

The web dependency property is generalized to apply to any field. By using the packageutil setwebdependentfields command, an administrator can modify a schema to make any fields be web dependent no matter what type of form control is used for the field.

Note: Note the following:

The schema must not be open in the designer when running the packageutil commands.
This packageutil command is only supported for setting web fields web dependent property.
The schema rev that was modified must be validated and checked in, and then a user database upgraded to use that new schema rev with the web dependency changes.

Procedure

To make a form with dependent fields available in DevOps Plan Web, run the packageutil command.

Run the packageutil command. The following example sets the Headline and Severity fields to be web dependent in the Defect record type in the DefectTracking schema in the schema repository for the dbset named Alpha. The example also includes the "-nocheckin" option.
```
packageutil setwebdependentfields -dbset Alpha admin "" DefectTracking Defect headline 1 severity 1 -nocheckin
```
Note: The value 1 sets the field to be web dependent. The value 0 clears the field as a web dependent field.
To see all the web dependent fields set by the packageutil setwebdependentfields command, see the following example:
```
packageutil showwebdependentfields -dbset Alpha admin "" DefectTracking defect
```