Identifying missing display keys

Guidewire provides a display key difference tool that does the following:

• Compares each language configured on the server against the master display key list.
• Generates a file that contains a list of any missing keys.

To generate a display key difference report, run the following command from the PolicyCenter installation directory:

gwb diffDisplayKeys

If necessary, the diffDisplayKeys tool creates a build/missing-display-keys/config/locale directory under the PolicyCenter installation directory, where it stores the generated diff files.

If the tool detects that a language has missing display keys:

• The tool creates a display_languageCode.properties file, using the language code for that language to name the file.
• The tool populates the file with the list of missing keys.

Each display_languageCode.properties file contains a list of display keys that are in the master list but not in the localization files. The format of the file is exactly the same as the display key configuration files. For example, the following code illustrates the contents of the file for en_US:

#
# Missing display keys for locale
# en_US
#
Java.Validation.Messages.SIMPLE.SimpleGroupHeaderLabel = Es befinden sich {0} Meldungen auf Seite {1}
Java.Validation.Messages.SIMPLE.SimpleGroupHeaderLabelSingleMessage = Es befindet sich eine Meldung auf Seite {0}
Web.ClaimSummaryDV.Title = {Term.LossDetails.Proper}