In a custom portfolio segmentation, the application is segmented in a category that was not expected when the points received by the application for both segment categories are same.
For eg the user expected an application to be categorized in the Replatform segment, but it is assigned to the Retain segment. They both have the same number of points.
Details
When there is the same number of points between two segments - there is no explicit priority. it depends on how it is configured in the JSON file.
Categorization happens based on segmentRef value in the segmentation configuration JSON file.
In the JSON file below it can be seen that the segmentRef for Replatform has a higher value Custom_5RSegmentation_seg_5 while Retain has a reference Custom_5RSegmentation_seg_2 so ties are going to Replatform.
{
"segmentRef" : "Custom_5RSegmentation_seg_5",
"name" : "Replatform",
"description" : "Maintain business capabilities limiting changes that are needed to get to the new target platform",
"color" : "#345995",
"matchingRules" : [ {
"description" : "High Business Impact",
"formula" : "BI > 0",
"points" : 20
}]
}, {
"segmentRef" : "Custom_5RSegmentation_seg_2",
"name" : "Retain",
"description" : "Business application serves valuable function with clear roadmap allowing for future decisions",
"color" : "#FFFF00",
"matchingRules" : [ {
"description" : "High Business Impact",
"formula" : "BI > 0",
"points" : 20
} ]
In the JSON file below the segmentRef for Retain has a higher value: Custom_5RSegmentation_seg_6 when compared with Custom_5RSegmentation_seg_3 for Replatform so the ties are going to Retain.
{
"segmentRef" : "Custom_5RSegmentation_seg_3",
"name" : "Replatform",
"description" : "Maintain business capabilities limiting changes that are needed to get to the new target platform",
"color" : "#345995",
"matchingRules" : [ {
"description" : "High Business Impact",
"formula" : "BI > 0",
"points" : 20
}]
{
"segmentRef" : "Custom_5RSegmentation_seg_6",
"name" : "Retain",
"description" : "Business application serves valuable function with clear roadmap allowing for future decisions",
"color" : "#FFFF00",
"matchingRules" : [ {
"description" : "High Business Impact",
"formula" : "BI > 0",
"points" : 20
} ]
The ties are thus going to the higher numbered reference. Also it is found to be not dependent on the file order.
This is an expected behaviour.
Ticket
47336
Related Articles
Comments