The Release Target Assignment Preference Use Cases
A new preference Release Target Assignment is introduced to control the selection of the default Release Target when a single eligible value exists.
As an administrator you may need to understand the purpose of the preference and how it affects the setting of the default Release Target. The preference description is as follows:
|
Name of the Preference
|
Release Target Assignment
|
|
Visibility
|
Site, Organization, Project, Library
|
|
Default
|
Apply Eligible If Default is Defined
|
|
Description
|
Controls the assignment of the release target when both a single eligible change transition and a blank option are available for selection. Select from these settings:
• Apply Eligible If Default is Defined—Apply the eligible change transition only if it matches the default value.
• Apply Eligible If Default is Undefined—Apply the eligible change transition if the default value is not set.
• Always Apply Eligible—Always apply the eligible change transition regardless of the default value.
|
The following scenarios explain how this preference controls the assignment of the release target when there is a single, multiple, or no change transition available.
Consider the following three parts:
• Part with no transition: No lifecycle transition exists for this part.
• Part with multiple transitions: Multiple transitions such as Change, Obsolescence, and Production Released.
• Part with single transition: Only one eligible transition (Change) exists.
The default value can be obtained from the Change Intent Release Targets mapping rule and the ChangeTransitions enumeration.
However, the default change transition from the mapping rule is not considered if:
• The mapping rule is not set.
• The change intent is not defined.
• The change intent is defined, but does not match the mapping rule
 |
The default value set by the mapping rule is prioritized when setting the actual release target.
|
You can define the default change transition using either the ChangeTransitions enumeration or the Change Intent Release Targets mapping rule.
You can filter eligible change transitions using the mapping rule.
If the mapping rule does not set a default value, the default from the ChangeTransitions enumeration is used.
If no default is set by the mapping rule or ChangeTransitions enumeration, then the default will be a blank value.
Consider the following eligible Change Transitions values for all three parts:
• Part with no transition: Blank
• Part with multiple transitions: Change, Obsolescence, and Production Released
• Part with single transition: Change
Assigning Release Targets When the Default Is Set— Change
Whenever default (Change) is set and eligible, either through the Change Intent Release Targets mapping rule or the ChangeTransitions enumeration, the blank value does not appear in the Release Target column of the Resulting Objects table.
• Part with no transition: Regardless of the default value set in ChangeTransitions enumeration, the Release Target column in the Resulting Objects table always shows a blank value.
• Part with multiple transitions: Change along with Obsolescence and Production Released
• Part with single transition: Change
The Release Target column of the Resulting Objects table shows the following change transition values when default is set (Change):
|
Parts
|
Apply Eligible If Default is Defined
|
Apply Eligible If Default is Undefined
|
Always Apply Eligible
|
|---|---|---|---|
|
No transition
|
Blank
|
Blank
|
Blank
|
|
Multiple transitions
|
Change along with Obsolescence and Production Released
|
Change along with Obsolescence and Production Released
|
Change along with Obsolescence and Production Released
|
|
Single transition
|
Change
|
Change
|
Change
|
Assigning Release Targets When the Default Is Not Set
When no default is set, either through the Change Intent Release Targets mapping rule or the ChangeTransitions enumeration, both the blank value and other eligible values appear in the Release Target column of the Resulting Objects table.
• Part with No Transition: Regardless of the default value set in ChangeTransitions enumeration, the Release Target column in the Resulting Objects table always shows a blank value.
• Part with Multiple Transitions: Shows blank along with Change, Obsolescence, and Production Released for all three values of the preference.
• Part with Single Transition:
◦ Shows blank along with Change when the preference value is set to Apply Eligible If Default is Defined.
◦ Shows Change when the preference value is set to Apply Eligible If Default is Undefined or to Always Apply Eligible.
The Release Target column of the Resulting Objects table shows the following change transition values when default is not set:
|
Parts
|
Apply Eligible If Default is Defined
|
Apply Eligible If Default is Undefined
|
Always Apply Eligible
|
|---|---|---|---|
|
No transition
|
Blank
|
Blank
|
Blank
|
|
Multiple transitions
|
Blank along with Change, Obsolescence, and Production Released
|
Blank along with Change, Obsolescence, and Production Released
|
Blank along with Change, Obsolescence, and Production Released
|
|
Single transition
|
Blank along with Change
|
Change
|
Change
|
Assigning Release Targets When the Default Is Not the Eligible Value—Revise
The Release Target column of the Resulting Objects table shows the following change transition values when default is not the eligible value:
|
Parts
|
Apply Eligible If Default is Defined
|
Apply Eligible If Default is Undefined
|
Always Apply Eligible
|
|---|---|---|---|
|
No transition
|
Blank
|
Blank
|
Blank
|
|
Multiple transitions
|
Blank along with Change, Obsolescence, and Production Released
|
Blank along with Change, Obsolescence, and Production Released
|
Blank along with Change, Obsolescence, and Production Released
|
|
Single transition
|
Blank along with Change
|
Blank along with Change
|
Change
|
From the above scenarios, it is observed that the Release Target column displays the change transitions based on the default settings and the Release Target Assignment preference values:
• Apply Eligible If Default is Defined
• Apply Eligible If Default is Undefined
• Always Apply Eligible
The preference Release Target Assignment controls the assignment of the release target. It displays the blank and eligible values for the following preference values:
• Blank along with eligible: When the default is not set and the preference is set to Apply Eligible If Default is Defined
• Eligible: When the default is set or not set and the preference value is set to either Apply Eligible If Default is Undefined or Always Apply Eligible.