Schema

yuuvis® RAD repository-manager 10.x »

For yuuvis® RAD repository-manager, you need corresponding object types in the schema for data management. This schema data is available for download.

  • RMALINKTypes.eoproj for the ArchiveLink connection

  • RMILMTypes.eoproj for the ILM connection

If you only use the ArchiveLink connection or only the ILM connection, then only import the data of the corresponding schema via yuuvis® RAD designer into the yuuvis® RAD system.

If you use both connections, open both schema files and copy the sapilmobjekt document type of the RMILMTypes.eoproj schema into the RMALINKTypes.eoproj schema and provide the data of this schema with both document types.

The schema also contains the roles that can be used for user management. Object type rights and functional rights can also be managed via other roles.

The 'sapaldocument' schema folder type

Technical name

Description

repository

Name of the content repository

alversion

ArchiveLink log version number (e.g., 0046)

protection

Document protection, a user-defined combination of the 'r' (read), 'c' (create), 'u' (update), and 'd' (delete) operations, is defined in the ArchiveLink ACL (AccessControlList). If SAP does not provide any information when creating a document, the default value defined in the KGS configuration interface applies (typically 'rcud': the document is protected during all operations in this manner).

id

Document ID that unambiguously identifies the SAP document.

creationdate

Date and time of creation

modificationdate

Date and time of the last modification

barcode

Optional: Temporary unique ID that can be used to assign a document located in yuuvis® RAD to a business transaction in the SAP system.

isBarcodeReported

This document flag indicates whether the barcode and thus the document have already been reported to SAP.

isBarcodeProcessingError This document property indicates whether barcode processing errors have occurred.

legalholdlock

Specifies that the document has to be retained due to legal reasons (legal hold), thus preventing the document or its components from being deleted.

This property was introduced with version 7.0. It is enabled for specific scenarios only.

expirationdate

Retention period for the document and its components.

This property was introduced with version 7.0. It is enabled for specific scenarios only.

etabfromsap SAP source
isDeleted Deletion marking
Schema for the 'sapalcomponent' document type
Technical name

Description

alversion

ArchiveLink log version number (e.g., 0046)

applicationversion

Version number of the application (such as 1.0)

charset

Character set (optional)

compressionstring

The Content Server performs compression using gzip for components with a file size larger than the adjustable CompressionSize threshold. This offers an advantage when it comes to storage, especially for print lists, which can be larger than 2 GB without compression. If they are compressed first, it typically reduces them to about 10 percent of the original size.

With this administrative information, the content server is able to determine the uncompressed size of the component and which compression parameters have been used.

contenttype

MIME type (image/tiff or application/pdf, for example)

id

Component ID ('data' for multi-page TIFF files or data, data1, data2, etc. for single-page TIFF files)

creationdate

Date and time of creation

filename

Filename of the 'source file.' As this name is always filed through Apache Tomcat's working directory, the name is always a temporary file name.

isDeleted Deletion marking
etabfromsap SAP source

modificationdate

Date and time of the last modification

Schema for the 'sapilmobject' document type
Field name Description
contentLength

Content size

0 for ILM collections

properties Tables with the 'name' and 'value' columns
type Collection or resource
url URL of the ILM object