Release 2020.10
This release is only available for Collibra Platform. Features and enhancements that are marked with cloud-only will never become available for on-premises environments.
Generally available features
New features
Collibra Console
- You can now access Collibra Console via single sign-on. The SSO protocol is limited to SAML 2.0.
- The logging API endpoints for Collibra Console are now public.
CollibraData Catalog
- The Collibra Data Classification model is expanding to automatically classify a number of new types of information out of the box. This release has a specific focus on privacy, offering classification of the following default classes:
- US Adoption Taxpayer Identification Number (ATIN)
- American Banking Association (ABA) Routing Number
- US Drivers License Number
- US Employer ID Number (EIN)
- US Individual Taxpayer Identification Number (ITIN)
- Vehicle Identification Number (VIN)
- US License Plate Number
- UK Drivers License Number
- UK National Health Service (NHS) Number
- Business vs. Personal Email Addresses
Collibra Data Lineage
- Collibra Data Lineage now supports transformations in SQL Server Integration Services (SSIS).
- You can now create a technical lineage for Netezza and Sybase Adaptive Server Enterprise data sources.
Collibra Integrations
- Collibra ERP/CRM Integrator is a next-generation integration for ERP and CRM solutions like SAP, JD Edwards, and MS Dynamics, which supports greater control and fidelity in what metadata to catalog in Collibra as it is discovered. ERP/CRM Integrator is a special connector and is not included in any bundles.
Enhancements
CollibraData Catalog
- Power BI Data Set assets now have a relation of the type "BI Folder contains BI Data Set" to a Power BI Workspace asset. They are no longer related to Power BI Tenant assets via this relation type.
- The More menu in asset pages is now called 'Actions' when Catalog Experience is enabled.
- Catalog Experience is no longer a feature in preview.
Collibra Data Lineage
- The "collibra" section in the lineage harvester configuration file is now called "catalog".
- The API key is no longer needed in the configuration file if you purchased Collibra Data Lineage.
Collibra Data Governance
- You can now migrate model objects between all versions newer than 5.7.
- We have fixed some security vulnerabilities by upgrading to the latest version of Apache Shiro (1.6.0).
- The performance to show large hierarchies is improved due to an updated hierarchy calculation strategy. (ticket #53015, 51820, 51613)
- The amount of available views that you can see in the view table is increased from 300 to 1,000. (ticket #51694)
- When you import assets, the DGC service log now contains new INFO log entries about the start date, end date and the duration of the import.
- When you open a diagram, the DGC service log now contains new INFO log entries about the back-end response time and the number of retrieved nodes and edges.
- Improved search performance due to fewer postgreSQL calls when showing search results.
- You can again add a "mailto" link in the Help menu of Collibra Platform. (ticket #52169)
Fixes
CollibraData Catalog
- When an ingestion fails, the job no longer indicates that it took 50 years to complete. (ticket #48924)
- When you stop an ingestion or profiling process in the Jobserver, the context processes are now terminated. (ticket #52388)
- The default time pattern for profiling parameters in the Jobserver is now correctly handled.
- The history page of an S3 File System asset type now correctly shows only activities related to the asset. (ticket #52193)
- An ingestion job no longer fails when you register a data source with a large number of assets or foreign keys and you have defined a cron expression in the Register a data source dialog box. (ticket #48947)
- When an ingestion job fails, the Data Profiling Results report now correctly shows the duration of the ingestion process. (ticket #48924)
- You can now see icons of tags and comments in the titlebar of asset pages when Catalog Experience is enabled in dark theme.
- On a Table asset page, sample data of a Column asset is shown as "sensitive", if you do not have the View Samples permission for the Column asset, but you do have it for at least one other Column asset from the same Table asset.
- On a Data Set asset page, sample data of a Column asset is shown as "sensitive", if you do not have the View Samples permission for the Column asset, but you do have it for at least one other Column asset from the same Table asset that is also in the Data Set.
Collibra Console
- In the Data Governance Center Configuration section in Collibra Console, the Register data source, Data profiling and features in preview are now accessible for users with the ADMIN role.
- Confidential information is no longer disclosed in a stacktrace.
- The Group Base DN and Membership attributes are no longer mandatory to configure LDAP. (ticket #47737, 47207)
- The version of the web server is no longer shown on error pages.
- Upgrading an environment that has a repository cluster no longer fails. (ticket #51499)
- When SAML_LDAP is used with SSO and the identifier is not the username, the login is now successful. (ticket #52203)
- GraphQL schema introspection is now disabled by default. You can enable it in the DGC service configuration in Collibra Console.
- If SAML is enabled and signing in fails, the error message now appears correctly on the sign-in page. (ticket #48715, 53020)
- If a user account in Collibra has an invalid email address, LDAP synchronization no longer fails, but it ignores the user. (ticket #52455)
Collibra Data Privacy
- When approved, a Compliance Self Assessment asset that was created with two parties in scope, now has the correct status Approved, instead of Obsolete.
- An Event-based Review Rule is now triggered when an edit is first made to the approved target Business Process asset. Previously, it was only triggered if a second edit was made to the target asset.
- If you start a manual review request for an assessment asset and select the option “Involve me in the feedback”, you are now correctly assigned the Stakeholder responsibility for the newly created assessment asset.
- When working from an approved Compliance Self Assessment asset, the Update Asset Directly workflow now works correctly when you choose the option “Copy data from a previous Compliance Self Assessment.
- In the Manual Review Request workflow, the Update <asset type> button now works correctly for all asset types.
- For new installations, the following updates are applied in the Privacy framework section of the Privacy dashboard:
- The “standards” link now points to the search page, where all Standard assets are shown.
- The “roles and responsibilities” link has been removed.
- For new installations, the Identifier attribute (UUID c0e00000-0000-0000-0001-000500000043) is no longer included in the CMA installation files, as it is no longer part of the Data Privacy operating model.
Collibra Data Governance
- On a Catalog Schema asset page, the "Refresh" button is no longer shown if you don't have the necessary permissions. (ticket #49924)
- The suggested asset types in the Global Create dialog box now take into account the current scope. (ticket #49272)
- If you edit an attribute directly after starting a workflow, the asset page now refreshes correctly. (ticket #51989)
- The Activities pop-up window now correctly refreshes when you cancel a job.
- When using the relation API to add relations, duplicate relations will be ignored. (ticket #52765)
- Migration will no longer treat the order of view assignment rules, view sharing rules or data quality metrics as a difference as it is non-deterministic. (ticket #49528)
- In the Responsibilities page of a resource, you can now remove a responsibility when the pop-up window with user or group information is shown. (ticket #52046)
- After you sign out, the password field in the Sign in dialog box is now empty. (ticket #52409)
- Group entries in history now show all dates in local time. (ticket #52194)
- When using the REST API, concurrent logins with basic authentication no longer cause an error. (ticket #52273)
- Data Quality score is now always up to date. (ticket #49984, 51284)
- The history no longer shows an entry when creating a relation that failed due to maximum cardinality. (ticket #36292)
- You can no longer create user groups via the GraphQL API if you don't have the User Administration or System Administration permission.
- Importing a too large set of objects now fails with a clear error message. (ticket #50748, 50488)
- When an import job fails, the import report now only contains the first 200 errors. (ticket #49361, 50057)
- When working with search results, the “Search in fields” dialog box no longer shows fields when invalid text is entered to refine the list of fields.
- The workflow buttons appear again without delays. (ticket #50992)
Patches
Patch 1
- Assets created by synchronizing Tableau, S3 and Data sources are now properly indexed and are available in the search (ticket #53581).
Patch 2
- In Collibra Platform version 2020.10.0 and 2020.10.1 there was an issue allowing a broken workflow to cause a system wide outage for a number of users. This issue is fixed in this patch. (ticket #54359, 54464)