Release form

  • Release version: Australia
  • Updated March 12, 2026
  • 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 in Digital Product Release enables product managers and release administrators to create and manage releases for product or service versions. This form captures essential details such as release identity, version selection, templates for release processes, scheduling targets, and special release types like out-of-band releases. Understanding and correctly configuring these fields helps streamline the release lifecycle and ensures alignment with organizational release policies.

    Show full answer Show less

    Key Features

    • Release name: A unique identifier for the release to distinguish it clearly.
    • Release validates a new product version: Controls whether the release validates a new version, influencing which versions and templates are selectable:
      • If selected, only versions not previously validated by other releases are available, and only templates marked to validate versions appear.
      • If cleared, all versions are visible, including those with active releases, along with templates that do not validate versions.
    • Product or service: The specific product or service for which the release is being created.
    • Version: The product/service version included in the release. Depending on the validation setting, versions available for selection vary. New versions can be added but must have unique identifiers.
    • Release template: Defines the release process workflow, including phases, tasks, policies, and approvals. Available templates are filtered based on the validation setting and product-level release settings.
    • Release readiness target: The intended date by which the product or service should be ready for release. This field’s requirement depends on system properties and applies only when the release is not out-of-band.
    • Out of band: Allows creation of releases not tied to existing release readiness targets. This feature requires specific system property settings and user roles to enable.
    • Release date and Release calendar: Applicable only for out-of-band releases, where a new readiness target is created or the release is added to an existing target on the selected date within the specified release calendar.

    Practical Application for ServiceNow Customers

    When creating a release, customers can:

    • Ensure unique identification and proper version control by using the validation options to manage which product versions are eligible and maintain release integrity.
    • Leverage release templates to standardize release workflows, aligning with organizational policies and improving consistency in release execution.
    • Set clear release readiness targets to schedule and coordinate releases effectively, with flexibility to create out-of-band releases when immediate or unscheduled releases are necessary.
    • Utilize release calendars to manage timing and aggregation of release readiness targets, thereby enhancing planning and visibility.

    By understanding and utilizing these form fields and their configurations, ServiceNow customers can optimize release management processes within the Digital Product Release application.

    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 cleared, the list displays all versions of the product or service, including those with active releases.
    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.
    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.

    For more information, see Create a release readiness target.

    This field appears only when Out of band is clear.

    Note:
    Release readiness target and Release target are used interchangeably. Both terms refer to the same concept - release readiness target date.
    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.