Digest 9.4

Owned by Technische Redaktion
Last updated: Dec 14, 2023 by Product Management

During the development of yuuvis® RAD version 9.4, the following new features and changes were made that are described in this documentation.

New Features

yuuvis® RAD core-service

  • Files can be stored encrypted in external archives (only for use within the EU due to export regulations). (internal: TUK-1775)

yuuvis® RAD Services

  • A new signing service is introduced as a Beta Version for gathering experience and for non-productive usage. Programmers can start to use it for requesting the signing of documents files that were prepared to be signed on the DocuSign platform. (internal: TUK-1853)
    • The preparation of the object type and a specific document instance is described in this article: The signing of a document
      Object types that contain documents with a PDF-formatted file to be signed must be derived from a quasi-standard abstract type that contains the necessary properties for the signing process. (internal: TUK-1851)
    • The Service Manager setup installs the Signing Service as well. (internal: TUK-2430)
    • The signing service polls as configured for the status of the files that are sent do DocuSign and transfers a signed document back as well as status changes (internal: TUK-1953)
    • Extended support for the OEM product Kyocera Enterprise Information Management (KEIM):
      • It is possible to select the full-text language package for either America & Europe or Asia during the installation of Elasticsearch. (internal: TUK-2531)
      • The following languages are supported by the Asia package: English, Traditional Chinese, Hangul, Thai, Simplified Chinese, Japanese, Indonesian, and Malaysian.
        Restrictions:
        • This package is only allowed for KEIM.
        • It is only allowed to activate English and one other language in an environment.

yuuvis® RAD client

  • Users are supported by digitally grouped data fields in processes (thousands separation, e.g. 4,711.98 for EN / 4.711,98 for DE / 4'711.98 for DE-CH). (internal: TUK-1941)
  • Users can request signing for a PDF file of a document. (internal: TUK-1963)
  • Users are informed about the status of a signing process in the Signatures object details aspect. (internal: TUK-2431)
  • If users request the deletion of a document that is currently in process, a dialog is shown prompting the users to decide whether to cancel or actually execute the deletion nevertheless. (internal: TUK-2060, ERA-9203)
  • Users can find documents without content files. (internal: TUK-2332)
  • Process task participants added by an administrator can be informed via e-mail about their newly assigned task.(internal: ERA-8003)
  • Users are supported by autocomplete suggestions in table column types that can be configured for autocomplete indexing. (internal: TUK-2502)
  • File types word, cell, and show form Hancom Office are classified as word, excel, and powerpoint file types. (internal: TUK-2572)
  • Files of the mime-types application/x-7z-compressed (file extension 7z) and application/x-rar-compressed (file extension rar) are classified as zip file type instead of octet-stream.
  • Files of the mime-type text/html (file extension html/htm)  are classified as txt file type.

yuuvis® RAD management-studio

  • Administrators can configure the file encryption for an external archive storage. (internal: TUK-1775)

yuuvis® RAD designer

  • Administrators can configure the digit grouping for BPM properties of type number as it is possible for business object properties, so that yuuvis® RAD client shows numbers with a thousands separator, e.g., 3,546,521.56 in English / 3.546.521,56 in German / 3'546'521.56 in Swiss German. (internal: ERA-9170)

Deprecated Functions and Removed Features

No features were set to deprecated or removed with version 9.4.

Breaking Changes 9.4

The REST-WS endpoint for deleting an object has been changed.

If an object should be deleted without user interaction, the parameter forcedelete has to be added and set to true.

The default is false and in this case, the object is contained in a process, the document is not deleted and an error is thrown. You have to check your processes or custom microservice whether you use the delete endpoint for objects that are contained in a process.