Release 2024.02

• New look and feel (beta)

• This release includes the public beta for our new, refreshed Collibra experience. A completely redesigned look and feel is now applied across the platform. With improved color selection, layouts, visual separation and many other design elements, the platform is now more engaging and easier to use than ever. Additionally, many new features have been built upon this new look and feel, such as our Tailored asset pages, AI Governance, and many more.
  Learn more about the changes and features that come with the new look and feel and participate in this beta to get your hands on our new Collibra user interface.

  Important In the documentation, the new user interface is referred to as 'latest', and the previous user interface is referred to as the classic. You can find options to switch the information between the two available user interfaces.

• Collibra AI Governance (beta)

• Collibra AI Governance (beta) is now available! AI Governance offers a holistic end-to-end view of all your organization's AI projects, and is designed to help you with the following:

  • Improve your organizational access to, and adoption of, AI systems.
  • Promote visibility, productivity, compliance, and accountability around AI use cases.
  • Mitigate the data privacy, intellectual property, and ethical risks associated with AI.
  • Prevent the duplication of efforts in the development and adoption of AI systems.
  • Drive meaningful business evaluations of AI use cases prior to investing in them.
  • Provide cross-functional collaboration, to address the internal use of AI systems for common business functions.

  If you would like to participate in beta testing, please apply on the Collibra Beta Platform.

• Data Lineage
• You can now create technical lineage for SAP HANA Cloud/Advanced on Edge by adding an SAP HANA capability with the Use Hana Cloud option selected.

• Edge
• You can now use vaults to implement your management and rotation policies for your data source credentials and applicable connection properties used in your Edge site connections.
• Note Edge vaults is available only in the latest user interface (beta).

  The following vault providers can be integrated with your Edge sites:

  • CyberArk Vault
  • HashiCorp Vault
  • Azure Key Vault
  • AWS Secrets Manager
  • Google Secret Manager

  Vaults allow you to:

  • More easily manage your sensitive data source details. As they are stored in your vault, you only need to update, rotate, or delete the details from the vault rather than also within your Edge site.
  • Add your data source details to your Edge site connections. Rather than entering the details manually into each Edge site connection, you can enter your vault details which then pull these details into your connection.
    
    
• The Edge site system requirements have been updated for k3s or EKS.
  • K3s:
    • We no longer provide support for Edge sites installed before 2023.11 with a k3s version older than 1.27. You must reinstall your Edge site to upgrade to the latest Edge supported k3s version.
      Note While we do not anticipate this change to break existing Edge sites, support will be limited for troubleshooting Kubernetes versions that are no longer officially supported by the Kubernetes foundation. You will need to reinstall your Edge site to upgrade to the latest version of k3s before the 2024.02 release. For more information, go to the Edge Compatibility table.

      • You now only need to add one URL to your allow-list in order to connect Edge to Datadog. We have simplified our Datadog connectivity checks, so that only one URL end point needs to be added to your allow-list. With this change, the endpoint from Edge to Datadog is fixed, which means that you should not need to update this link every time Datadog releases a URL change. When you upgrade to Edge 2024.02, you must add one of the following URLs to your network allow-list:

        • Commercial - https://http-intake.logs.datadoghq.com:
        • Fedramp: https://http-intake.logs.ddog-gov.com
  • EKS:
    • We no longer provide support for Edge sites installed on an EKS version older than 1.27. You must upgrade your EKS version to 1.27.
      Note While we do not anticipate this change to break existing Edge sites, support will be limited for troubleshooting Kubernetes versions that are no longer officially supported by the Kubernetes foundation. Go to our Support site to follow the instructions on how to upgrade your Edge sites using EKS from EKS 1.24 and lower to EKS 1.27 before the 2024.02 release. For more information, go to the Edge Compatibility table.
    • We no longer require EBS volumes.

    • You now only need to add one URL to your allow-list in order to connect Edge to Datadog. We have simplified our Datadog connectivity checks, so that only one URL end point needs to be added to your allow-list. With this change, the endpoint from Edge to Datadog is fixed, which means that you should not need to update this link every time Datadog releases a URL change. When you upgrade to Edge 2024.02, you must add one of the following URLs to your network allow-list:

      • Commercial - https://http-intake.logs.datadoghq.com:
      • Fedramp: https://http-intake.logs.ddog-gov.com

• Metamodel changes
• The attribute "Owner in Source" is now by default assigned to Database, Schema, Table, and Database View assets.
• The attribute "Source Tags" is now by default assigned to Database and Schema assets.
• The attribute "Description" is now by default assigned to Dataplex Zone.
  The attribute "Description from source" is now by default assigned to Dataplex Zone and Dataplex Lake.
  A new out-of-the-box relation type has been added: Dataplex Zone contains / is part of Schema.
• With the release of CollibraAI Governance, the following out-of-the-box asset types are now available:
  • AI Model, UUID: 00000000-0000-0000-0000-000000031402
  • AI Use Case, UUID: 00000000-0000-0000-0000-000000031401
• We removed the unnecessary Backup Edit and View global permissions. (ticket #115651, 117376, 134024)
• As part of the migration process from the Java Core API v1 to v2, a number of v1 methods are now deprecated or removed.See what is changing

  Interface v1	Method v1	Change Removed: The method is no longer available and there is no replacement. Drop: The method is deprecated with no replacement and will be removed in the future. Convert: The method is deprecated and will be removed in the future, but there is a replacement available.	Interface v2	Method v2
  PrivateAssignmentComponent	getAssignedAttributeType	Removed
  TermComponent	addTerms	Removed
  TermComponent	getRootType	Removed
  TermComponent	getTermArticulationScore	Removed
  TermComponent	getTerms	Removed
  StatusComponent	getStatuses	Removed
  StatusComponent	removeStatus	Removed
  StatusComponent	updateStatus	Removed
  TermComponent	changeConceptType	Removed
  RepresentationComponent	changeConceptType	Removed
  RepresentationComponent	changeExcludedFromHyperlinking	Removed
  RepresentationComponent	findPossibleAttributeTypes	Removed
  RepresentationComponent	findPossibleAttributeOrRelationTypes	Removed
  RepresentationComponent	findPossibleStatuses	Removed
  RelationComponent	change	Removed
  RelationComponent	changeSourceTerm	Removed
  RelationComponent	changeTargetTerm	Removed
  RelationComponent	getRelationCount	Removed
  ConceptTypeComponent	addConceptTypeWithCustomUUID	Removed
  ConceptTypeComponent	changeSignifier	Removed
  ConceptTypeComponent	getConceptTypeHierarchy	Removed
  ConfigurationComponent	clear	Removed
  ConfigurationComponent	getString	Removed
  ConfigurationComponent	setProperty	Removed
  RelationTypeComponent	addRelationType	Removed
  RelationTypeComponent	addRelationTypeWithCustomUUID	Removed
  RelationTypeComponent	changeBinaryFactTypeWithExistingTerms	Removed
  RelationTypeComponent	findPossibleRelationTypesForSourceTerm	Removed
  RelationTypeComponent	findPossibleRelationTypesForSourceType	Removed
  RelationTypeComponent	findPossibleRelationTypesForTargetTerm	Removed
  RelationTypeComponent	findPossibleRelationTypesForTargetType	Removed
  RelationTypeComponent	findRelationTypesContainingRoleAndHeadOrTail	Removed
  RelationTypeComponent	findRelationTypesContainingRoleOrSignifier	Removed
  RelationTypeComponent	getRelationTypesContainingHeadTerm	Removed
  RelationTypeComponent	getRelationTypesContainingSourceTerm	Removed
  RelationTypeComponent	getRelationTypesContainingTailTerm	Removed
  RelationTypeComponent	getRelationTypesContainingTerm	Removed
  RelationTypeComponent	getSynonymRelationType	Removed
  ComplexRelationTypeComponent	addComplexRelationType	Removed
  ComplexRelationTypeComponent	addComplexRelationTypeWithCustomUUID	Removed
  ComplexRelationTypeComponent	changeComplexRelationType	Removed
  ComplexRelationTypeComponent	exportCSV	Removed
  ComplexRelationTypeComponent	exportCSVAsString	Removed
  ComplexRelationTypeComponent	exportExcel	Removed
  ComplexRelationTypeComponent	exportExcelWithoutJob	Removed
  ComplexRelationTypeComponent	remove	Removed
  RightsComponent	addRoleWithCustomUUID	Removed
  RightsComponent	changeMemberRole	Removed
  RightsComponent	findRolesContainingSignifier	Removed
  RightsComponent	getCurrentUserRights	Removed
  RightsComponent	getInheritedMembersByResourceAndRole	Removed
  RightsComponent	getMemberRoles	Removed
  RightsComponent	getMembersByOwnerAndRole	Removed
  RightsComponent	getRoles	Removed
  RightsComponent	isComplete	Removed
  RightsComponent	setPermissions	Removed
  UserComponent	addAdditionalEmail	Removed
  UserComponent	addGroup	Removed
  UserComponent	addUsers	Removed
  UserComponent	addUsersToGroup	Removed
  UserComponent	changeAdditionalEmail	Removed
  UserComponent	checkActivationCode	Removed
  UserComponent	getGroups	Removed
  UserComponent	getUsersCount	Removed
  UserComponent	isAuthenticatedSAMLUser	Removed
  UserComponent	removeAvatar	Removed
  UserComponent	removeGroup	Removed
  UserComponent	removeGroups	Removed
  UserComponent	requestReset	Removed
  UserComponent	sendEmailNotifications	Removed
  VocabularyComponent	change	Removed
  VocabularyComponent	changeCommunity	Removed
  VocabularyComponent	changeDescription	Removed
  VocabularyComponent	changeExcludedFromHyperlinking	Removed
  VocabularyComponent	changeName	Removed
  VocabularyComponent	changeNameAndUri	Removed
  VocabularyComponent	changeType	Removed
  VocabularyComponent	changeUri	Removed
  VocabularyComponent	findPossibleAttributeOrRelationTypes	Removed
  VocabularyComponent	findPossibleAttributeTypes	Removed
  VocabularyComponent	findPossibleComplexRelationTypes	Removed
  VocabularyComponent	findPossibleFactTypes	Removed
  VocabularyComponent	findPossibleObjectTypes	Removed
  VocabularyComponent	findPossibleRelationTypes	Removed
  VocabularyComponent	findPossibleStatuses	Removed
  VocabularyComponent	removeVocabulary	Removed

  For a complete list of changes that impact Java API v1 methods, see the Java API v1 to v2 mapping on the Developer Portal.

Data Governance

• There is a new asset type property 'lockStatuses'. When this property is set to true, Collibra will manage the lifecycle of assets of this type. This means you can not add your own statuses to the assignments of this asset type. It won’t be possible to create or update an asset of this type to have a different status than the ones listed on the assignment. For all existing asset types, the value of this new property was set to false, so you can still customize the list of statues the same way as before. Only on the newly introduced out-of-the-box asset type 'AI Use Case', will have an enabled status restriction.

  • There is another new asset type property 'finalType'. When this property is set to true, you cannot create subtypes of this asset type and you cannot create scoped assignments on this asset type. For all existing asset types, the value of this new property was set to false, so you can still extend the asset type the same way as before. Only on the newly introduced out-of-the-box asset type 'AI Use Case', will not be able to create subtypes and scoped assignments.

  • In this release, the value of these new properties can only be consulted via the API, but we plan to adjust the UI so you can show the value of these property in an upcoming release.

Assessments

• You can now choose to hide all out-of-the-box assessment templates for all users from the template gallery. This also hides the templates from the template drop-down list when conducting an assessment. To facilitate this feature, the "Show out of the box templates" setting has been added to Collibra Console and Collibra settings.

Edge

• The Google Dataplex Lineage synchronization via Edge setting in Services Configuration is added for the feature to be released in a future release.
• You can now use vaults to implement your management and rotation policies for your data source credentials and applicable connection properties used in your Edge site connections.
Note Edge vaults is available only in the latest user interface (beta).

Security

• You can now use a dedicated dgc/custom-dashboards folder to upload custom dashboards via the back up and restore process. This new folder is behind authentication and its contents are not available to users that are not signed in.

API

• To help you remove existing classification matches, the following endpoints of the Collibra Catalog Classification REST API now have a DELETE method available:
  • /dataClassification/classificationMatches/bulk
  • /dataClassification/classificationMatches/{classificationMatchId}

• To help you remove existing classification matches, the following classes and interfaces are now available for the Collibra Catalog Classification Java API:
  • DeleteClassificationMatchesRequest
  • DeleteClassificationMatchRequest
  • ClassificationMatchApi

Data Catalog

• We made several enhancements to the new data classification method:

  • You can create a classification rule with a list of more than 1,000 values. To do this, you must upload a file that contains the list of values with one value per line.
    Any list of values can now also be downloaded.
  • The maximum number of values for all the lists of values in one data class is now 25,000.
  • You now need the global permission Classification > Classify to start the automatic Unified Data Classification process.
  • The “Examples” field in the data class details now supports multiple examples. Each example needs to be added on a separate line.
  • When you import out-of-the-box data classes, we no longer select any classes by default.
• You can add up to 10 synchronization rules for a schema. (idea #2427)
• We have enhanced the Databricks Unity Catalog integration.
  • The following fields are now generally available in the Databricks Unity Catalog capability: "Filters and Domain Mapping" and "Extensible Properties Mapping".
  • In the "Extensible Properties Mapping" field in the Databricks Unity Catalog capability, we allow a new format where you can map views separately from tables. If you use format version 0.2 in this field, validation checks now run on both tables and views. (ticket #132723)
  • For Databricks Unity Catalog, we now support the integration of source tags in Database, Schema, Table, and Column assets. The tags are available in the "Source Tags" field. (idea #DCC-I-2495)
  • For Databricks Unity Catalog, we now support the integration of the owner in Database, Schema, and Table assets. The owner is available in the "Owner in Source" field. (idea #DCC-I-2562)
  • The following Databricks Unity Catalog fields can now also be integrated via the Extensible Properties Mapping (ticket #132712):
    • Table: table_type , securable_type, and securable_kind.
    • Schema: securable_type and securable_kind.
• To reduce the number of API calls during the S3 synchronization via Edge, the programmatic user for S3 now needs additional permissions.
  • glue:BatchGetCrawlers
  • glue:ListCrawlers

  Important If you created the programmatic user with an AWS managed policy: AWSGlueServiceRole, you don’t need to specify these permissions.

Data Lineage and BI integrations

• Optimized memory profile when harvesting database models during the integrating of JDBC data sources via Edge. This helps reduce the chances of Out Of Memory (OOM) errors. (ticket #130766)
• All supported BI tools now benefit from SQL extension v2:
  • The Collibra Data Lineage service instances can now successfully process more SQL queries. This results in a more complete lineage, including nodes that represent queries which previously could not be processed.
  • The source code is more intuitively grouped in the transformations table [link] and includes names, for example, “source code 1”, where previously names were “None”. Queries and their relevant assets are now combined into a single line in the transformations table. Because of this, the source code processed count in the Done column is reduced and the success rate might differ. The lineage itself is unchanged.
• Improved folder filtering for Looker integrations. The following improvements are applicable when filtering by folder ID.
  • Filtering is now carried out via the API, instead of on the Collibra Data Lineage service instances. This means that the lineage harvester accesses only the specified folders, and sends the metadata to the Collibra Data Lineage service instance for processing and ingestion in Data Catalog. Previously, metadata from all folders was sent to the Collibra Data Lineage service instance, where filtering was then carried out. This change greatly improves Looker integration flexibility, speed, and performance.
  • The log files now include more detailed information about the filter results.
• When integrating JDBC data sources via the lineage harvester, with the “Folder connection” method, you can now include the new "databaseSystemMapping" property in your configuration file, to map specific databases to specific systems, to obtain stitching. Previously, stitching was missing, as all databases were associated with the default system name provided in the "collibraSystemName" property.

Data Governance

• The import results summary now contains information about created or updated tags.

Data Marketplace

• If you are using Collibra Protect, you can now see the data access rules and standards applicable for tables and columns in the Data Marketplace asset preview. This will help users to set expectations before they launch an access request.
  An extra tab, Policies, is available in Data Set, Table, and Column asset previews. (idea #DCC-I-1980)

Workflows

• We have improved the logic of the workflow information purge mechanism.
• We have upgraded the Collibra workflow engine to use Jakarta EE instead of Javax EE. If you have workflows that use Javax EE javax.* functions, see Upgrading your scripts for Collibra 2024.02 compatibility on the Developer Portal for additional details.
• With the current release we are gradually adding more thorough checks for scripts used in workflows. You will not be able to deploy workflows with scripts that contain critical violations, while non-critical violations are going to be logged. If you encounter issues as a result of these checks, contact Collibra Support.

Workflow Designer

Note Workflow Designer enhancements become available with the upgrade of production environments.

• Trying to export an empty Workflow Designer app now displays an error message about missing a business process model.
• Trying to deploy an empty Workflow Designer app now displays an error message.

Edge

• We have updated our system requirements for Edge sites installed on k3s or EKS.
  • K3s:
    • We no longer provide support for Edge sites installed before 2023.11. You must reinstall your Edge site in order to update to the latest Edge supported version of k3s.

    • You now only need to add one URL to your allow-list in order to connect Edge to Datadog.

  • EKS:
    • We no longer provide support for Edge sites installed on an EKS versions older than 1.27. You must upgrade your EKS version to 1.27.
    • You no longer need EBS volumes.
    • You now only need to add one URL to your allow-list in order to connect Edge to Datadog.

Miscellaneous

• The Product Documentation link on the Help menu now directly opens the new Collibra Documentation Center instead of the Product Resource Center.

Data Catalog

• In a Configuration tab of a Database asset, for schemas with the status "Removed from Source", we no longer display the "Synchronize Schema" button and we now provide the option to remove the synchronization rules.
• In the Metadata Synchronization tab of the Configuration in a Database asset, we now correctly indicate if the list of schemas is empty. Before this change, the interface kept on loading.
• We increased the reliability of the database registration job status. (ticket #128092)
• When an environment stopped while a refresh of a list of schemas for a database was ongoing, the Configuration tab of the Database asset now loads properly after a restart. (ticket #116158)
• The Database Registration REST API now provides location headers in responses. (ticket #128782)
• The REST API now returns the classifications in a fixed order. This ensures that you don’t miss any classification or that you have any duplicates when pagination is needed. (ticket #124769)
• When a user creates a new data class via the new classification method, the correct user is logged as the creator and we display the correct creator name in the Data Classification page.
• You can no longer see data classes in the Data Classification page if you don't have the Classification > Data Classes > Read permission when using the new classification method.

Data Lineage and BI integrations

• The Power BI Data Mart asset type now has candidate as status when first ingested. (ticket #126870)
• The MicroStrategy Data Entity asset type now correctly has the BI Catalog domain type as the assigned domain in the global assignment.

Data Governance

• Previously, users were receiving an error when removing an assigned Data Quality rule from an asset type. This issue has been resolved from versions 2024.02 versions and lower. You can now remove a Data Quality rule assigned to an asset type without error.
• Searching for communities with applied filters is now working as expected for lower case, upper case, and camel case values. (ticket #127486)
• When you add attributes to a complex relation table, the attributes are now immediately visible after you save. This means that you don't have to refresh the page to see this new addition. (ticket #127278)
• When you delete a attribute type, relation type, complex relation type, domain type, status, articulation score rule, validation rule, or data quality rule that is part of an assignment, the last modification date and the user who last modified are now correctly updated on the assignment object. This information is not visible in the UI, but you can retrieve it via the assignment API.
• A new information message appears on the Articulation score rule assignment page. The new message is as follows: “Articulation scores are recalculated when an asset is edited. Changing the rule itself won’t trigger recalculation. The maximum articulation score is always 100.” The message better reflects the current business logic.
• We updated the description of the total field in the ActivityPagedResponse object to explain it returns a constant value rather than the actual amount of activities in the system, because of performance reasons.
• We marked the field countLimit as deprecated on the Java FindActivitiesRequest object. We also marked the field countLimit as deprecated as an input parameter on the REST GET /activities API. We marked the fields total, offset, and limit as deprecated in the response object ActivitiesPagedResult, that is returned by the REST API call GET /activities. This was done in order to align the REST API documentation with the deprecation notice that was already added on the Java API documentation for the PagedResponse<T> class.
• Previously, when trying to create a domain via the Global Create pop-up, communities with a Meta=true flag were not filtered out of the community drop down options. This issue has been resolved. Meta=true communities are not shown.
• We have fixed an issue where a limited set of asset type icons were displayed as a Warning in the top-navigation search bar and in other pages. (ticket #128354)
• Co-roles for relations are now shown for complex relations in Data Quality.
• The articulation score has been recalculated and optimized to improve performance.
• We have fixed an issue of Data Quality results in the Quality tab displaying incorrectly. The Data Quality metrics have been updated. (ticket #125271)
• We have optimized the validation job for TermImpl entities so there is no unnecessary fetching of asset entities.
• Assets without any assigned validation script that are submitted for validation do not trigger database requests to create asset models.
• You can again import tags and relations simultaneously. (ticket #130625)
• Importing a file with an empty column no longer causes the import wizard to incorrectly map column values.
• We have fixed an issue where, during antivirus scanning of a new file upload, NIST logging files were taking an excessive amount of time to scan. (ticket #127574)

Data Marketplace

• We no longer display the "Add to Data Basket" button twice, if you don't use Catalog experience. (ticket #129392, 130519)
• To search for a URL, you can now use "" quotes, for example "collibra.com/documentation". When you use quotes. the number of / in the URL does not impact your search results. (ticket #123952)
• If you use a special character in a search query with quotes, for example "customer data [", we no longer show an error message.

Assessments

• If you have the Assessments Admin global role, you can now also view private assessments and edit the permissions of any assessment. (ticket #130919)

Protect

• Protect now correctly reads its scheduler fixed delay configuration for Console-based deployments.

Workflow Designer

Note Workflow Designer fixes become available with the upgrade of production environments.

• The Event-based gateway component is now part of the Gateways section in the Workflow Designer Shape repository.
• Signing out of the Workflow Designer no longer causes an internal server error. (ticket #130670)

Edge

• We fixed an issue that prevented the configuration of JDBC connections that have the `OAuthSettingsLocation` property defined from working correctly.

Search

• In the search results, terms that match your search text are again highlighted. (ticket #123870)

Browser Extension

• Legacy icons are now shown in Collibra Browser Extension 1.4.1. (ticket #132966)

Collibra Console

• We have improved the logic of retrieving the status of a backup operation.
• Usage Analytics no longer prevents some restored environments from starting. (ticket #130475)
• We have removed inaccurate metrics from the Collibra Console Monitoring tab. (ticket #127243)
• Signing in to Collibra Console no longer takes an unusual amount of time in some cases. (ticket #115370)

Security

• Not agreeing to the disclaimer when both the frontend (shell) and the Homepage are enabled now redirects you immediately to the sign-in page.
• The password reset form now uses version 2 of the Collibra Core REST API.

Miscellaneous

• We have improved the security of Jobserver.
• In a view for which you have enabled the hierarchy, if one or more relation types in the hierarchy are deleted, the view no longer crashes, and you can now create the hierarchy view using the available relation types. (ticket #114508)
• Upgrading from Collibra version 5.9.1 to Collibra Platform Self-Hosted when the installation directory and collibra_data directory are on different partitions no longer fails.

Beta features

New look and feel

This release includes the public beta for our new, refreshed Collibra experience. A completely redesigned look and feel is now applied across the platform. With improved color selection, layouts, visual separation and many other design elements, the platform is now more engaging and easier to use than ever. Additionally, many new features have been built upon this new look and feel, such as our Tailored asset pages, AI Governance, and many more.
Learn more about the changes and features that come with the new look and feel and participate in this beta to get your hands on our new Collibra user interface.

Important In the documentation, the new user interface is referred to as 'latest', and the previous user interface is referred to as the classic. You can find options to switch the information between the two available user interfaces.

AI Governance

Collibra AI Governance is now available! AI Governance offers a holistic end-to-end view of all your organization's AI projects, and is designed to help you with the following:

• Improve your organizational access to, and adoption of, AI systems.
• Promote visibility, productivity, compliance and accountability around AI use cases.
• Mitigate the data privacy, intellectual property and ethical risks associated with AI.
• Prevent the duplication of efforts in the development and adoption of AI systems.
• Drive meaningful business evaluations of AI use cases prior to investing in them.
• Provide cross-functional collaboration, to address the internal use of AI systems for common business functions.

If you would like to participate , please reach out to your Customer Success Manager, for more information and access to the Collibra Beta Platform.

Data Marketplace: Data Similarity

• You can now define the data similarity threshold. The threshold is the similarity score from which a Table is considered as similar data.

Data Lineage

• Collibra Data Lineage support for Databricks Unity Catalog is now available in beta testing. You can create technical lineage for Databricks Unity Catalog by using technical lineage via Edge.
• When integrating Power BI, you can now enable DAX parsing (in beta), to allow for column-level lineage of calculated columns and measures. (idea #265)

Knowledge Graph API

• The response returned by the Knowledge Graph API no longer contains an additional "extensions" field.
• In case of a timeout error, the Knowledge Graph API error message now mentions the cause of the error.

Collibra 2024.02.1

• Data Similarity for Table assets in Data Marketplace is now generally available and enabled by default for Cloud environments, except for Public sector. This feature allows you to see similar Table assets inside of a Table asset preview. This will help your data analysts to navigate the data landscape and find alternative data, and will therefore reduce their time to value.
  If the Data Similarity feature is enabled, extra AI algorithms, which use privacy enhancing technologies, will run during data profiling. These algorithms detect similar data across all data sources that you have profiled after this feature was enabled.
  With 2024.02, you can also define the data similarity threshold. The threshold is the similarity score from which a Table is considered as similar data.
• Signing in with SSO and SAML no longer prevents you from accessing your Collibra environment. (ticket #136309, 136311, 136312, 136317, 136319, 136323, 136329, 136330, 136331, 136335, 136344, 136346, 136349, 136355, 136356, 136358, 36363, 136369, 136382, 136385, 136386, 136388, 136389, 136396, 136405)
• Session timeouts no longer prevent very long running jobs from finishing.
• If you have multiple databases for the same data source, the data protection standards or data access rules no longer fail during the synchronization. (ticket #134881)

Collibra 2024.02.2

• Redeploying a workflow with a sub-process when a user task of the sub-process is still active no longer prevents you from completing the user task. (ticket #134284, 137412)
• The Edge Site role is now by default assigned the View Permission - View All permission.

Collibra 2024.02.3

• We made some performance improvements related to assignments, which impacted asset pages load times. (ticket #138695, 138397)
• You can once again use attributes with True/False values in the filter of Bar Chart widgets. (ticket #137637, 138206, 138578, 138875, 139335)

Collibra 2024.02.4

• Collibra data entry asset components that retrieve more than 1,000 proposed values in a workflow task no longer cause an error. (ticket #136622, 137219)

Collibra 2024.02.5

• Relation reindexing now continues even if the confirmation response times out during the indexing request. (ticket #138154)

Collibra 2024.02.6

• Responding to workflow action emails works again as expected. (ticket #139637)
• The performance of relational indexing is now improved significantly. (ticket #138154)
• An API request to modify a resource locks again that resource, preventing other API requests from modifying the same resource while the request is under way. (ticket #139836)

Collibra 2024.02.7

• We fixed an issue that blocked upgrades from Collibra 5.9.1 on separate partitions to CPSH 2024.02. (ticket #138783, 142212)