Manage WebApp Catalogs

Catalogs provide a means to:

• Populate and administer translations or alias values

• Create dynamic help text that displays in the Information pane

Refer to Add Dynamic Help to a Page and Add Column Help Text for more information.

Catalogs, which can be applied at the page, the WebApp or the system level, contain groups of phrases and phrase translations. They can be tailored to contain a complete WebApp or system phrase set, a subset of phrases, such as SAP field names, or a larger set of phrases.

It is recommended to translate phrases at the highest level appropriate. The higher the level the phrase is translated, the more useful the translation will be. A phrase translated at the WebApp level can be reused by many WebApps and many pages. A phrase translated at the page level is used only for that page.

There are cases where a phrase has a unique meaning on a page, different from its usual meaning, and should be translated at the page level. However, page-level translation should be the exception to the rule.

Catalogs are included for delivered WebApps and, in most cases, cannot be edited. Custom catalogs can be added, and assigned to both delivered and custom WebApps, and to the system.

Note

You can import a catalog from a Syniti Content library. The Syniti Custom Catalog contains the SAP Catalog that is provided in the Stewardship Tier. This SAP Catalog can be used as content, and imported into Construct. Refer to the Knowledge Base article Upload a Custom Catalog to Syniti Construct for more information.

Managing catalogs includes the following topics:

• Add Phrases to Catalogs

• Display Translations for Column Data

• Troubleshoot Translations

Page Catalogs

Translations, help text and alias values in a page catalog are only applicable for the one page to which the catalog is linked. This is the first level the Syniti Construct searches for a phrase translation.

When a page- or column-specific translation is added, the Syniti Construct creates a new catalog for the specific page.

WebApp Catalogs

For each phrase it encounters, the Syniti Construct searches for a translation in all catalogs assigned to a WebApp in a prioritized order.

The Syniti Construct searches for translations starting with the highest level catalog (the one assigned at the WebApp level with the lowest priority). If a match is not found, the next level catalog is searched (either the catalog at the WebApp level with the next lowest priority, or the catalog at the page level). If no translations are found, the Syniti Construct searches the system catalog.

System Catalog

The Syniti Construct UI can easily be customized to support language-specific requirements by creating a custom catalog and assigning it at the system level. The custom system catalog serves as an additional translation layer between the WebApp catalog and the .System catalog.

The .System catalog, which is the default system catalog delivered with the Syniti Construct, is the last catalog searched for a phrase translation. If a custom system catalog is created by a user and assigned to the system via the System Catalog ID, even though .System is no longer selected, it is still searched for a phrase translation after the custom system catalog is searched for a translation.