Valid from

...

• The extraction-service also supports e-invoices based on the new ZUGFeRD version 2.3 and Factur-X 1.0.07. (internal: TUK-5900)
  Info on FERD

• The extraction-service supports e-invoice files of format XRechnung 3.0.1 in the syntax UBL 2.1 (internal: TUK-4100)
  This is the third step in supporting e-invoices. The extraction from ZUGFeRD formatted e-invoices is supported since yuuvis® RAD version 9.-16 LTS, from Factur-X 1.0.06 and XRechnung 3.0.2 with Syntac CII (UN/CEFACT) since yuuvis® RAD version 10.4.
  An additional configurable mapping file is introduced that maps the new UBL-XRechnung tags to the existing extraction tags beginning with FERD:. This allows the configuration of a single mapping in the designer that handles all three different e-invoice formats.

• The rmalink-service can connect to an SAP instance by automatic certificate activation or without using any certificate. Manual activation of certificates is the default behavior. (internal: SAP-2934)
  Active SAP certificates can be deactivated through the Swagger endpoint. (internal SAP-2941)
  We strongly recommend the use of certificates for security reasons.

yuuvis® RAD client

The following features increase the user productivity:

...

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

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

  Code Block
  { "requiredRolesExport": ["myrole1", "myrole2"] }

yuuvis® RAD management-studio

The following features increase the user productivity:

• The user attribute 'Salutation'/'Anrede' could be imported via ad-sync and written via API. This attribute can be maintained in the create and edit form in the organization state. (internal: TUK-5597)