Digital Product Release properties

  • Release version: Australia
  • Updated March 12, 2026
  • 5 minutes to read

    • Configure the system properties to customize various features of Digital Product Release according to your organization's needs.

    These properties are available for Digital Product Release.
    Note:
    To open the System Properties [sys_properties] table, enter sys_properties.list in the navigation filter.
    Table 1. Properties for Digital Product Release
    Property Description

    sn_dpr.auto_transition_release_to_completed

    		 Determines whether a release can be automatically moved from the Review state to Completed state when its review is finished.
    • Type: true|false
    • Default value: false
    • Other possible values: true

    sn_dpr.auto_transition_release_to_review

    		 Determines whether a release can be automatically moved from the In Progress state to Review state when all its phases are completed.
    • Type: true|false
    • Default value: true
    • Other possible values: false

    sn_dpr.complete_phase_override

    		 Enables users with specific roles to complete a release phase. The default role, sn_dpr_model.release_admin, is set in the Value field. You can append additional roles that have write access to the release phase state, separated by commas.
    • Type: string
    • Default value: sn_dpr_model.release_admin
    • Other possible values: Roles that have write access to the release phase state.

    sn_dpr.mandate_release_target

    		 Determines whether selecting a release target is mandatory for a stage release.
    • Type: true|false
    • Default value: false
    • Other possible values: true

    sn_dpr.max_template_duration

    		 Specifies the maximum number of days for the duration of a release template. It is the total duration of all phases included in the template.
    • Type: Integer
    • Default value: 730 days
    • Other possible values: An integer value

    sn_dpr.multi_product.create_independent_releases
    Determines whether to create individual releases that can be managed independently for each product selected during release creation.
    • When set to false, a main release is created for the primary product or service that includes individual releases for each product as dependent releases.
    • When set to true, a release bundle is created that includes independent releases for each included product.
    For more information, see Create a release with a wizard.
    • Type: true|false
    • Default value: false
    • Other possible values: false

    sn_dpr.multi_product.included_products_limit
    Specifies the maximum number of products that can be added as Included products when creating a multi-product release. For more information, see Create a release with a wizard.
    Note:
    This property is applicable only if sn_dpr.multi_product.create_independent_releases is set to true.
    • Type: Integer
    • Default value: 10
    • Other possible values: An integer value

    sn_dpr.out_of_band_release_allowed

    		 Determines whether a release can be created on any given date, without a release target.
    Note:
    When the property is set to true, you can still set out-of-band release targets at individual product level from the product's release settings. For more information, see .
    • Type: true|false
    • Default value: true
    • Other possible values: false

    sn_dpr.out_of_band_release_roles

    		 Specifies the comma-separated list of roles that can create a one-off release.
    • Type: string
    • Default value: sn_dpr_model.release_admin

    sn_dpr.release_calendar_exclusions

    Restricts the schedules shown as part of release calendar using the encoded query.

    You can use an encoded query on the cmn_schedule table to filter and show specific schedules in the Exclusion schedules field on the Release calendar dialog box. Blackout and Maintenance schedules are included by default.

    • Type: string
    • Default value: None (empty string)

    sn_dpr.release_kanban_lanes

    		 Specifies the task state IDs to display as lanes on the Kanban board view in the Release tasks page. Each value corresponds to a task state. By default, three lanes (Open, Work in Progress, and Closed Complete) are displayed. To display a custom task state as a lane, add its state ID to this property as a comma-separated value.
    • Type: string
    • Default value: 1,2,3

    sn_dpr.sequential_task_execution

    		 Determines whether tasks in a phase of a release are processed one after the other.

    When this property is set to true, tasks are processed in sequential order. At the start of a phase, the task with the lowest order in it is set to the Open state. After this task is completed, the next task in the order is opened. This process continues for the remaining tasks in the phase. If the task is an approval task, the state is moved to the Requested state.

    When this property is set to false, tasks are not processed in sequential order. Instead, all its tasks are set to the Open state at the start of the phase.

    • Type: true|false
    • Default value: true
    • Other possible values: false

    sn_dpr.stage_workflow_auto_transition

    		 Determines whether a stage-oriented release and its phases can automatically transition between states through the scheduled job.

    If this property is set to false, the phases of the release will not transition between states, even if they comply with mapped policies.

    • Type: true|false
    • Default value: true
    • Other possible values: false

    sn_dpr.VulnerabilitiesTypeMapping

    		 Customizes the levels mapped to various types of vulnerabilities so that they can be represented in the Vulnerabilities widget in the Release Quality dashboard.

    sn_dpr_model.allow_any_release_dates

    		 Controls whether you can create timeline releases with flexible date configurations, even if the release start date is in the past.
    • When set to false (default behavior):
      • Restricts release creation if the release duration does not have sufficient days between today and the selected release target.
      • Restricts releases creation and retargeting with dates before today.
    • When set to true:
      • Enables creation of releases even if the start dates are before today.
      • Enables creation of tasks and key dates in the past, but only after the release start date.
      • Restricts release targets to be set to today or future dates only.
      • Enables retargeting releases with dates before today.
    • Type: true|false
    • Default value: false
    • Other possible values: true

    sn_dpr_model.release_related_task_types

    		 Specifies the comma-separated list of Task record types that can be associated with a release. Each entry includes the table name and the default view type, and the name of the list that shows up on the Release scope page of a release.
    • Type: string
    • Default value: 
      [
{"table":"incident", "view": "default", "label": "Incidents"}, 
{"table":"problem", "view": "default", "label": "Problems"}, 
{"table":"sc_request", "view": "default", "label": "Catalog requests"}
]
    • Other possible values: Other Task record types in the same format as provided in the default value.

    sn_dpr_workspace.allowed_states_for_create_auto_product_enhancement

    		 States of primary epics that are considered for automatic creation of product enhancements.
    • Type: string
    • Default value: created,planned,wip,complete,proposed,active,design,ready
    • Other possible values: You can provide new states or modify the list of existing states.

    sn_dpr_workspace.auto_create_product_enhancement_for_primary_epic

    		 Determines whether product enhancements can be automatically created for primary epics.
    • Type: true|false
    • Default value: false
    • Other possible values: true

    sn_dpr_workspace.cmdb_model_creation.supported_ci_types

    		 Specifies the comma-separated list of Configuration Item (CI) types that can be associated with products or services while requesting them. For more information, see Request a new product or service.
    • Type: string
    • Default value: cmdb_ci_service_technical, cmdb_ci_service_business, cmdb_ci_service_auto, cmdb_ci_business_app
    • Other possible values: Valid CI types