...
If a catalog should be stable after setting it up, the parameter readonly can be set into the classification attribute, e.g.:
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<classification>dynamic:catalog[tenMytenant:contracts,readonly]</classification> |
...
The edit dialog can be opened by clicking the pencil symbol at the field. The screenshot below shows the edit dialog for the example pick-list contracts where already the four values Employment contract, Rental agreement, User contract and Purchase contract were already added.
...
- The list elements from the catalog are read with the GET endpoint
https://<domain>/api-web/dms/catalogs/tenMytenant:contracts. - If the catalog does not exist it is created with the POST endpoint
https://<domain>/api-web/dms/catalogs/tenMytenant:contracts. - If the catalog does exist changes of its list elements are saved with the PATCH endpoint
https://<domain>/api-web/dms/catalogs/tenMytenant:contracts.
Editing via Web-API Gateway
Users with the role YUUVIS_TENANT_ADMIN are offered the same maintenance actions via the Web-API Gateway GET, POST and PATCH endpoints: https://<domain>/api-web/admin/catalogs/tenMytenant:contracts of the admin-controller.
The client uses the Web-API Gateway dms-controller endpoints:
...
catalog
...
The catalog data is saved in the config server beside the tenant - schema configuration.
The format of the catalogs is JSON. The following example shows a list of four elements stored for the tenant Mytenant:
...