Dynamic catalogs are introduced with version 2021 Summer at the latest. Beginning with 2021 Summer Alpha2, the Web-API Gateway offers the endpoints for maintaining such catalogs, and the users are offered a pick-up list including an edit dialog if the property readonly is not set.

These catalogs are named dynamic because they can be changed by responsible users without changing the schema configuration.

In the following, the different use of such dynamic catalogs is described.

Dynamic catalogs used by a specific tenant

If only a specific tenant will use a dynamic catalog it is recommended to configure this catalog with a classification-tag for the field that should contain one of its values:

	<propertyStringDefinition>
		<id>contract</id>
		<propertyType>string</propertyType>
		<cardinality>single</cardinality>
		<required>false</required>
        <classification>dynamic:catalog[appMytenant:contracts]</classification>
	</propertyStringDefinition>

After uploading the tenant-schema 'Mytenant' the user will get an empty pick-list for that field. A user with the role YUUVIS_MANAG_SETTINGS can maintain this list:

Create a new list element
Remove a list element. A warning is given if this element is used by an object.
Disable a list element. Such elements are offered for search but not during creating or editing an object.

An administrator with the role YUUVIS_TENANT_ADMIN can maintain the dynamic catalog contracts using the Web-API Gateway GET and POST endpoints https://<domain>/api-web/admin/catalogs/contracts

The format of the catalogs JSON formated in this way:

{
  "tenant": "Mytenant",
  "entries": [
    {
      "name": "Contract 1",
      "disabled": false
    },
    {
      "name": "Contract 2",
      "disabled": false
    }
  ]
}

Managing dynamic catalogs

Dynamic catalogs used by a specific tenant