...
A core feature of CDCM is the integration of different authoring tools and other applications. These other applications require a different authentication methods and/or use different identity providers than CDCM itself. In order to handle these different outgoing connections CDCM uses a single file where the connections and authentications are configured. The documentation how to configure this file called connection-routing.yml
can be found here.
Minor features
Initial configuration for new Unit instances
When a new unit is created a child configuration with the title “Initial Stream” is autiomatically created.
Blank configuration items
...
: In addition to the configuration items that could be created before “empty configuration items” can now be created where:
only the title is provided → listed as external work product without a storage location
only the title and storage location is provided → listed with the given storage location
Display state Name instead of state key in change log
All types (concept, property etc) can now accessed and updated via their key (see swagger ui for details) in the api
Masterdata api was updated to use keys for all requests (see swagger ui)
UI features/improvements
A lot of different UI updates and improvements were made in this version. Below is a list of all the changes in this version. The tasks containing more information were linked.
CI Browser: show empty CDCM config items in Configurations Used folder
In Configuration Items "Source" should be "Storage Location"
Design of "Cancel" and "Save" button is inconsistent throughout the application
Bug fixes
Known Issues
Re-Order of Configuration Items is not persisted