This release introduces a number of key updates, including a major WebReader update, callback parameters on REST conversion services, the possibility to configure custom content types, and more.
This release has been patched - see Patch Release Notes for details.
On this page
- Updating Conversion and ADx
- New Features and Improvements
- Known Issues
You can install this release from the provided package. Follow Installation Instructions if you're installing from scratch.
For information on how to update previously installed Conversion and ADx, see the following:
The following features are provided in this release:
|https://jira.braintribe.com/browse/AD-695||Conversion Callback Support in ADx - see documentation||Critical|
|https://jira.braintribe.com/browse/AD-386||ADx Admin: Custom Types Management - see documentation||Critical|
|https://jira.braintribe.com/browse/AD-327||DCTM Repository: Support for Documentum 6||Critical|
|https://jira.braintribe.com/browse/AD-818||Backup & Restore scripts - see documentation||Major|
|https://jira.braintribe.com/browse/AD-625||MetaData Export Support - see documentation||Major|
|https://jira.braintribe.com/browse/AD-566||Drag & Drop Support for Entities||Major|
|https://jira.braintribe.com/browse/AD-726||Add missing conversion mimetypes||Major|
|https://jira.braintribe.com/browse/AD-570||UI improvements - Open Action & GotoModelPath Command, see UI Improvements||Major|
|https://jira.braintribe.com/browse/AD-764||Version Switch in Documentation Site||Major|
You can now use the Go to action to open the contents of a folder:
When you open the folder, a full structure is shown in the breadcrumb:
Items in Grid View are now grouped by content type:
Note that you can configure custom types now! For details, see Configuring Custom Types.
New WebReader is now available:
For information on how to use WebReader features, see Browsing Contents in WebReader.
You will notice that this site has a version switch in the top-right corner. Use this switch to find content relevant for a specific version (2.0 and 2.1 at the time of this release).
The following known issues were resolved.
|https://jira.braintribe.com/browse/AD-347||MAJOR||ADx Admin: Repository Deletion not properly working|
No changes made to
example-installation-settings file (only minor comment adjustments).
The following runtime properties were added in this release:
|ADX_AUTO_SYNC_REPOSITORIES||Optionally, you can add this property to your installation settings file. When set to |
A list of problems we're aware of and working on.
|https://jira.braintribe.com/browse/AD-321||CRITICAL||Add missing indices|
|https://jira.braintribe.com/browse/AD-354||CRITICAL||ADx Admin: Problem when synchronizing Type Definitions form DCTM/CMIS|
|https://jira.braintribe.com/browse/AD-350||CRITICAL||ADx Admin: Repository Activation state sometimes not correct in case of errors|
|https://jira.braintribe.com/browse/AD-348||MAJOR||ADx Admin: Repository Modification-Status not updated on Update|
|https://jira.braintribe.com/browse/AD-330||MAJOR||ADx Content: Missing ADx context information for conversion jobs|
|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|
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.
|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/AD-501||MAJOR||tf-conversion user has the admin role assigned|
|https://jira.braintribe.com/browse/EXTDOCS-71||MINOR||Fix wrong encoding on opening resource in Browser|
The following error currently appears in ADx console output. It doesn't affect ADx 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.
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
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]
These warnings do not affect the functionality of the application and can be ignored. We are working on a fix.