The Release Types table stores a record for each type of release.  The release type can have a default task workflow and documentation for release readiness and acceptance criteria. Release Types are pulled into Release records where all of the workflow and processing information is pulled in and applied to the Release.

Release types can be marked as Active or Inactive by changing the status field. Active is the default value, but the status can be set to Inactive if the release type will no longer be used.

The Clone to Create new Version button can be used to create a new release type with the Release Type, Description, Acceptance Criteria, Default Task Workflow, Release Readiness Criteria, and Task Generation Method mapped. The new release type record will appear on the screen so that any modifications can be made to these fields. The Version Number of the cloned release type is set to the previous release type version number incremented by 1.

Release Type and Version is a compound field, combining the Release Type name and the Version Number of the release type. 

Release Readiness Criteria and Acceptance Criteria and Checklist hold files describing release readiness and criteria for acceptance of the release - i.e. policies, regulations, standards, and other requirements that must be met for deployment approval. These can also include information about service validation, various test plans and other testing activities.

In the tasks section, a Default Task Workflow can be selected. This determines the Task Workflow that is chosen automatically in a new release for this release type. These can be customized and used to incorporate Service Test Models, Service Validation, and various testing activities. The Task Templates are also used to manage roles and responsibilities and schedules, and can include different activities in different deployment environments. Once a Default Task Workflow Title is selected, the task templates included in the workflow are shown in the Task Templates table below.

When the release is created and a release type selected, the workflow and other information from the release type is populated into the release.  The task templates, when generated, are created as tasks and their overall sequence and prerequisite structure is maintained.

This is a background table with no other processing, so there are no reports or other automation.