Helm Chart V 1.0.0

• reference CDCM Application in Version 1.0.0

New Features

• Possibility to configure a secret for a trust store and a trust store password

• Possibility to configure a secret that contains the connection routing configuration “connection-routing.yml”

Single Page Application V 1.0.0

Breaking changes

• The following redirect URL has to be added in the identity provider user for Login: {cdcmhostURL}/login/oauth2/code/primary

• For every connection configured in connection routing that uses Oauth2 a a redirect URI like this has to be added to the corresponding identity provider: {{cdcmhostURL}}/external-login/oauth2-redirect/{connectionId} (connectionId is configured in the connection-routing.yml)

New Features

Full-Text Search on Atlas

• The search was improved to use Atlas Search if the application is running on an Atlas Cluster as database

• Indices are created and updated automatically on bootup of the application

• The feature is designed in a backwards compatible manner, meaning it detects if running on a normal MongoDB / Cluster or on Atlas and depending on that use the classic text-base search or the advanced Atlas Search with full Lucene Index

  • The behaviour can be controlled via MONGO_RUNNING_ON_ATLAS environment variable. By default it is set to ‘autodetect’

• There is a short documentation on how to use the search here: Search

Improved Logging

• More logging: Logging of entering and existing of methods. This means you can much better understand the data flow during all operations. This is logged with the DEBUG logging level

• Set logging level via environment variable: LOGGING_LEVEL env variable can be used to set the logging level. Available levels:

  • TRACE

  • DEBUG (default)

  • INFO

  • WARN

  • ERROR

  • FATAL

  • OFF

Connection routing

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.ymlcan 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)

• Added search filter for searching by Tags. Filter works as AND.

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.

• Adopt the date time format to the localization

• Groups in CI browser

• Sharepoint picker enhancement

• Add tags as filters to search

• CI Browser: show empty CDCM config items in Configurations Used folder

• Delegated UI usability improvement

• Login Flow changes

• Manage Roles and Premissions UI

• In Configuration Items "Source" should be "Storage Location"

• Storage Location References

• Adding / Replacing a configuration item

• Storage Location Lists: Remove non-common attributes

• Minor UI Changes ongoing

• Delegated UI for Configuration/Component/EWP

• Cannot do anything in a space when there is no config area

• Rebuild loading overlay

• CI Browser: Groups UI improvements

• Instead of the Angular Icon, use the Smartfacts Icon

• Design of "Cancel" and "Save" button is inconsistent throughout the application

• maintain streams (add / remove / replace) incl. the configuration structure (manually / automatically)

• Replace IWPs and EWPs in a configuration

• Storage Location rootservice feedback

• Import / Export UI of configuration data

Bug fixes

• [State Model] - State Names

• [API] - missing function update master data table row with key

• [Roles & Rights] - User can be stuck with no active element in login screen

• [API] - GetMasterDataTable row works only with ID

• [UI / Data Browsing] - Baseline/Derived Stream Name change doesn`t take any effect

• [API] - Bulk import for MasterData doesn't support upsert

• [Storage Locations] - Physical /Software with authorization errors

Known Issues

• Re-Order of Configuration Items is not persisted