Digital Product Release properties
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.
| 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.ci\_default\_query | Defines the filter criteria applied to the Configuration Items \(CI\) list when adding CIs to a release phase. Modify this property to control which CIs are available for selection.- Type: string - Default value: life\_cycle\_stage!=End of Life^ORlife\_cycle\_stage!=End of Operation^ORlife\_cycle\_stage!=Missing^NQoperational\_status=2^ORoperational\_status=6 \(excludes End-of-Life, End-of-Operation, Missing lifecycle stages or operational status of 2 or 6\) - Other possible values: A valid filter condition for the CI list |
| 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.
|
| 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 Configure product-level release settings.
|
| 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.
|
| 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 |
| sn\_dpr\_workspace.enhancement\_work\_item\_types | Specifies the comma-separated list of work item types that can be mapped to a product enhancement. Use this property to extend the mapping beyond epics to other work item types available in your DevOps instance.- Type: string - Default value: epic - Other possible values: A comma-separated list of valid work item types \(for example, epic,feature,story\). |
Parent Topic:Digital Product Release reference