Learn how to configure the ValueBasedPriority strategy to control Operational Value (OV) selection based on attribute value order.

The ValueBasedPriority survivorship strategy determines the Operational Value (OV) for an attribute by applying a user-defined priority list of acceptable values. The value with the highest priority becomes the winner, and all crosswalks associated with this value are also marked as winners. This strategy ensures that a specific value—defined as preferred—is consistently selected, regardless of contributing source systems.

You must define the valuesPriorityOrder list to indicate the preferred attribute values and their priority order. If this list is missing, configuration validation fails. If none of the attribute values match those in the list, all values will have their OV flag set to false.

If you use this strategy with nested attributes, define the comparisonAttributeUri parameter to specify which sub-attribute should be used for value comparison. For more information, see Survivorship mapping parameter comparisonAttributeOvOnly.

If the attribute is a lookup, use the lookupComparisonField parameter to specify which type of lookup value to use for comparison. Valid options are lookupCode, lookupValue, and lookupRawValue. If not specified, the system applies default behavior that resolves the lookup value automatically based on the strategy context.

Examples – configuring the ValueBasedPriority strategy:

• Configuring a lookup attribute:

{
  "attribute": "configuration/entityTypes/Location/attributes/Country",
  "valuesPriorityOrder": ["US", "CAN", "UK"],
  "lookupComparisonField": "lookupCode",
  "survivorshipStrategy": "ValueBasedPriority"
}

• Configuring a non-lookup attribute:

{
  "attribute": "configuration/entityTypes/HCP/attributes/Status",
  "valuesPriorityOrder": ["Active", "Inactive", "Defunct"],
  "survivorshipStrategy": "ValueBasedPriority"
}

In the second example, the priority order for the Status attribute is defined as Active, Inactive, and Defunct. Here's how the strategy applies:

• If any value from the priority list appears in the attribute, the highest-ranked value becomes the OV and is marked true.
• If none of the values in the priority list are present, all attribute values are marked false.
• If multiple values from the list are present (from different crosswalks), the one listed first in valuesPriorityOrder is selected as the OV.