Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

The service provides the usage of catalogs defined as document object types in a tenant schema.

As of version 2021 Winter, the CATALOG service is provided as a beta version.

Characteristics

Service Namecatalog
Public APICATALOG Service Endpoints

Function

The CATALOG service manages catalog objects and provides CRUD (create, read, update, delete) operations on it. Its endpoints are provided in an own API. 
>> CATALOG Service Endpoints

As of version 2021 Winter, only global catalogs can be managed.

An example tutorial describing a use case of the CATALOG service is provided here:
>> Validation of Properties using Catalogs

Requirements

The CATALOG service requires the yuuvis® Momentum core services and the corresponding infrastructure.
>> yuuvis® Momentum Requirements

Configuration

The access permissions for the usage of the CATALOG service are configured in the authentication-prod.yml file. We recommend to enable the endpoints for the management of global catalogs only for administrative users who are already responsible for other global resources. The code block below shows an example entry from the authorization.accesses list.

Example Configuration
- endpoints: /catalog/**
  access: hasAuthority('YUUVIS_SYSTEM_INTEGRATOR')
  • No labels