Fixes for Collibra Console 5.7.0-60

  • The authentication to email handlers no longer fails if non-alphanumeric characters are used in the password.
  • Restoring a backup now recalculates the metrics for data quality.
  • A purge process no longer removes the data that is necessary to calculate the data quality.
  • When you upload a license file, the license page is now immediately updated.
  • It is no longer possible to enter values greater than 1 if the expected value is between 0 and 1.
  • The port of a mail handler is no longer marked as mandatory if you leave it empty.
  • In a service configuration, you can now delete values that are selected from an enumeration, for example notification days.
  • A user locale can no longer prevent an installation.
  • An improved error message appears when an error occurs during the validation of the Data Governance Center service. More details are then stored in the agent logs.
  • Decreased the size of the Create backup dialog box.
  • You can again stop an incomplete environment that still contains running services.
  • In some specific scenarios, missing notification messages are now shown.
  • On Linux, the installation using the graphical user interface now succeeds even when required fonts are not installed.
  • Password reset emails are now sent to every user with the matching email address.
  • Collibra Console redirects to the sign-in page after a configurable time of inactivity.
  • The backup API documentation has been corrected.
  • Updating the Collibra Console email settings no longer require a restart.
  • Performing two installations on the same node with root privileges is now prevented by the installer. Only the first installation succeeds.
  • Creating a large number of backups in a short period no longer causes the Collibra Console to stop responding.
  • You can now start or stop a partially running repository cluster via the API.
  • An HTTPS port value of a service no longer shows a comma on the service's overview page.
  • When you upgrade the Search service, you now have to enter the hostname in the upgrade wizard.
  • After an upgrade, repository clusters are now correctly fetched and added to the environment.