yuuvis® RAD core-service

The following features reduce administration efforts:

The REST-WS endpoint ./dms/{id}/children can be requested with nullvalues=true to get such properties in the answer as well. (internal: TUK-5709)
The REST-WS endpoint ../result/query provides the wildcard search for text-based parameters. (internal: TUK-5150)
The core-service setup asks for the license key to connect the License-Management-Service and whether metrics should be sent. Currently, these values can be entered in the ‘Systems’ view of the management-studio. (internal: TUK-5785)

yuuvis® RAD services

The following features reduce administration effort:

The search-service API can be requested to return the technical catalog entry id or data. (internal: TUK-5711)
The signing-service sends admin emails with the affected objectId and a URL for opening it in the client. (internal: TUK-5577)
It is possible to activate the used context path for specific gateways so that services not supporting the context path can use a gateway without the activated context path. With this feature, the configuration of the context path in the extend.json file of the client is no longer necessary. (internal: TUK-5873)
- The parameter server.servlet.context-path must no longer be configured in the application-prod.yml. For each configured gateway, the gateway-service sets the new request header x-os-context-path with the server.servlet.context-path value read from the file gateway-<profile>.yml. (internal: TUK-5897)

This feature supports users in optimized handling of objects listed in the CSV export of their hit lists:

The search API provides the CSV export with a column with the URL to the document if the request parameter withurl=true is set. The default is false without this column. (internal: TUK-2723)

The following features increase the user productivity:

The search form field of the types user/group, dynamic-list and auto-complete provides the following operators (internal: TUK-5594):
- = (equal) for the known search to find objects containing the entered term
- ≠ (not equal) to find objects not containing the entered term
- Out of scope: Search in tables. This will come later.
The user is asked whether to export the CSV data of the hit list with the URL to the object. (internal: TUK-2723)

The following features extend the catalog features and match specific data export compliance policies:

The auto-complete field resolves the placeholders {clientlocale} and {schemalocale}which can be used for particular parameter values in the configured URL, e. g. (internal: TUK-5610):
autocomplete/mycatalog?description=mydescr_{clientlocale}&myparam={schemalocale}
It is possible to configure in the extend.json file of the client to offer only object actions that can export a document file, like downloading it or sending it via email with attachments for users with a specific role. Without this configuration, all users are provided with these features which is the default. (internal: TUK-4525)
Example configuration:
{ "requiredRolesExport": ["myrole1", "myrole2"] }