Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Helm Chart V 0.1.6

  • Changed mongoConnectionString (as mentioned above)

  • added Java options for host, port and nonProxyHosts

  • added resource limits for Java and Docker

Single Page Application V 0.1.6

  • New Features

  • Fixed issues found in the MVP test

Breaking Changes

MONGO_CONNECTION_STRING env variable

Configuration of the database connection was simplified. This also enabled the configuration of multiple hosts, which is needed for the usage of replica sets. To configure the connection to the database a single connection string has to be set for the MONGO_CONNECTION_STRING env variable (also documented in this env variable table here). Other env variables regarding the database connection were removed.

Features

Form Builder

Changing the order of controls: The Form Builder supports to change the order of the controls that have been added to a form by clicking on the drag icon and dragging and dropping the control at the desired position in the form.

Empty control spaces: Adding controls means that all added controls are added in a sequence horizontally and when a row of controls is occupied the next control will be placed into the next row. The user can now choose to add an empty control. This allows to define the user interface in a more flexible way.

Definition of the column width of the controls grid: Each column of the controls grid of a user interface can now be dragged to define its width by percentage of the available horizontal space. When the user increases / decreases the width of a column, then all columns right of this column will be decreased / increased in their width.
Additionally, a minimum width can be assigned to each column. When the overall width of the browser is too small to show all controls at their minimum width, then a horizontal scrollbar will be shown that allows to scroll the content horizontally.

Configuration browser: All sub configurations are now structured under a node “Configurations Used”.

Audit history of components and configurations: The order of the columns in the audit history have been re-ordered to a more logical way. Still, we see room for improvement so the user better understands what has happened.

Version Number: The version number of the CDCM instance is now visible under the Administration area.

Issues Fixed

T0110: Show user names instead of user ids

...

T0066: Title "Can be restriction to search" can be misleading. Maybe instead "Filter by this attribute"

T0082: Config Area definition issues