Business Condition: LOV Cross-Validation

LOV Cross-Validation is a condition which specifies legal relationships between the values in two Lists of Values (LOV) attributes. Setting up the 'LOV Cross-Validation' condition requires setting a defining attribute to which the dependent attribute will be compared.

For example, an LOV attribute is named ‘List Colors’ with values ‘Blue,’ ‘Black,’ and ‘Red.’ This is the 'Defining' attribute. Another LOV attribute is named ‘List_Size’ with values 'M,' ‘L’, ‘XL,’ or ‘XXL.' This is the 'Dependent' attribute. Based on the availability of different sizes of shirt for a particular color, you can make use of the ‘LOV Cross-Validation’ business condition to specify the relationships between the two LOV attributes like ‘Blue’ > L, XL, ‘Black’ > XXL, ‘M,’ and so on.

Important: It is not recommended to use LOVs with duplicate values in cross-validation in both dependent and defining attributes.

Prerequisites

Before using this business condition:

  1. Verify the 'Use IDs on values' option for both the 'Defining attribute' and the 'Dependent attribute' LOVs is set to Yes.

  2. Verify the Defining and the Dependent attribute LOVs are configured so that users cannot add new values. This enables the user to specify that the value of one LOV attribute limits which values are valid for another LOV attribute.
  3. Create a business rule as defined in the Creating a Business Rule, Function, or Library topic.
  4. Edit the business rule to configure the operation as defined in Editing a Business Rule or Function topic.

Configuration

  1. On the 'Edit Operation' dialog, select LOV Cross-Validation from the dropdown.
  2. For the 'Defining attribute' field, click the ellipsis button () to display the Defining Attributes dialog. Use the 'Browse' or 'Search' tab to identify the defining list of values, then select the desired single-valued LOV attribute. Click Select to display this attribute as the defining attribute.

  1. For the 'Dependent attribute' field, click the ellipsis button () to display the Dependent Attributes dialog. Use the Browse or Search tab to identify the dependent list of values, select the desired single or multi-valued LOV attribute. Click Select to display this attribute as the Dependent attribute.

  1. Select an attribute in the 'Defining Attribute' column list on the left, and set the valid dependent attribute values in the 'Dependent attribute' column list on the right.

    Note: The number in the parentheses next to each attribute name specifies how many values of the dependent attribute are configured to be valid. This provides an overview of the configuration without clicking through every defining value.

  2. Select the Save button to save this business condition.

Note: The cross validation functionality will also work in the Web UI when the LOV Cross-Validation business condition has been configured for two editable LOV attributes inside a data container.

Important: If one or more attributes are configured in multiple business conditions, the business conditions that share attributes will not work when applied. For instance, if two LOV Cross-Validation business conditions are set and one attribute is configured in both, the cross validation functionality will not work as expected.

To set up business conditions in the Web UI, refer to the Business Rules in Web UI topic in the Business Rules documentation and the Configuring Business Conditions in Web UI topic in the Web User Interfaces documentation.

Bidirectional and Omnidirectional LOV Cross-Validation

If a business condition is configured with both the 'Defining' and 'Dependent' attributes, and those same attributes are added as 'Target Attributes' in the Web UI configuration, the business condition enables a bidirectional LOV cross-validation. This means that the list of LOV options shown in dropdown for the 'Defining' attribute is filtered based on the selected value of the 'Dependent' attribute, and vice versa.

In a business condition where both the 'Defining' and 'Dependent' attributes are configured but only the 'Dependent' attribute is added as a 'Target Attribute' in the Web UI configuration, only the 'Dependent' attribute's LOV options will be filtered and the 'Defining' attribute's LOV option dropdown will show all values. This scenario is an omnidirectional LOV cross-validation. In this case, selecting an LOV value from the 'Defining' attribute's LOV dropdown that is disallowed based on the configuration of the 'Dependent' attribute will cause a warning to display for both the 'Defining' and 'Dependent' attributes.

The LOV cross-validation functionality also works for the following components: