D1 2.8 (01/04/2022) Release notes

Overview

This release introduces the following key features and bug fixes:

• Manual steps
• New features
• Bug fixes

Manual steps after upgrading from ADx x.x to D1 2.8

1. Synchronize all repositories: This will prevent errors with "Connection check" and unlock new features (eSignature and AntiVirus)
2. Migrate DSCA to gain better performance by running the following scripts:

• Download and unzip file with scripts migrateStorage.zip
• Open file migrateStorage.sh and populate fields in section "USER PARAMETER VALUES"
• Run script migrateStorage.sh in terminal
• To get status of migration open file migrateStorageStatus.sh and populate fields in section "USER PARAMETER VALUES"
• Run script migrateStorageStatus.sh in terminal

Java version

The on-prem installation packages for this release have been tested with JDK JDK 11.0.14 (package zulu11.54.23-ca-jdk11.0.14-linux_x64)

Changes in actual version

Nothing has been removed since previous release.

Changes in upcoming versions

In the upcoming version D1 2.9 the following change will appear:

• the minimal Java Runtime to start up will be Java 17.
• the legacy API including legacy migration capabilities will be completely removed.

Runtime properties and configuration changes

No runtime properties have been added, changed or removed in this release.

List of new features and improvements

Issue	Priority	Summary Description
AD-321	Critical	Ensure proper DB-Indices for StandardRepository and CacheAccess
AD-1007	Critical	API error codes
AD-2429	Critical	Harmonise Explorer column handling
AD-2444	Critical	Support for Virus Scanning when documents are imported
AD-2473	Critical	Add access to document via API
AD-2498	Critical	Add rotate feature to WebReader
AD-2564	Critical	Support disabling of loading external resources when converting emails
AD-2614	Critical	Add support for custom types for transfer-in/transfer-out
AD-2633	Critical	Provide custom types via API
AD-2663	Critical	ADx goes D1
AD-2669	Critical	Add support for versions in transfer-in/out
AD-2700	Critical	Add hide/show for annotations
AD-2720	Critical	Add way to display custom properties of annotations
AD-2733	Critical	Add force comment on resolve
AD-2738	Critical	Webviewer Handmode (pan)
AD-2745	Critical	Select property panel tab on loading should be configurable
AD-2782	Critical	Add service for DCSA migration
AD-2793	Critical	Create entry exists API
AD-2792	Critical	Improve login time
AD-2031	Major	Add context for Notifications
AD-2534	Major	Export selected rows
AD-2586	Major	Make dropdown searchable
AD-2591	Major	Add formatting for comments
AD-2640	Major	Add split-pdf to Content workbench
AD-2714	Major	Add support for copying id using shortcut
AD-2253	Major	Add esignature support
AD-2667	Major	Create 'exists' service
AD-2884	Major	Allow download multiple entries
AD-2658	Major	Add scrolling to select list
AD-2743	Major	Provide documentation to avoid WebReader reloading
AD-1739	Minor	Allow downloading of a sub-document within a Compound Document
AD-1567	Minor	Improve about page for Explorer
AD-2746	Minor	Add troubleshooting documentation for suddenly shut down

Bug Fixes

Issue	Priority	Summary Description
AD-2672	Blocker	Error using CMIS with custom types
AD-2677	Blocker	CMIS repo cannot be viewed
AD-2693	Blocker	Cannot query previous versions on CMIS
AD-2719	Blocker	Cannot delete annotation
AD-2863	Blocker	Follow security issue CVE-2021-44228
AD-2993	Blocker	Get rid of query
AD-2556	Critical	CMIS repository cannot connect to ADx due to certification error
AD-2592	Critical	Cannot convert documents
AD-2596	Critical	Error on sync of custom repository
AD-2696	Critical	Permissions wrong in case of Split view
AD-2701	Critical	No scrollbar in file list
AD-2721	Critical	Fix comment handling
AD-2771	Critical	Annotation gets wrong ID on migration
AD-2780	Critical	Add support for deleting entries in target systems on migration
AD-2781	Critical	Cannot migrate content with different users
AD-2803	Critical	Cannot display document
AD-2888	Critical	Change to log4j 2.17.0
AD-2362	Major	The number of tabs in explorer should be configurable
AD-2523	Major	Connection check fails if S3 user cannot list all buckets
AD-2675	Major	"Error while synchronizing repository ""Mic Test"""
AD-2708	Major	WebReader: Button is sometimes there sometimes not
AD-2940	Major	WebReader is displaying logically deleted documents
AD-2737	Minor	Fix position of visibility
AD-2652	Minor	Fix ToPdf for different formats
AD-2967	Minor	D1 does not recover on DB error

Updating Conversion Service and D1

For information on how to update previously installed Conversion and ADx, see the following:

• Updating Conversion
• Updating ADx

Known issues

Below you can find a list of problems we're still working on.

Known issues D1

Ticket	SEVERITY	Description
https://jira.braintribe.com/browse/AD-321	CRITICAL	Add missing indices
https://jira.braintribe.com/browse/AD-348	MAJOR	ADx Admin: Repository Modification-Status not updated on Update
https://jira.braintribe.com/browse/AD-1898	MAJOR	Min and Max length metadata not respected on initial upload
https://jira.braintribe.com/browse/AD-342	MINOR	Hibernate warnings in the log files
https://jira.braintribe.com/browse/AD-341	MINOR	Java warnings during for Java 9 and later
https://jira.braintribe.com/browse/AD-311	MINOR	Oracle - DbLockManager prints Oracle constraint message

Reimporting an existing repository requires UI reload

In some cases, when reimporting an existing repository, repository properties are not rendered correctly. To make sure properties are rendered correctly, refresh your browser after each import.

Cannot migrate legacy contents simultaneously

Due to cache database being shared between repositories, it's not possible for now to run multiple migration jobs from a single legacy repository at the same time. You need to wait for the previous migration to finish before running a new one.

Min and max length metadata not respected on initial upload

String length checks are only applied when values are updated but not on the initial upload.

Known issues Conversion

Ticket	SEVERITY	Description
https://jira.braintribe.com/browse/AD-338	CRITICAL	Introduce roles for conversion
https://jira.braintribe.com/browse/AD-337	MAJOR	Make TF Conversion workbench consistent to ADx
https://jira.braintribe.com/browse/EXTDOCS-71	MINOR	Fix wrong encoding on opening resource in Browser

Minor warnings

StatusLogger error

The following error currently appears in D1 console output. It doesn't affect D1 functionality or performance.

ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console.
  Set system property 'org.apache.logging.log4j.simplelog.StatusLogger.level' to TRACE to show Log4j2 internal initialization logging.

Tomcat shutdown warning

The following warning is sometimes thrown by Tomcat when stopping the service:

./tribefire-console-stop.sh
...
Tomcat did not stop in time.
PID file was not removed.
To aid diagnostics a thread dump has been written to standard out.
Tribefire Host stopped.

This happens when shutdown takes longer than Tomcat expects. Shutdown may take several minutes, which will result in this message being printed out. This warning could appear on both Conversion and D1.

Java warnings

When using Java 9 or later, the following warning may appear in application logs and also during installation procedure:

WARNING: An illegal reflective access operation has occurred
WARNING : Illegal reflective access by com.braintribe.model.processing.itw.asm.AsmClassLoaderWrapper$1 (file:/path/to/instant-type-weaving-1.0.28.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)
WARNING: Please consider reporting this to the maintainers of com.braintribe.model.processing.itw.asm.AsmClassLoaderWrapper$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

Ticket: https://jira.braintribe.com/browse/AD-341

Hibernate warnings

The log files may contain Hibernate-related warnings. They can be identified based on the fully qualified class which starts with org.hibernate, as in:

WARNING org.hibernate.tuple.entity.EntityMetamodel 'HHH000084: Entity [com.braintribe.model.user.User] is abstract-class/interface explicitly mapped as non-abstract; be sure to supply entity-names' [TribefireServices-2.0:tribefire-services#initialize,ApplicationLoader:/tribefire-services#initialize]

Ticket: https://jira.braintribe.com/browse/AD-342

These warnings do not affect the functionality of the application and can be ignored. We are working on a fix.