Release form

  • Release version: Yokohama
  • Updated December 9, 2025
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Release Form

    The Release Form feature in Digital Product Release enables product managers and release administrators to create and manage releases for product or service versions. This tool is essential for organizing and executing the release process efficiently.

    Show full answer Show less

    Key Features

    • Release Name: A unique identifier for the release.
    • Release Validates a New Product Version: Option to validate versions; affects the availability of versions and templates for selection.
    • Product or Service: Specifies the product or service related to the release.
    • Version: Selects the product or service version; list filtered based on validation settings.
    • Release Template: Defines the release process, including phases, tasks, and approvals, with availability influenced by validation settings.
    • Release Readiness Target: Indicates the expected readiness date; requirement depends on system properties.
    • Out of Band: Allows for releases not tied to existing readiness targets; requires specific configurations and roles.
    • Release Date: Specifies the date for an out-of-band release.
    • Release Calendar: Targets a calendar for scheduling the release, creating targets as necessary.

    Key Outcomes

    Utilizing the Release Form streamlines the release process by ensuring proper validation, scheduling, and adherence to predefined templates. Customers can expect enhanced organization and efficiency in managing product versions, leading to smoother release cycles.

    Product managers or release admins can create a release for a product or service version in Digital Product Release.

    For more information, see Create a release for a product or service.

    Table 1. Create release form
    Field Description
    Release name Unique release name to identify the release.
    Release validates a new product version Option to determine whether the release can validate the version.
    • If selected, the version and template selections are impacted as below:
      • Existing versions that are not validated by other releases are listed in the Version field for selection.
      • Only templates with the Validates version set to true are shown in the Release template list.
    • If cleared, the version and template selections are impacted as below:
      • All existing versions, whether validated or not, are listed in the Version field for selection. You can also add a new version as needed.
      • Templates created with the Validates version set to false are shown in the Release template list.
    Product or service Product or service for which the release is created.
    Version Version of the product or service that is included in the release.
    The list of available versions is filtered based on the Release validates a new product version field.
    • If selected, the list displays only versions that have not been used in a previous release.
    • If clear, the list displays all versions, including those with active releases.
    • If you enter a new version, it will be created and associated with the release.
    Release template Template that defines the release process. The template applies the predefined phases, tasks, policies, and approvals to this release.
    The list of available templates is filtered based on the Release validates a new product version field.
    • If selected, the list displays only templates with the validates version option set to true.
    • If clear, the list displays only templates with the validates version option set to false.
    For more information, see Create a release template.

    Based on the template you select, the release follows either a timeline-oriented or stage-oriented release process. For more information, see Release for a product or service.
    Release readiness target Release readiness target to indicate when the product or service should be ready for the release.
    Note:
    For stage-oriented releases, whether this field is required depends on the system property sn_dpr.mandate_release_target:
    • When set to false: This field is optional. You can leave it blank if needed.
    • When set to true: This field is required. You must specify a release readiness target before you can proceed.
    Note:
    Release readiness target and Release target are used interchangeably. Both terms refer to the same concept - release readiness target date.

    For more information, see Create a release readiness target.

    This field appears only when Out of band is clear.
    Out of band Option to make this release as an out-of-band release, which means it isn’t associated with any existing release readiness target. Instead, a new release readiness target is created for the selected date.
    The option to create out-of-band releases depends on the following system properties configuration:
    • out_of_band_release_allowed is set to true.
    • You have one of the roles listed in out_of_band_release_roles.
    For more information, see Digital Product Release properties.
    Release date Date of release for an out-of-band release.

    This field appears only when Out of band is selected.
    Release calendar Release calendar on which the release is targeted. If a release target exists on the selected date in the release calendar, the release is added to it. If not, a release target is created and the release is added to it.

    For more information, see Create a release calendar.

    This field appears only when Out of band is selected.