Release 2021.02

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.

Important Due to an uncovered issue during testing, this release has been cancelled. All content from this release will be available in the 2021.03 release.

Generally available features

New features

Collibra Console

  • To install or upgrade an on-premises Jobserver, you can now download an independent Jobserver installer, instead of the full on-premises Collibra DGC installer. Similar to the full installer, this slimmed-down installer will be available along with the full installer, on a quarterly basis.

Collibra Data Catalog

  • MariaDB is now available on Marketplace as a certified Data Catalog connector.

Collibra Data Governance

  • You can now export a CSV file containing the user table, including the last login time from the Users page in the DGC Settings.

Diagrams

  • In the JSON text editor for diagram views, you can now specify the maximum flow depth, meaning the flow relation path length from the start flow node to any other flow node. This reduces diagram size and improves readability and performance. You can specify a system-wide default maximum flow depth in Collibra Console.

Search

  • Improved ordering of search results, as the search engine now takes into account partial exact matching of the search text in the Name field.

Collibra for Desktop

  • Asset diagram pictures are now available in Collibra for Desktop. These pictures allow a better understanding of the asset's context. You will also have a direct link to open the corresponding diagram in Collibra.
  • You can now complete workflow tasks such as reviewing an asset or voting for an asset.
  • You can also start workflows such as proposing a new business term or asking a question to an expert. It is possible that complex workflows, for example a workflow with multiple step forms, won't work.
  • If your organization has more than one Collibra environment, you can now easily switch between them.
  • You can now configure a session timeout for Collibra for Desktop, which will automatically sign out users from the app after a certain period of inactivity.

Collibra for Mobile

  • When you sign in with a username and password, you can now use Touch ID and Face ID to sign in to Collibra for Mobile.
  • You can now configure a default browser via your mobile device management software. The default browser is used to sign in to the app. If the browser that is specified as the default is not installed on your device, an error message is shown and you are unable to sign in to the app. (ticket #57109)
  • You can now configure notification message that is shown before you sign in to the app, for example to notify the user that they are using governmental property.

Data Privacy and Workflows

  • A Business Process Management workflow is now available with improved user experience for onboarding Business Process assets.
  • You can non longer directly edit the raw workflow definition on the worflow definition page in Collibra.

Enhancements

Collibra Console

  • You can now configure the SAML Entity ID separately in Collibra Console.

Collibra Data Catalog

  • If you upgraded to Tableau 2020.02 or newer, you can now synchronize your Tableau Server without losing manually added characteristics, tags, comments and stitching results.
  • The logs of the Jobserver are now improved.
  • Collibra Data Intelligence cloud now uses native sampling if you enable push down sampling for Databricks.
  • The Physical Data Connector now supports pagination of displayed physical data on all levels of the physical data hierarchy. This update allows for the analysis of extremely large data sets in a more scalable way.
  • The assignment rules of the Tableau Workbook asset type have been improved. (ticket #53643)
  • The URL attribute type is now added to the global assignment of the Looker Query asset type.

Collibra Data Lineage and BI integrations

Note Collibra Data Lineage is a cloud-only feature.

  • The connection to the Collibra Data Lineage is now improved.
  • Collibra Data Lineage now supports transformation logic for IBM DataStage.
  • The Power BI and lineage harvesters can now connect to a server address located in Australia for Google cloud users. If you change firewall rules to include the new Collibra Data Lineage server’s IP address, run the harvester with a full-sync command and restart the DGC service in Collibra Console.

  • Collibra Data Lineage now support summary tables in a DB2 data source.

Collibra Data Governance

  • If you import an attribute type with allowed values via the Solution install mode of the Migration feature, allowed values from the CMA file are now added to the list of allowed values in the target environment.
  • All logged user actions now mention the session ID.
  • The loading time of the Migration export page has been improved.
  • When you now print an asset page, the responsibilities are also included.
  • When using Open API with basic authentication, only one session is created for the user, which improves performance and logging.
  • The assignment rules of the Tableau Workbook asset type have been improved. (ticket #53643)
  • The URL attribute type is now added to the global assignment of the Looker Query asset type.

Fixes

Collibra Data Catalog

  • The API endpoint /rest/catalog/1.0/schemas/marketplace/accounting now works correctly.
  • You no longer see an error message about the asset recommender after signing in. (ticket #55667)
  • The Profiling information attribute that is shown on a Table asset page after profiling failed is now no longer shown after you refresh a schema and the data source is profiled successfully. (ticket #53186)
  • If you enabled push down sampling for a data source and the push down sampling process failed for a table or a view, Catalog now skips the table or view and continues with the next. (ticket #56341, 56404, 56605)
  • If you enabled push down sampling for a data source for which push down sampling is not supported, Catalog no longer reverts to the regular profiling process, but doesn't profile your data source at all.
  • The Google BigQuery Catalog connector can now ingest nested columns, columns of the type RECORD containing JSON, and represent them as unnested columns. (ticket #55160)
  • The REMARKS property of tables and columns is no longer stored in the Description attribute, but in a new attribute of the type Description from source system. As a result, changes made to the description in the data source will be reflected in Catalog after every refresh rather than never being updated after the initial ingestion. (ticket #57284, 54734, 55772, 57661)
  • The connection string and connection properties of a JDBC driver can now consist of more than 255 characters. (ticket #56609, 56558, 56586)
  • The Responsibilities tab page is available again on Looker Look asset pages. (ticket #57609)

Collibra Data Lineage and BI integrations

Note Collibra Data Lineage is a cloud-only feature.

  • The Power BI harvester can now process Power BI data with a large number of workspaces. (ticket #57040, 57240)
  • The Power BI metadata process is now improved to create a full technical lineage for Power BI Data Set Column assets. (ticket #57048)

Collibra Data Governance

  • Your Collibra license now expires at the end of the expiry date instead of at the start.
  • You can now only upload BPMN, ZIP, BAR and BPMN20.XML files on the Workflow Definition page.
  • SSO users can no longer edit their user profile, including their email address.
  • SSO users can no longer edit their password in Collibra. (ticket #53256, 55438)
  • Line breaks in UI strings are now handled correctly.
  • After signing in via SSO, Collibra now redirects using HTTPS instead of HTTP. (ticket #56438, 57954)
  • You can no longer start to revalidate an asset while it is being validated.
  • Updating the legs of a complex relation type via the REST API no longer fails. (ticket #54922)
  • The "last modified date" and "last modified by" fields of assets now update correctly again when you edit an attribute of the asset. (ticket #56386, 58243)
  • The visibility of the filter rule of advanced asset filters is improved. (ticket #57911)
  • The main menu no longer crashes if you perform actions in the Browse pane (ticket #58650, 58761, 58511)
  • You no longer get an "unknown field error" in table views, for example when sorting. (ticket #54258)
  • If you are on a Domain or Community page, and you have the Asset > Add resource permission, but not the Domain > Add and Community > Add, the Global Create button is available again. (ticket #57730, 57855, 57965, 58107, 58154, 58155, 58356, 58486, 58674)
  • In asset tables and sets of tiles, attributes that contain a numerical value with decimals now always show two decimal places. (ticket #54908)
  • Custom favicons are now displayed correctly. (ticket #55616, 56003, 56104, 57879, 58163, 58469)
  • When you create a new dashboard, Collibra no longer adds several copies of the new dashboard. (ticket #59040)

Diagrams

  • You can again start a workflow from an asset in a diagram without being prompted to sign in to Collibra.

Collibra for Desktop

  • The first comment on an asset now shows the actual user instead of "Deleted user". (ticket #58510)

Collibra for Mobile

  • When you configure the app settings in Collibra Console of your Collibra environment, the settings are now correctly applied in the app. You need Collibra 2021.01 or newer.

Patches

Patch 1

  • The Jobserver-only installer now correctly installs the agent in all installation scenarios. (ticket #59915, 60077)
  • You can again configure the Jobserver to poll Collibra for jobs.
  • You can again directly edit workflows via the workflow definition in Collibra. This feature was disabled in version 2021.02.
  • Users with Consumer license but with the permission to update tags can again add tags to assets. (ticket #58394, 58557)
  • While performing certain operations, for example a Tableau synchronization, it could occur that users were no longer able to sign in, which could result in an unresponsive Collibra environment. In that situation, the Collibra environment required a restart. The fix prevents the Collibra environment from becoming unresponsive for those specific operations.