...
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>
Global dynamic catalogs
In this case, your tenants should use object types that are configured in a system or app-schema and should use only standard values an administrator with the role YUUVIS_SYSTEM_INTEGRATOR can set up global catalogs with initial standard elements and set the catalogs readonly. In this case the Web-API Gateway system-controller endpoints GET and POST are used.
- For the catalog contracts in the system-schema: https://<domain>/api-web/system/catalogs/contracts
- For the catalog contracts in the app-schema businesspartner: https://<domain>/api-web/system/catalogs/contracts?appschemaname=businesspartner
Global catalogs without an appschemaname are saved in the config-service beside the system-schema configuration. Otherwise the catalogs are saved beside the app-schema configurations.
Editable global catalogs
If the catalog parameter readonly is not set users with the role YUUVIS_MANAGE_SETTINGS can change the list elements. With the first update of such a catalog, a new catalog with the same technical name is saved for that tenant.
Note: From now on changes made in the global catalog are not affecting the copy. Only new tenants will get the new list elements of the global catalog.