Localization of New Values

Most static string values in the compliance database support translation. These static values usually populate enumerated lists, such as a list of asset types, or the possible values of asset status.

The translation mechanism uses three database tables:

• ComplianceResourceString gives each string using a unique string ID, and provides the default content for the string if no localized versions are found.
• ComplianceCultureType lists the available culture types for which localizations are available.
• ResourceStringCultureType stores all required translations of a string identified by a string ID and the culture type.

When your Import defined for an Object requires new values in such lists (for example, creating a new asset type or a new asset status), a unique string ID is automatically created by the Business Importer and the base record is created in the ComplianceResourceString table, using the imported new value as the default.

In order that anyone using the web interface for FlexNet Manager Suite in another language is not left with a blank where the new value should be, the same value is also written into all available culture types as the 'translated' values within each culture. This is simply a placeholder, and is unlikely to be the final desired value for each of your supported culture types. If you need to display a localized value for your new static string in the web interface of FlexNet Manager Suite, ensure that the appropriate localized version(s) are also edited in the ResourceStringCultureType table. For example:

• Suppose you import a new asset status value of Under repair.
• Immediately after import, this value is displayed in all cultures. An operator using a French presentation currently sees Under repair.
• Using SQL Server Management Studio, you open ResourceStringCultureType and edit the corresponding string for fr-FR from Under repair to En réparation.
• From this edit onwards, an operator using a French presentation sees En réparation.

Note: When searching the database for existing records, the match is performed using the translation(s) found in the ResourceStringCultureType table.