Customize the labels describing the different metadata properties displayed in your client for different languages.

Introduction

The Localization tile is available on the dashboard for users with the YUUVIS_TENANT_ADMIN or YUUVIS_SYSTEM_INTEGRATOR roles.

In your client, forms are used to present the properties of your business objects. yuuvis® architect allows you to customize the labels of the individual property fields and thus replace technical names in the forms, filters and hit list columns.

The structure of the metadata forms for the client cannot be customized via localization, but by means of the Form Modeling view of yuuvis® architect.

Customizing Labels

yuuvis® Momentum client reference implementation includes a default label configuration for the languages English and German. Any technical name you may have defined additionally will have no corresponding language-specific label. If you select a language other than English or German, no labels are predefined at all. In your client, the technical names will be displayed instead.

The following instructions will help you to either customize the default labels or define your own labels.

• Click the Localization tile to open the view for the label customizing. Alternatively, click the menu button on the top left and select Localization. 
• Select one or two languages on the right side of the top bar.
  
• Find a list with the columns Technical name, and for each language Label and Description. All technical names are displayed that correspond to a specific property field available in your client and that are enabled for customizing based on your roles.
• Add or edit labels and/or descriptions in your language for any technical name in the list. The description is used to group object types in the Create object and Restrict to object types dialogs. Object types with the same description are displayed in the same group.
• Save your changes or Reset to the last saved configuration and discard all changes.
• Sort the list by a column by clicking its header. Clicking the column header repeatedly will invert the sort direction.
• Find a tree of object types in the Filter technical names by: area on the left next to the list. The structure represents the schema structure and contains all types of business objects and extending types you are allowed to customize. Additionally, the # Tags filter provides all technical names identifying names and values of process tags that you are allowed to customize.
• Click on a node or leaf in the tree to limit the listed technical names by showing only the technical names associated with the selected filter.
• Click repeatedly on the same filter to remove it and display the entire list of technical names.

New technical names cannot be added in the localization view of yuuvis® architect. They appear automatically in the list after applying changes to the metadata structure directly via the schema or via the Form Modeling view of yuuvis® architect. 

Note: The technical names are automatically extracted from the active schema definition. If new definitions are added, the corresponding technical names will appear in the list of available technical names. However with the version 2020 Winter of yuuvis® architect, if schema definitions are deleted, the technical names are not removed from the localizations list. So far, it is not possible to delete the corresponding localization entries that have been saved before. This feature will be available as of version 2021 Summer.

Customizing Language Files

As of version 2021 Summer, the labels can be localized alternatively via language files. To change the language file you have two options: a) make changes online in your browser or b) download the language file, make changes offline and upload the edited file to the server. 
a) Online editing

• To change a label or description for an object type, double-click on the corresponding field and enter your change. Click Save to save your change or Reset to reset.

b) Offline editing

• Download the language file for the selected language by clicking the corresponding Export icon on the right side of the title bar.
• Modify the file locally in an editor of your choice.
• If you want to reuse the file for a different language, rename it consistent with the convention <ISO>.json, e.g., fr.json for French.
• If you want to reuse the file for a different tenant, the prefixes of tenant-specific labels have to be adjusted.
• Upload your custom language file by clicking the corresponding  Import icon on the right side of the title bar and selecting the file from the Explorer window.
• After you have selected the language file, the Import validation dialog opens in which you can check your changes before uploading them. In the left column of the Import validation dialog, the technical names of all object types that have been added to the language file are displayed. In the right column of the Import validation dialog, the technical names of all object types that have been deleted from the language file are displayed. If only the labels and descriptions of object types have been changed, but no technical names, the left column of the Import validation dialog will remain empty.
• Click OK to upload your local language file to the server.
• To complete the offline editing, click Save. The values on the server will then be overwritten by the values from your local language file.

yuuvis® Momentum library-based clients support a number of languages. They are listed in Localization for Clients.
Note: Sublocales, like German for Switzerland (de-CH), are not supported in yuuvis® architect.

Summary

The localization modeling in yuuvis® architect allows for users with YUUVIS_TENANT_ADMIN or YUUVIS_SYSTEM_INTEGRATOR roles to customize the labels of the individual property fields displayed in their client. These roles authorize users to customize labels associated with object types of either tenant-specific or global schema definitions, respectively. Thus, technical names in the forms, filters and hit list columns can be replaced.

The structure of the metadata forms for the client cannot be customized via localization, but by means of the Form Modeling view of yuuvis® architect.