edoc archive service Release Notes
Breadcrumbs

edoc archive service Build 25.1.5

With this release, you will receive numerous new functions, and the design of the confirmation dialogs has been revised.

In addition, some bugs have been fixed.

New functions and enhancements

ID 13088: Prevent copying of the password

For security reasons, copying of passwords is now prevented.


ID 104754: Do not consider inactive process types when transferring the configuration

From now on, you can first create the process types and then finalize and enable the configuration at a later time. Only enabled process types are now applied when transferring the configuration.


ID 14753: Retrieve all processes from the ERP system

Processes are now also retrieved from edoc archive service that are flagged as incorrect in the ERP system or have not yet been processed.


ID 14751: Ignore previous incorrect archiving operation of a process

You can now manually ignore a faulty or non-existent archiving process in the edoc archive service cockpit in order to archive the next version.


ID 13525: Adapt the design of the confirmation dialogs to the edoc corporate design

Confirmation dialogs have been adapted to the edoc corporate design. The labeling of the buttons has also been improved so that administrators are guided more intuitively through a process.

Bug fixes and improvements

Normal ID 14623: Successful transfer despite non-working connection

If you have configured at least two identical ERP connections with the Microsoft Entra ID authentication method, only the data of the ERP connections for which there are valid login data will be transferred.


Normal ID 14864: Empty captions for pages, tables and reports in Dynamics NAV lead to errors when retrieving data

If there are pages, tables and reports with empty captions in your ERP system (e.g. Microsoft Dynamics NAV), the data will still be retrieved correctly by edoc archive service.


Normal ID 14865: ECM destination field values are not changed by webhook for changing ECM destination properties before archiving operation

If you have configured an endpoint for a webhook for incoming documents to change the ECM destination properties before the archiving operation, the ECM target field values are now changed correctly.