Fixes for Collibra Data Governance Center 5.7.6
5.7.6-114
- The connection to the Collibra Data Intelligence database is now closed after you create a technical lineage.
5.7.6-106
- The migration of data now respects the correct role direction of relations when importing a data quality rule.
- Deleting a large amount of assets has an increased performance.
- A scope that includes a community, no longer directly includes the children of that community. They are included automatically as a result of inheritance.
- Completing a workflow task that contains a "relationtype" field via the Core REST API /workflowTasks/completed endpoint no longer causes an error when you specify the relation direction.
- Resource role names that contain "reviewer" no longer prevent you from performing the Reassign Reviewer task of the out-of-the-box Issue Management workflow.
- You can now add an asset or domain restriction to a workflow definition only when the “Applies To” option is set to Asset or Domain, respectively.
- Having a "datetime" process variable in a workflow no longer causes an error when editing the process variables on the workflow definition settings page in Collibra Data Governance Center.
- You no longer receive notification emails of passed events after an upgrade. (ticket #42840)
- You can again rebuild automatic hyperlinks.
- The relations table has two extra indexes that increase the performance.
- When saving a view, the view is now validated to ensure that it can be correctly parsed, saved and reopened.
- The endpoint URLs are updated in the Hitchhiker's Guide to the Output Module. (ticket #47820)
- The Recently viewed widget on dashboards now shows the correct month. (ticket #44207)
- The field selector in a relation table now shows only relevant characteristic types.
- The Collibra Console API no longer shows encrypted passwords. (ticket #36336)
- Fixed an XSS vulnerability in the Collibra Console API. (ticket #36336, 38443)
- JMX is disabled by default on the agent and Collibra Console. (ticket #48818)
- Vacuum commands are no longer executed on slaves of a repository cluster. (ticket #49612, 45955)
- A root installation on RHEL 7 and 8 now correctly uses systemd instead of systemv. (ticket #49609)
- The Request Assets Access workflow no longer uses private API calls. (ticket #46224)
- You can now safely remove the relation type 'Data Set related to/impacted by Business Asset' from the assignment of the Data Set asset type and its children.
- You can now safely remove the relation type 'Data Set contains/is part of Data Element' from the assignment of the Data Set asset type and its children. (ticket #48147)
- You can now add child asset types of Data Set to the Data Basket. (ticket 41326)
- You can now access Catalog Home if you have the Catalog Author role. (ticket #49955)
- The activities table now shows the Created On column.
- When a user adds an attribute, the asset history now shows the characters "<" and ">" correctly. (ticket #48021)
- The statuses in the Responsibilities table of the Profile page no longer are no longer hyperlinks. (ticket #47794)
- The documentation of the PATCH bulk API methods now mentions that you have to pass the ID field.
- In the Organization facet dialog box, up to 15 subcommunities are now shown when relevant to the search results.
- The repository diagnostics now produce a set of files with advanced database statistics that contain a detailed overview of the database internal state and the type of queries it runs.
- The jobs table in the database now has an index, which makes pages load faster.
- Fixed support for Apache JServ Protocol (AJP).