5.0.0
08.11.2023
Major Release
Change to Jarkata Servlet >= 6.0 - Breaking Change: is only running on modern Java-Webserver that supports JakartaEE (e.g. Tomcat 10 …) and Java 17+
Security-Fixes
4.2.13
10.10.2023
Bugfix:
fixed a problem with data exctraction from filenames when the name contains more than one “.“ (dot)
fixed an issue that leads to an out of memory issue in tif coordination
4.2.12
30.08.2023
Bugfix:
fixed a problem with accumulating logback threads when the REST interface is used
4.2.11
09.08.2023
Bugfix:
fixed a problem when using the security provider enabled for the web console
4.2.10
25.07.2023
Bugfix:
fix an instance crash during sorting of input files
fix a wrong return code in REST interface that returns 200 instead of 400
fix an issue that executed the epilog again after it already failed
4.2.9
18.07.2023
Bugfix:
fix an issue where the license is not read in time and causes an issue with autostarting instances.
4.2.8
27.06.2023
Enhancement:
Skip pause after single instance prolog run
Bugfix:
subdirs 2 fixed
4.2.7
09.05.2023
Bugfix:
Remove logs redirection to stdout
fix multithreading handling issues with prolog
fix fallback configuration, to prevent import of remaining files with ignored file endings
change error message in case of 419/404: add source filename
4.2.6
27.04.2023
Improvement:
prefix bases repository mapper: log file name added to log message for unknown prefixes
Bugfix:
security provider packaged again
digest calculation triggered although archiving is disabled (now does not calculate digest)
on creation of DR instance checksum type shown on UI was not consistent to the digest type stored and applied
disabled docId and compId validation before triggering doPostProcessing/doEpilog after index file split
Breaking changes!
For licensing reasons, the Oracle driver was removed.
If sapa link is used with an oracle db as destination please configure as described in Configuration (Store) - OracleUCM (7)
If oracle db is used for protocol service please read: Oracle
4.2.5
04.04.2023
Improvement:
Add JWT OPENID Support for Multipart Rest interface (see DR4 - Authentication - Tab for Instance configuration)
Bugfix:
Fix an issue with converted TIFs to PDFs where the PDFs are not moved to success folder
4.2.4
28.02.2023
Improvement:
Add support for UTF16 encoded idx files
Add a option to disable characters encoding detection for index files
Bugfix:
Fix an issue with stopping instances when the thread limit is reached
Fix an issue with wrong error directory, when no repository was found/configured
4.2.3
16.01.2023
Fix problem leaking threads in multipart interface
4.2.2
28.11.2022
Fix problem with email logs
Fixed a problem with unused/skipped index file field indexes
4.2.1.1
04.11.2022
Improved index file charset handling
Bugfix for Prologes which are using SingleInstance Prolog
4.2.1
27.10.2022
Improved index file charset handling
Integrated automated charset detection for Index files - if the guess is confident enough it will take precedence over the configuration setting
4.2.0
20.10.2022
Breaking changes! Take care when you are upgrading an existing installation! If you are not using a custom database, changes must be made to the existing H2 database, or existing data will be lost. Please see Update H2 Database from 1.3.175 to 2.X for documentation of the required changes.
Removed thread limit for MaximumThreadCount (was limited to number of CPU Cores)
Improved logging
Added MIME-Type for Excel macros (XLSM)
SMTPPort is adjustable for TLS
Updated embedded H2-Database to 2.1.242
4.1.5
10.10.2022
Fixed protocol entry with 419 error when CoreOfTia protocols are used
4.1.4
29.09.2022
Prevent issue while index file split
Prolog doPostProcessing(): Added check of DocID emptiness
Corrected wrong formatted log output
Schema parsing: accept schemas with holes in indexes
4.1.3
19.07.2022
Fixed:
Move Files after import was not working when there was a link in the path.
Fixed an issue when MoveOnError and MoveOnOK was checked
Optimize wait time when maxFileFetch size is set
IndexSkipLineStartsWith is working korrekt and ignores configured lines
Fixed an issue with files bigger than 2.1 Global
Make average time consumed message more clear
4.1.2
30.05.2022
Fixed
In some configuration scenarios the DR didn't delete emptied directories from the input directory
Multipart POST requests required to have only one configured instance, to work correctly
A bug prevented loading of MIME types from SAP systems (since 4.1.0)
Some left over logs from development were written to stdout
Improved
Allow empty DescrFileFilter, when working without index files (= all parameters are taken from the DataInterface definition)
Additionally allow comma as separator in file filter fields, for backwards compatibility with DR3
If configured, Success directory is cleaned asynchronously and doesn't delay instance startup nor document processing anymore
4.1.1
12.05.2022
Fixed
DataInterface definitions with | as separater lead to error message ‘Schema type could not be determined’
4.1.0
11.05.2022
New
Prolog support, compatible with DR3 prologues
Support for renamed config items, so they still work even when their old name is used
Streamserve support, implemented as Prolog. New config item PrologUndeletedTriggerFileIsError
Config item 'Lock' to enable or disable DMS locking
Added epilog method to prolog API
Changed
Renamed SIDMapping config item to ArchiveLinkConnectionMapping
Fixed
In some situations moving files in the document directory when an instance was running lead to error messages
Archive Link connection mapped in datainterface wasn't used
Improved error handling when no repository is configured in SAP
Instances sometimes did not start automatically after servlet container restart
Global license tab was missing
Removed spaces in config item name 'Common.Maximum Thread Count'
Document hash was not stored in protocol
Instances stopped when a SAP connection configured in the datainterface could not be found
4.0.9.2
23.03.2022
Fix: instances don't start automatically
4.0.9.1
18.03.2022
Fixed NPE in EMailNotificationSender
Instance log level is applied at startup, after instance INFO is logged
Instance stop is always logged as INFO. Even if level is WARN, ERROR, or OFF
NEW: Config option LogPeriodicStatusInfo
Periodic INFO messages are logged at DEBUG and TRACE levels, or if LogPeriodicStatusInfo is set to true
4.0.9
21.02.2022
performance improvements by profund refacturing
no prologes