New Profile Option Added and Blind Query Removed for Redwood Address LOVs

On the HCM Redwood address attributes that were supported by an LOV, the blind query that was executed when a user clicked an address attribute has been removed, irrespective of the address format of Postal address or Supplemental Taxation and Reporting Address. Now, a search query will only happen once the user begins to enter some text into the address attribute. This change was done for two reasons. Firstly, the blind query used to return results that didn't help the user because the data returned was random. Secondly, the blind query had some performance issues.  

The behavior of the HCM Responsive address attribute LOVs is slightly different from the Redwood address attribute LOVs for the Postal address formats. So, we’re introducing a new profile option that will allow you to change the behavior of the Redwood address attribute LOVs.

To explain the difference, let's assume that the following geography data hierarchy exists in the Manage Geographies setup and maintenance task for just one zip code in the United States:

  • Country: United States
    • State: Primary - CA
    • State: Alternate - California
      • County: Primary - Alemeda
        • City: Primary - Pleasanton
        • City: Alternate - Alfred Pleasanton
        • City: Alternate - East Bay Tri Valley
          • Zip Code: Primary - 94588
          • Zip Code: Alternate - 94588-3939

As you can see from the above hierarchy, each geography level has a primary geography name, and in some cases a geography could have none, one, or two alternate names provided. When a user is on an address attribute, we will refer to that as the geography attribute, and any level in the hierarchy above that selected geography attribute will be referred to as the parent geography.    

In the Responsive address attribute LOVs, when the user is on a geography attribute, if primary and alternate names have been defined in the geography data, both the primary and alternate names will be displayed, but only the primary parent geography will be displayed. For example, if you are on the zip code field and entered 94588, you will see only 2 records:

  • 94588             Pleasanton     Alemeda   CA
  • 94588-3939    Pleasanton     Alemeda   CA

That's because Pleasanton, Alemeda, and CA are all the primary names in the geography hierarchy.

By default, in the Redwood address attribute LOVs, if primary and alternate names have been defined in the geography data, both the primary and alternate names will be displayed, and the primary and alternate names of the parent geography will be displayed. For example, if you’re on the zip code field and you enter 94588, you will see a total of 12 records:

  • 94588             Pleasanton                   Alemeda   CA
  • 94588-3939    Pleasanton                   Alemeda   CA
  • 94588             Alfred Pleasanton         Alemeda   CA
  • 94588-3939    Alfred Pleasanton         Alemeda   CA
  • 94588             East Bay Tri Valley       Alemeda   CA
  • 94588-3939    East Bay Tri Valley       Alemeda   CA
  • 94588             Pleasanton                   Alemeda   California
  • 94588-3939    Pleasanton                  Alemeda   California
  • 94588             Alfred Pleasanton        Alemeda   California
  • 94588-3939    Alfred Pleasanton        Alemeda   California
  • 94588             East Bay Tri Valley      Alemeda   California
  • 94588-3939    East Bay Tri Valley      Alemeda   California

That’s because both the primary and alternate names from each parent geography will be displayed in combination with the primary and alternate name of the zip code.

While some of you have requested that both the primary and alternate names be displayed and selectable from the LOV, others have raised a request to change this behavior back to the Responsive behaviour, where only the primary and alternate names of the geography attribute and the primary parent geography are displayed. 

To achieve this request, we have introduced a new profile option that will apply only to the HCM Redwood pages that use the Postal address formats and not the Supplemental Taxation and Reporting Address formats. The address format used on the page is based on the Features by Country or Territory setup and maintenance task. 

The new profile option is Redwood Address List of Values (ORA_PER_REDWOOD_ADDRESS_LOV). For more information about the valid values and the behavior of this profile option, see the Steps to Enable section.

This feature enables you to control the display of HCM Redwood address attribute LOVs with the Postal address format.

Steps to Enable

The default value of the ORA_PER_REDWOOD_ADDRESS_LOV profile option is Null. If you want to change the display of the HCM Redwood address attribute LOVs with the Postal address format, you need to update the profile option value.

For more information about the profile option values and how you update them, see How do I change the display of the HCM Redwood address attribute LOVs with the Postal address format?