Only show release notes of Collibra Cloud for Government-certified features

Release 2022.11

Release information

  • Release date of 2022.11.0: November 6, 2022
    • Upgrade non-production environments: November 6, 2022
    • Upgrade production environments: November 27, 2022
  • Release date of 2022.11.1: November 27, 2022
  • Release date of 2022.11.2: December 13, 2022
  • Release date of 2022.11.3: December 22, 2022
  • Release date of 2022.11.4: January 8, 2023
  • Relevant Jobserver version:
    • 2022.11.0-52 (uses PostgreSQL 10)
    • 2023.01.0-63 (uses PostgreSQL 11)

Highlights

  • You can now protect sensitive data and grant varying levels of access to the data to specific groups of people through policies that do not require you to code. To facilitate this, a new product, Collibra Protect, is now available. You can enforce data protection at the source database level directly from the Collibra Protect interface, and apply advanced data protection through masking, redacting, and hashing. Collibra Protect simplifies access governance and eliminates the need for repetitive actions and approvals. By providing permission to view information to only those who need it, Collibra Protect minimizes risk and promotes a safe data culture in your organization.

  • Data Marketplace is now generally available! Data Marketplace is where you can find trusted data across Collibra Platform.
    Administrators can tailor the Data Marketplace search and filters by configuring relation-based search and filters, previously known as custom facets.
    Customers who requested the creation of custom relation-based filters and relation paths for relation-based search before release 2022.11, need to recreate the relation paths manually via the new interface. The interface takes all validations and limitations into account.

  • A new Homepage experience is now available in Collibra Platform. This new, pre-configured Homepage is the new entrance to Collibra. The Homepage guides you within Collibra by showing relevant information such as your dashboards, the most visited assets, and the recommended assets. You can also quickly perform a search and find the data that is most important to you.

    Note The Homepage is disabled by default, except if your environment was created in or after version 2022.11.

  • You can now use the Usage Analytics dashboard, which is a usage-focused dashboard that provides you insights of who in your organization is using Collibra Platform and how they are using and engaging with it. The Usage Analytics dashboard shows you data on users, content, and products. You can use this data to monitor user activities, understand the total asset coverage, identify popular communities or assets, allocate efforts, and maximize your investment and recharge costs. In addition, you can view the usage over time, observe trends, and measure success.

  • When you integrate Power BI:
    • Inactive workspaces and personal workspaces are no longer ingested.
    • Filtering is improved. You can now use the optional properties "excludeWorkspaceNames" and "excludeWorkspaceIds" to exclude specified workspaces. Before configuring your filters, ensure that you read all about the advantages, limitations and configuration considerations in Power BI workspaces.

  • The Collibra sampling feature has been enhanced and can now support the use of Sample data via Edge. If you have the required permissions, you can request to see sample data for a data source registered via Edge.

  • During the upgrade to 2022.11, the out-of-the-box PostgreSQL, Oracle, and Microsoft SQL Server driver JAR files are removed for data sources registered via your own driver and Jobserver. The upgrade logs provide details on the impact this has on your environment.

  • We no longer provide support for new Edge installations on CentOS 8 Linux as it has been deprecated. Existing Edge sites will continue to run on CentOS 8, but to continue receiving Edge support, upgrade to RedHat Enterprise Linux 8.x by following the back up and restore an Edge site instructions.

  • Collibra has standardized on user definitions and are using “Standard” and “Read-only”. There are also changes to how licenses are monitored and updated, including:

    • A new column on the User table for ‘Latest workflow participation’
    • An "Effective" user metric above the User table
    • The ability to export user totals
    • License info has been removed from user profile
    • Given license has been dropped. Admins now no longer need to manually give a license to a user
    • License exceeded banner (based on given license) has been removed from Collibra Platform
    • License related information and banners have been removed from Collibra Console
    • Changes to the API (see API fixes below)

    For more information, see User licenses.

Metamodel changes

  • A metamodel for Azure Data Lake Store (ADLS) is available to support the upcoming ADLS integration. The metamodel can change based on feedback from the upcoming ADLS integration Beta testing.
  • Fixed an issue in the Patch Scope API when adding a list of domains.
  • You can once again create, edit and delete articulation score rules in the Global Assignment tab of an asset page without having to change the condition value of already existing articulation score rules.

New features

Data Catalog

  • During the upgrade to 2022.11, the out-of-the-box PostgreSQL, Oracle, and Microsoft SQL Server driver JAR files are removed for data sources registered via your own driver and Jobserver. The upgrade logs provide details on the impact this has on your environment.
  • The Collibra sampling feature has been enhanced and can now support the use of Sample data via Edge. If you have the required permissions, you can request to see sample data for a data source registered via Edge.
  • You can now profile up to four databases in parallel via Edge.
  • You can now use partial scan to profile AWS Athena and AWS Glue data sources via Edge.

Data Marketplace

  • Data Marketplace is now generally available! Data Marketplace is where you can find trusted data across Collibra Platform.
  • Administrators can tailor the Data Marketplace search and filters by configuring relation-based search and filters, previously known as custom facets.
    Customers who requested the creation of custom relation-based filters and relation paths for relation-based search before release 2022.11, need to recreate the relation paths manually via the new interface. The interface takes all validations and limitations into account.

Enhancements

Data Catalog

  • During the upgrade to 2022.11, the out-of-the-box PostgreSQL, Oracle, and Microsoft SQL Server driver JAR files are removed for data sources registered via your own driver and Jobserver. The upgrade logs provide details on the impact this has on your environment.
  • It is now possible to edit the Jobserver connection properties, even when the connection configuration has been used to successfully register a data source.
  • In the Data Classification page, when you select a data class, hyperlinks are now available for all classified columns.
  • The Collibra sampling feature has been enhanced and can now support the use of Sample data via Edge. If you have the required permissions, you can request to see sample data for a data source registered via Edge.

Data Lineage and BI integrations

  • When you integrate Power BI, the ownership information (admin and creator email addresses only) for reports is now ingested in Collibra. The "Owner in source" attribute is included on Power BI Report asset pages.
  • Collibra Data Lineage now supports Microsoft SQL Server data sources for MicroStrategy integration.
  • The lineage harvester now uses Looker 4.0 APIs, with paging options.
  • When you integrate Tableau:
    • When you integrate Tableau, the ownership information (email addresses only) for projects, data models, workbooks and dashboard is now ingested in Collibra. The "Owner in source" attribute is included on Tableau Project, Tableau Data Model, Tableau Workbook and Tableau Dashboard asset pages.
    • You can now ingest sites that don't have workbooks.
    • Previously, when you filtered on a site, a Tableau Site asset was created in Collibra, but no metadata was ingested. Now, when you filter on a site, all metadata in the site is ingested in the specified domain. If, however, a site is specified in the lineage harvester configuration file, but not in the "filters" and "domainMapping" properties in the Tableau <source ID> configuration file, the metadata is ingested in the default domain.
    • You can now use wildcards in the "filters" property in the Tableau <source ID> configuration file. Also, the "filters" property is no longer case-sensitive.
  • When you integrate Snowflake data sources, the Collibra Data Lineage service instances now correctly parse “IDENTIFIER(string_literal)” constructs and interpret them as corresponding database object references.
  • When you ingest metadata from Oracle data sources, you can now add a new "DatabaseOracle" section in your lineage harvester configuration file, to specify the Oracle database name and ensure stitching without any workarounds.
  • Transformation descriptions in Informatica PowerCenter are now shown in the technical lineage Sources tab page.
  • When you ingest SQL Server Integration Services (SSIS) data sources, the Collibra Data Lineage service instances now parse SQL statements that begin with a comment. Previously, these SQL statements were ignored without an error message.
  • When you ingest Informatica Intelligent Cloud Services data sources:
    • Collibra Data Lineage now shows conditions on Joiner transformations.
    • Custom expression code and routing expression code is now shown in the transformations table on the technical lineage Sources tab page.

Data Marketplace

  • Data Marketplace has integrated the Collibra top bar. As a result, the option to activate search suggestions has moved to the Data Marketplace settings.
  • Several changes have been made to enhance the visual design and usability:
    • More filter tabs can be displayed on a page.
    • You can now sort your search results based on relevance and date.
    • There is less space between the title and the related values in the asset preview.
    • The button to open BI and Tableau report assets is more visible.
  • Some service configuration setting names have changed.
    • "Search over relations" changed to "Relation-based search".
    • "Consistency for Custom facets and Search over Relations" changed to "Automatic relation indexing".
  • Some service configuration settings moved to other locations in the Collibra service settings page.
    • Data Marketplace is available in the Data Marketplace section.
    • Relation-based search is available in the Search index configuration section.
    • The settings are enabled by default in new environments.
  • The "Automatic relation indexing" setting now also reindexes the custom relation paths created or updated after the 2022.11 release.
  • Administrators can now remove the primary action from asset previews.
  • The maximum number of relations in a custom relation path has been set to four.
  • You can create a maximum of 20 relation indexes to be used in the relation-based search and filters.
  • When you create a full backup of Collibra, the Data Marketplace data is now included in this backup.
  • The URL for Data Marketplace has changed to [your environment]/apps/data-marketplace.

Data Governance

  • Domain names on the History tab page of an asset page are now links to those domains.
  • If you assign a relation type to an asset type you can now restrict the target asset type of the relation type to one of the subtypes of the target.
  • The asset import wizard is now improved using version 2 of the Import API for better performance, with a refreshed interface and more intuitive mapping. The v2 import feature is currently turned off by default but can be enabled via Collibra Console. The v2 import will be enabled by default in a future release. (ticket #56018)
  • When using the new import interface, if a relation type in your import file matches with multiple relation types in Collibra then this will no longer be auto-mapped, instead you will need to map it yourself. (ticket #83005)
  • You can now define distinct cardinalities for both directions of an assigned relation type with either identical head and tail or head and tail being ancestors of one another.
  • Self-relation types are now divided in the assignment table with the head and tail appearing on separate lines.
    Asset type Asset Type UUIIDRelation Type Relation Type definition UUIID
    ADLS Container00000000-0000-0000-0001-002800000003contains / contained in00000000-0000-0000-0000-000000007060
    ADLS Container00000000-0000-0000-0001-002800000003contains / is part of00000000-0000-0000-0001-002600000001
    ADLS File System00000000-0000-0000-0001-002800000001contains / is part of00000000-0000-0000-0001-002600000000
    ADLS Storage Account00000000-0000-0000-0001-002800000002contains / is part of00000000-0000-0000-0001-002600000001
    Assessment Review00000000-0000-0000-0000-000000031305is assessed by / assesses00000000-0000-0000-0000-000000007097
    Business Asset00000000-0000-0000-0000-000000031101groups / grouped by00000000-0000-0000-0000-000000007021
    Business Process00000000-0000-0000-0000-000000031103produces / is produced by00000000-0000-0000-0000-000000007006
    Business Process00000000-0000-0000-0000-000000031103classifies / is classified by00000000-0000-0000-0000-000000007007
    Business Process00000000-0000-0000-0000-000000031103groups / grouped by00000000-0000-0000-0000-000000007021
    Business Process00000000-0000-0000-0000-000000031103consumes / is consumed by00000000-0000-0000-0000-000000007063
    Business Qualifier00000000-0000-0000-0000-000000031115groups / grouped by00000000-0000-0000-0000-000000007021
    Business Qualifier00000000-0000-0000-0000-000000031115qualifies / is qualified by00000000-0000-0000-0000-000000007096
    Business Rule00000000-0000-0000-0000-000000031204governed by / governs00000000-0000-0000-0000-000000007009
    Business Rule00000000-0000-0000-0000-000000031204is implemented by / implements00000000-0000-0000-0000-000000007014
    Business Rule00000000-0000-0000-0000-000000031204complies to / applies to00000000-0000-0000-0000-000000007018
    Business Rule00000000-0000-0000-0000-000000031204groups / is grouped by00000000-0000-0000-0000-000000007056
    Business Term00000000-0000-0000-0000-000000011001synonym / synonym of00000000-0000-0000-0000-000000007001
    Business Term00000000-0000-0000-0000-000000011001allowed value / allowed value of00000000-0000-0000-0000-000000007003
    Business Term00000000-0000-0000-0000-000000011001groups / grouped by00000000-0000-0000-0000-000000007021
    Code Value00000000-0000-0000-0000-000000021001groups / grouped by00000000-0000-0000-0000-000000007022
    Column00000000-0000-0000-0000-000000031008targets / sources00000000-0000-0000-0000-000000007069
    Database00000000-0000-0000-0000-000000031006groups / is grouped by00000000-0000-0000-0000-000000007054
    Data Category00000000-0000-0000-0000-000000031109classifies / is classified by00000000-0000-0000-0000-000000007007
    Data Category00000000-0000-0000-0000-000000031109groups / grouped by00000000-0000-0000-0000-000000007021
    Data Concept00000000-0000-0000-0000-000000031113classifies / is classified by00000000-0000-0000-0000-000000007007
    Data Concept00000000-0000-0000-0000-000000031113groups / grouped by00000000-0000-0000-0000-000000007021
    Data Domain00000000-0000-0000-0000-000000031114classifies / is classified by00000000-0000-0000-0000-000000007007
    Data Domain00000000-0000-0000-0000-000000031114groups / grouped by00000000-0000-0000-0000-000000007021
    Data Domain00000000-0000-0000-0000-000000031114has subtype / is subtype of00000000-0000-0000-0000-000000007095
    Data Quality Metric00000000-0000-0000-0000-000000031107complies to / applies to00000000-0000-0000-0000-000000007018
    Data Quality Rule00000000-0000-0000-0000-000000031205governed by / governs00000000-0000-0000-0000-000000007009
    Data Quality Rule00000000-0000-0000-0000-000000031205complies to / applies to00000000-0000-0000-0000-000000007018
    Data Usage00000000-0000-0000-0000-000000031131is essential for / requires00000000-0000-0000-0000-000000007061
    Directory00000000-0000-0000-0000-000000031303contains / is part of00000000-0000-0000-0001-002600000001
    Directory00000000-0000-0000-0000-000000031303contains / is part of00000000-0000-0000-0001-002600000003
    File Container00000000-0000-0000-0001-002900000002contains / is part of00000000-0000-0000-0001-002600000001
    GCS Bucket00000000-0000-0000-0001-002700000002contains / is part of00000000-0000-0000-0001-002600000001
    Governance Asset00000000-0000-0000-0000-000000031201complies to / applies to00000000-0000-0000-0000-000000007018
    Governance Asset00000000-0000-0000-0000-000000031201groups / is grouped by00000000-0000-0000-0000-000000007056
    Issue00000000-0000-0000-0000-000000031111related to / impacted by00000000-0000-0000-0000-000000007015
    Issue00000000-0000-0000-0000-000000031111impacts / impacted by00000000-0000-0000-0000-000000007025
    Issue Category00000000-0000-0000-0000-000000031112complies to / applies to00000000-0000-0000-0000-000000007018
    Issue Category00000000-0000-0000-0000-000000031112groups / is grouped by00000000-0000-0000-0000-000000007056
    KPI00000000-0000-0000-0000-000000011002groups / grouped by00000000-0000-0000-0000-000000007021
    Line of Business00000000-0000-0000-0000-000000031110classifies / is classified by00000000-0000-0000-0000-000000007007
    Line of Business00000000-0000-0000-0000-000000031110associates / is associated with00000000-0000-0000-0000-000000007008
    Line of Business00000000-0000-0000-0000-000000031110groups / grouped by00000000-0000-0000-0000-000000007021
    Looker Dashboard00000000-0000-0000-0000-100000000013groups / is grouped into00000000-0000-0000-0000-120000000004
    Looker Dashboard00000000-0000-0000-0000-100000000013related to / is impacted by00000000-0000-0000-0000-120000000006
    Looker Dashboard00000000-0000-0000-0000-100000000013uses / used in00000000-0000-0000-0000-120000000007
    Looker Data Set Column00000000-0000-0000-0000-100000000018targets / sources00000000-0000-0000-0000-000000007069
    Looker Folder00000000-0000-0000-0000-100000000012assembles / is assembled in00000000-0000-0000-0000-120000000001
    Looker Look00000000-0000-0000-0000-100000000014groups / is grouped into00000000-0000-0000-0000-120000000004
    Looker Look00000000-0000-0000-0000-100000000014related to / is impacted by00000000-0000-0000-0000-120000000006
    Looker Look00000000-0000-0000-0000-100000000014uses / used in00000000-0000-0000-0000-120000000007
    Looker Query00000000-0000-0000-0000-100000000016groups / is grouped into00000000-0000-0000-0000-120000000004
    Looker Query00000000-0000-0000-0000-100000000016related to / is impacted by00000000-0000-0000-0000-120000000006
    Looker Query00000000-0000-0000-0000-100000000016uses / used in00000000-0000-0000-0000-120000000007
    Looker Report Attribute00000000-0000-0000-0000-100000000019is source for / is target of00000000-0000-0000-0000-120000000008
    Looker Tile00000000-0000-0000-0000-100000000015related to / is impacted by00000000-0000-0000-0000-120000000006
    Looker Tile00000000-0000-0000-0000-100000000015uses / used in00000000-0000-0000-0000-120000000007
    Measure00000000-0000-0000-0000-000000031104groups / grouped by00000000-0000-0000-0000-000000007021
    MicroStrategy Column00000000-0000-0000-0000-100000000047targets / sources00000000-0000-0000-0000-000000007069
    MicroStrategy Dossier00000000-0000-0000-0000-100000000043groups / is grouped into00000000-0000-0000-0000-120000000004
    MicroStrategy Dossier00000000-0000-0000-0000-100000000043related to / is impacted by00000000-0000-0000-0000-120000000006
    MicroStrategy Folder00000000-0000-0000-0000-100000000042assembles / is assembled in00000000-0000-0000-0000-120000000001
    MicroStrategy Project00000000-0000-0000-0000-100000000041assembles / is assembled in00000000-0000-0000-0000-120000000001
    MicroStrategy Report00000000-0000-0000-0000-100000000044groups / is grouped into00000000-0000-0000-0000-120000000004
    MicroStrategy Report00000000-0000-0000-0000-100000000044related to / is impacted by00000000-0000-0000-0000-120000000006
    Policy00000000-0000-0000-0000-000000031202complies to / applies to00000000-0000-0000-0000-000000007018
    Policy00000000-0000-0000-0000-000000031202groups / is grouped by00000000-0000-0000-0000-000000007056
    Power BI Capacity00000000-0000-0000-0000-100000000002assembles / is assembled in00000000-0000-0000-0000-120000000001
    Power BI Column00000000-0000-0000-0000-100000000008targets / sources00000000-0000-0000-0000-000000007069
    Power BI Dashboard00000000-0000-0000-0000-100000000004related to / is impacted by00000000-0000-0000-0000-120000000006
    Power BI Dashboard00000000-0000-0000-0000-100000000004uses / used in00000000-0000-0000-0000-120000000007
    Power BI Folder00000000-0000-0000-0000-100000000020assembles / is assembled in00000000-0000-0000-0000-120000000001
    Power BI KPI00000000-0000-0000-0000-100000000021related to / is impacted by00000000-0000-0000-0000-120000000006
    Power BI Report00000000-0000-0000-0000-100000000006related to / is impacted by00000000-0000-0000-0000-120000000006
    Power BI Report00000000-0000-0000-0000-100000000006uses / used in00000000-0000-0000-0000-120000000007
    Power BI Tile00000000-0000-0000-0000-100000000005related to / is impacted by00000000-0000-0000-0000-120000000006
    Power BI Tile00000000-0000-0000-0000-100000000005uses / used in00000000-0000-0000-0000-120000000007
    Power BI Workspace00000000-0000-0000-0000-100000000003assembles / is assembled in00000000-0000-0000-0000-120000000001
    Report00000000-0000-0000-0000-000000031102groups / grouped by00000000-0000-0000-0000-000000007021
    Rule00000000-0000-0000-0000-000000031203complies to / applies to00000000-0000-0000-0000-000000007018
    Rule00000000-0000-0000-0000-000000031203groups / is grouped by00000000-0000-0000-0000-000000007056
    S3 Bucket00000000-0000-0000-0001-002400000001contains / is part of00000000-0000-0000-0001-002600000001
    SSRS KPI00000000-0000-0000-0000-100000000026related to / is impacted by00000000-0000-0000-0000-120000000006
    Standard00000000-0000-0000-0000-000000031206is included in / includes00000000-0000-0000-0000-000000007012
    Standard00000000-0000-0000-0000-000000031206complies to / applies to00000000-0000-0000-0000-000000007018
    Standard00000000-0000-0000-0000-000000031206groups / is grouped by00000000-0000-0000-0000-000000007056
    System00000000-0000-0000-0000-000000031302groups / is grouped by00000000-0000-0000-0000-000000007054
    Tableau Data Attribute00000000-0000-0000-0000-110000000010targets / sources00000000-0000-0000-0000-000000007069
    Tableau Project00000000-0000-0000-0000-110000000001assembles / is assembled in00000000-0000-0000-0000-120000000001
    Tableau Report Attribute00000000-0000-0000-0000-110000000007is source for / is target of00000000-0000-0000-0000-120000000008
    Tableau Site00000000-0000-0000-0000-110000000000assembles / is assembled in00000000-0000-0000-0000-120000000001
    Tableau View00000000-0000-0000-0000-110000000003groups / is grouped into00000000-0000-0000-0000-120000000004
    Tableau View00000000-0000-0000-0000-110000000003related to / is impacted by00000000-0000-0000-0000-120000000006
    Tableau View00000000-0000-0000-0000-110000000003uses / used in00000000-0000-0000-0000-120000000007
    Tableau Workbook00000000-0000-0000-0000-110000000002groups / is grouped into00000000-0000-0000-0000-120000000004
    Tableau Workbook00000000-0000-0000-0000-110000000002related to / is impacted by00000000-0000-0000-0000-120000000006
  • There is now a column for Job Result in the Activities table so you can see if a completed job encountered any acceptable errors, was free from errors or was cancelled.

Workflows

  • The workflows task sidebar is now enabled by default. The task sidebar replaces the task bar on resource pages.

Edge

  • K3S version upgrades are now included in the auto-update process for new Edge site installations starting from 2022.11. You need to install the newest version of Edge to acquire this new feature, as it is not included in the automatic upgrade.
  • We no longer provide support for new Edge installations on CentOS 8 Linux as it has been deprecated. Existing Edge sites will continue to run on CentOS 8, but to continue receiving Edge support, upgrade to RedHat Enterprise Linux 8.x by following the back up and restore an Edge site instructions.

Search

  • The Search reindex using Output Module setting is now removed from Collibra Console.
  • In new Collibra environments, the Asynchronous indexing setting is now enabled by default. In upgraded Collibra environments, the previous status of the Asynchronous indexing setting is retained.

Insights Data Access and Usage Analytics

API

  • You can now choose IGNORE as a finalizationStrategy parameter for the REST Import API synchronization finalization request to ignore assets that no longer exist in the external system.

Miscellaneous

  • The Browse pane now shows dashboards in addition to communities, domains, and pinned asset views.
  • Apache Commons Text has been upgraded to version 1.10.

Fixes

Data Catalog

  • The "Foreign Key Update Rule" and "Foreign Key Delete Rule" attributes in Foreign Key assets are now correctly set during the Metadata Synchronization via Jobserver and via Edge. (ticket #87076)
  • Increased stability of the JDBC ingestion via Jobserver with Reverse Proxy Server by ensuring the previous context is removed. (ticket #93131)
  • Fixed the issue with S3 synchronization via Jobserver that was caused by connection issues on HTTP level. (ticket #91640, 90141)
  • Fixed an issue where some custom data classes were incorrectly recognized as out-of-the-box data classes, which prevented a merge or deletion of those data classes. (ticket #87166, 93676) After the upgrade, we will automatically update the Classification tables to correct any impacted custom data classes.
  • Because of security reasons, some Edge data sources may not have a sampling capability configured. We now no longer show an error when you open a page that displays sample data for such a data source.
  • If you do not have the 'View Samples' permission, we no longer show an error when you open a page that displays sample data.
  • When requesting sample data for a table without columns, the HTTP error code is now 400 (bad request).
  • When you cancel a 'Request sample data' job, the job is no longer gets the 'Failed' status.
  • The order of the columns in the Sample data table is now primarily based on the column position in the data source.
  • The Sample data table now allows scrolling if no data is available. (ticket #72317)
  • The Sample data table in the Table asset page can now display up to 1,500 columns. (ticket #94851)

Data Lineage and BI integrations

  • The technical lineage graph loading times are improved. (ticket #95005)
  • When you integrate Looker and set the "useCollibraSystemName" property to "True", the Looker node now remains a separate node in the technical lineage Browse tab pane.
  • If you manually synchronize Tableau, a new Save Configuration button on Tableau Server asset pages, now allows you to save the configuration before starting the synchronization job. (ticket #90196).
  • When you ingest Informatica Intelligent Cloud Services data sources, if the "useCollibraSystemNames" property is set to “true”, databases are now shown in the technical lineage Browse tab pane with the specified system name or as "UNDEFINED”, if a database could not be mapped to a system name. If set to “False,” then all databases are now shown directly under the DATABASE node. (tickets #93243, 94290, 96244)
  • When you ingest Snowflake data sources, the databaseNames property is now correctly taken into consideration.
  • Improved handling of import jobs, to ensure that the asset types of new assets can be identified, thereby avoiding errors that result in the message “The asset type is not defined". (tickets #97571, 97579)
  • If you integrate SSRS-PBRS and use a <source ID> configuration file, the CustomDataSource section in the <source ID> configuration file is no longer mandatory.
  • When you ingest Informatica PowerCenter data sources, the Collibra Data Lineage service instances now correctly stitch for mapping overrides for ETL targets. Previously, they stitched to the wrong assets in Data Catalog.
  • When you integrate Power BI:
    • The email addresses of all admins and creators of Power BI data models and workspaces are now ingested. Previously only a single email address was ingested, even if there were multiple admins or creators of the data object in Power BI. (ticket #98570)
    • Calculated columns and measures no longer cause “analyze errors”. (ticket #92376)
  • When you ingest Informatica Intelligent Cloud Services data sources and there is a lookup procedure, if CONNECTIONSUBTYPE is empty, the Collibra Data Lineage service now looks to CONNECTIONREFERENCE for the name. If that is also empty, the name in the VARIABLE parameter is used. This is needed to correctly detect the SQL dialect. (ticket #92523)
  • When you ingest Informatica PowerCenter data sources, the lineage harvester now correctly processes session mapplets. Previously, this failed with error message "'NoneType' object has no attribute 'lower'". (ticket #94239)
  • Collibra Data Lineage now correctly ingests metadata of Tableau data objects without an owner in Tableau Server, when you use a lineage harvester version 2022.07 or older.

Data Marketplace

  • Fixed an issue where Data Marketplace could not provide any search results because an asset or a relation between assets that applies to the search criteria was removed.
  • The reindexing of relations now correctly removes information that is no longer valid.
  • Fixed an issue where Data Marketplace had an incorrect app title in the browser tab. (ticket #88571)

Data Governance

  • If you add a value to a multiple selection attribute in a table view and the attribute contains an invalid value, Collibra now converts the invalid value into an empty value, allowing you to delete this empty value, instead of returning an error. (ticket #92470)
  • If you assign a role to a user or user group for a domain or community from a table that has hierarchy enabled in Stewardship or from the Organization page of a community, the hierarchy no longer collapses. (ticket #85597)
  • You can once again filter on the Started by column on the Activities page. (ticket #93192, 93998)
  • A non-admin user now only has limited access to the user profile information of other users. (ticket #72348)
  • The Responsibility tab page of asset pages can now show all responsibilities. (ticket #65336, 73054, 76137)
  • You can now delete a community or domain if it contains assets which belong to a product for which you do not have the global permission.
  • Fixed an issue where the title was missing from the attribute dialog box when adding an attribute as a characteristic on an asset page. (ticket #94997)
  • Formatting changes involving removing all tags are no longer ignored and the field is updated accordingly when importing via the new import interface. (ticket #66457)
  • When importing from the new import interface backslash and quotes are no longer treated as literal parts of the asset. (tickets #87065, 91621)
  • When importing complex relations from the new import interface an error is shown regarding the attribute limit. (ticket #65375)
  • Acronym assets are no longer duplicated when created via the new import interface. (ticket #81329)
  • When importing assets or complex relations, testing the import no longer fails if the user interface language is not set to English. (ticket #91500)
  • The Output module once again returns responsibilities for non-administrator users if "Enable joins for view permission filtering" is enabled. (ticket #90057, 90829, 91185, 98429)
  • You will now be logged out if all your product right permissions are removed whilst you are using the Collibra Platform.

  • If you are logged in, you can now only trigger an API call to reset your own password, unless you are an admin in which case you can also reset another user's password. (ticket #93314)

Workflows

  • Cancelling a bulk task operation on the Tasks page no longer causes the task sidebar to show an error.

Edge

  • Fixed an issue where users received an authentication error when pulling docker images for Edge installations on EKS. (ticket #93637)
  • Fixed an issue where the randomly generated password for Edge installation was too short and caused the installer to fail.
  • A Null Pointer Exception (NPE) is no longer caused by excluding the optional timeout to the test connections Rest API.
  • Edge proxy configuration now accepts special bash characters, such as $, in both usernames and passwords. (ticket #93803, 95149)
  • Edge API now returns the error code 413 when attempting to upload a driver where the file is too large. (ticket #88160)
  • Fixed an issue where the Edge installer connectivity checks did not use the configured proxy. (ticket # 95901)
  • Fixed an issue where the back button on the Edge site Detail screen did not redirect users to the previous page.
  • You no longer see log levels for Edge capabilities which do not produce CDATA logs.
  • Fixed an issue in Edge where a failed job would be reported multiple times.

Search

  • The search time is now reduced, especially if your Collibra environment contains many communities and domains.
  • Search reindex using Output Module can now reindex assets that do not have a status. (ticket #89966)

(Undefined variable: CollibraProducts.Collibra4Desktop)

  • The descriptions of workflows on the Actions tab no longer contain HTML tags. (ticket #87653)
  • If an Acronym asset does not have a definition, the asset page of the Acronym asset now shows the relation to the linked Business Term asset. (ticket #94171, 95114)

Browser Extension

  • You can now search for assets using Collibra Browser Extension even if the CSRF token in Collibra Console is enabled.
  • You can no longer access Jolokia rest endpoints, this is to enhance the security of the platform.

API

  • Workflows configured via the API to start on 'user disabled' event now start properly when the user is disabled, not enabled. (ticket #87482)
  • The REST API calls to get assets, attributes, relations, complex relations, communities and domains now support cursor-based paging. This is an alternative to the current offset-based paging. The benefits of cursor-based paging are better performance and stable results when assets/characteristics are added while going through the pages.
  • The /assets API now works to find assets even if the excludeMeta parameter is set to false and no other parameters are set. (ticket #90832)
  • You can now retrieve all comments using a CSV endpoint with a TableViewConfig in the REST Core API Output Module resource. (ticket #89625)
  • The Given License Type parameter is now ignored by APIs that receive it as an argument. APIs that return Given License Type always use CONSUMER as the value.

Beta features

A public beta is an upcoming feature or product that is made available to all customers before it is fully ready for general availability so it can be tested and evaluated early. Learn more

Workflow Designer

  • You can now use the Workflow Designer to build and manage workflows. This is a powerful visual tool which provides drag and drop functionality and full control over the layout and behavior of workflow forms. The new Workflow Designer makes it easier for teams to work together to create and use new workflows to automate business processes.

Hotfixes

Collibra 2022.11.1

  • If the 'Settings landing enabled' setting in the Beta features section is not enabled, the Data Marketplace settings are no longer available in the Settings page. The new Settings landing page must be enabled to configure Data Marketplace settings.
  • Fixed possible database performance decrease right after restoring backups from older versions.
  • You can no longer edit the restriction on a system assignment line in the API.
  • To fix the Data Marketplace issue "Request failed with status code 503", Collibra no longer shows user avatars in the Responsibilities tab in asset previews. (ticket #101776, 102145)
  • Fixed an issue where some connections using JDBC drivers failed because they were not able to write to the Edge file system. (ticket #100482, 100925, 100949, 101007, 101232)
  • Fixed an issue where capabilities would fail to report data back to Collibra due to a timeout on an Edge site's proxy component. (ticket #99194)

Collibra 2022.11.2

  • To enhance the security of Collibra, two components for data classification via Edge have been upgraded to use a later version of Java (ticket #102575):
    • data_classification-dynamodb:1.20.0 now uses Java 8.342
    • data_classification-controller now uses azul/zulu-openjdk-alpine version 11.0.16.

Collibra 2022.11.3

  • Collibra can now connect to Collibra DQ if service mesh is enabled.

Collibra 2022.11.4

  • The hierarchy in a view containing assets from an S3 file system now works as expected. (ticket #96736)

Lineage harvester hotfix 1

  • The lineage harvester now correctly picks up the Looker <source ID> configuration file.

Catalog JDBC Profiling capability hotfix 1

  • Columns with unsupported data types are now excluded from profiling queries. The exclusion applies to columns mapped to following java.sql.Types: ARRAY, BINARY, BLOB, CLOB, DATALINK, DISTINCT, JAVA_OBJECT, LONGVARBINARY, NCLOB, NULL, OTHER, REF, REF_CURSOR, ROWID, SQLXML, STRUCT, VARBINARY. (ticket #100005)

Asset Recommender hotfix 1

  • The data source of Asset Recommender has been updated to provide more up-to-date and accurate recommendations.