PolicyCenter and the master list of display keys

On startup, PolicyCenter uses the display property files to generate a master list of display keys for use in the user interface. For each property file, PolicyCenter loads the display keys and adds each display key to the master list under the following circumstances:

• The master list does not already contain the display key.
• The master list already contains the display key, but, the display key in the master list has a different number of arguments from the display key being added. In this case, PolicyCenter logs a warning message noting that it found a display key value with different argument lists in different locales. For example:
  • Configuration Display key found with different argument lists across locales: Validator.Phone

As PolicyCenter creates the master display key list, it scans for display.properties and display_languageCode.properties files in the following order:

1. The application primary language code properties file, as set by configuration parameter DefaultApplicationLanguage
2. All other language code properties files configured for use by the server
3. The fallback language code properties file, which in the base configuration is display.properties
4. All remaining language code properties files

Because the error message returns the display key name, you can use that name to generate a display key value in the correct display key property file.