Page Comparison

...

	<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:

...

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

The catalog data is saved in the config server beside the tenant-schema configuration.

The format of the catalogs JSON formated in this wayis JSON. The following example shows a list of two elements stored for the tenant Mytenant:

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

The client uses the Web-API Gateway dms-controller endpoints: 

• The list elements from the catalog are read with the GET endpoint https://<domain>/api-web/dms/catalogs/contracts
  
• If the catalog does not exist it is created with the POST endpoint https://<domain>/api-web/dms/catalogs/contracts.
• If the catalog does exist changes of its list elements are saved with the PATCH endpoint https://<domain>/api-web/dms/catalogs/contracts.

Set a catalog to read-only

If a catalog should be stable after setting it up, the parameter readonly can be set into the classification-tag, e.g.:

<classification>dynamic:catalog[appMytenant:contracts,readonly]</classification>