DMS service
You will find information about the latest service releases of the DMS service here.
Installation
Services are installed via the os_service-manager_setup.exe file in the \Backend\Service-Manager directory.
Service updates take place via enaio_services_versionfix.exe in the \Backend\Service-Manager-Update directory. Copy the directory to the computers where the microservice installations are located prior to carrying out the updates.


The results will have a different structure when the includeAllowedChildObjectTypeIds parameter for the object type relations is used to query a folder or register. The object type IDs will be returned along with information on how many objects of a specific type can be created.
If you are already using the DMS service, please check the processing.

The HARDDELETE and DELETECASCADING parameters used to delete objects will be discontinued in an upcoming version. Use the corresponding parameters in the current structure.

All but a few server job options are available for adding, updating, deleting, moving, and copying objects. This includes, for example, ARCHIVEIMMEDIATELY to archive objects immediately.
Please follow the instructions on using use server job options.

Renditions for objects can be retrieved (PDFs, OCR texts, quicklooks).

The following endpoints can be used to set the 'Approved/not approved for archiving' property for documents:

Reference documents can be created.

CMIS for Queries
From now on multiple object types can be queried in one query using the CMIS SQL query language of the DMS microservice. This makes it possible to query parent fields of the parent register or folder as well as to set conditions on these parent objects. Furthermore, multiple child objects can also be requested with their desired fields based on the defined export depth.
Please note that this function will only be fully available with the release of version 5.3.

The DMS Service 5.3 requires the installation of server patch 10.0.13.
UNION Syntax for Search Requests
The endpoint for search requests – POST/dms/objects/search – accepts the UNION syntax, making it possible to efficiently request field information for multiple object types simultaneously within a single request.
Internal Names for Insert and Update
In addition to the object type ID, the internal name can also be specified in the JSON field 'system:objectTypeId' for insert and update functions.
Recycle Bin
New endpoints allow access to the recycle bin with the options to Restore and Delete objects permanently.
Multipage TIFF
Multipage TIFFs are no longer transferred as *.zip files but as *.tiff files via the renditions as of version 5.3.

Creating Variants
[POST] /variants: When creating variants, the objectTypeId, variantType, and transferPlannedRetention parameters can be specified directly in the payload.
Searching for Variants
[GET] /variants: The endpoint for retrieving the index data of all variants of an object provides the fields and systemFields parameters, which can be used to request index data fields as well as system fields for each variant.
Full-text Search: Quality
[POST] /search: The SCORE() function is available to return the quality of the full-text result in the JSON.
Full-text Search: System Fields
[POST] /search: CMIS SQL search provides the following special fields as part of system-wide full-text queries: system:objectId and system:objectTypeId.
Conditions on Table Controls
[POST] /search: CMIS SQL search supports conditions when searching for table controls.
Field Settings for Hit Lists
[POST] /native/names: Provides an endpoint to retrieve the names according to the field settings for hit lists, window titles, and sending.
Field Settings for an Object Type
[GET] /name: Also provides an endpoint to retrieve the names according to the field settings for hit lists, window titles, and sending for an object type.

The service release contains a new endpoint, in addition to bug fixes.
Deleting a Content File
[DELETE] /file: The new endpoint allows the contents of a document to be deleted.