...

A property can be classified in the schema definition to be displayed as a dynamic catalog in your client by setting the value dynamic:catalog[<catalog name>] for the attribute classification. The catalog name  name will be the displayed expression in your client per default. It can be localized in order to replace the displayed expression. We recommend naming conventions described below that makes it easy to distinguish between tenant-specific and global catalogs.

The catalog values are saved in a JSON file in the config server beside the corresponding schema configuration.

Catalogs can be set as readonly in the catalog maintenance view of the architect via Web-API gateway. Thus, the catalog values can not cannot be modified via the dms-controller endpoints of the Web-API gateway. Since the client uses the dms-controller endpoints, the corresponding pick-list elements in the client will also be not editable. Changes can be applied only via the system-controller endpoints in case of global catalogs and via the admin-controller endpoints in case of tenant-specific catalogs. The catalog values are saved in a JSON file in the config server beside the corresponding schema configurationThis catalog management is also possible via yuuvis® architect.
>> yuuvis® architect

In order to avoid the occurance of empty pick lists in your client, we recommend to create the JSON configuration of the catalog first and introduce the definition into the schema afterwards.

Tenant-Specific Dynamic Catalogs

...