Release 2023.08

• Release information
• Highlights
• New features
• Enhancements
• Fixes
• Features in preview
• Collibra maintenance updates
• Edge updates

Release information

• Publication dates:
  • Release notes: July 20, 2023
  • Documentation Center: August 3, 2023
•  Release date of Collibra 2023.08.0: August 6, 2023
  • Upgrade non-production environments: August 6, 2023
  • Upgrade production environments: August 27, 2023
  • Upgrade GovCloud environments: Approximately end of September. Please check with your Customer Success Manager for more information.
• Release date of Collibra 2023.08.1: August 27, 2023
• Release date of Collibra 2023.08.2: On demand only
• Release date of Edge 2023.08.1: August 20, 2023
• Release date of Edge 2023.08.2: September 10, 2023
• Release date of Edge 2023.08.3: October 1, 2023
• Release date of Edge 2023.08.4: October 8, 2023
• Release date of Edge 2023.08.5: October 15, 2023
• Release date of Edge 2023.08.6: October 22, 2023
• Release date of Edge 2023.08.7: October 29, 2023
• Release date of Edge 2023.08.8: November 5, 2023
• Relevant Jobserver version: 2023.08.0-28

Highlights

• Metamodel changes
• The out-of-the-box global assignment of Database and Schema asset types has been updated with attribute type 'Description from source system'. This allows for the Databricks Unity Catalog integration to display the description from the source in Database and Schema assets.
  
• A new Power BI Data Mart asset type helps you integrate more accurately Power BI datamart metadata in Collibra.
• Two new Import and Export global roles and global permissions allow you to manage who can import or export data. Collibra users that don't have a role with the Import or Export permissions do not have the option to import or export assets and complex relations. (Idea #DGCPLAT-I-494)
  
• 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
  I18nComponent	setTranslationOverrides	Removed
  UserComponent	isGuestAccessAllowed	Drop
  ComplexRelationComponent	getComplexRelationCount	Removed
  ComplexRelationComponent	getInvolvedComplexRelationTypes	Removed
  ComplexRelationComponent	createComplexRelationFilter	Removed
  LicenseComponent	getActiveAPIUsers	Drop
  LicenseComponent	getActiveAPIUsersCount	Drop
  LicenseComponent	getActiveReadUsers	Drop
  LicenseComponent	getActiveReadUsersCount	Drop
  LicenseComponent	getActiveUsers	Drop
  LicenseComponent	getActiveWriteUsers	Drop
  LicenseComponent	getActiveWriteUsersCount	Drop
  LicenseComponent	getDaysBeforeExpiration	Drop
  LicenseComponent	getExpirationDate	Drop
  LicenseComponent	getMaxAPIUserCount	Drop
  LicenseComponent	getMaxReadUserCount	Drop
  LicenseComponent	getMaxWriteUserCount	Drop
  LicenseComponent	getNumberOfAPIUsers	Drop
  LicenseComponent	getNumberOfActiveSessions	Drop
  LicenseComponent	getNumberOfReadUsers	Drop
  LicenseComponent	getNumberOfWriteUsers	Drop
  LicenseComponent	hasProduct	Drop
  LicenseComponent	hasValidLicense	Drop
  LicenseComponent	isExpired	Drop
  LicenseComponent	isGuestAccessAllowed	Drop
  LicenseComponent	updateLicenseUsage	Drop
  WorkflowComponent	getAllTasksForUser	Removed
  HyperlinkComponent	findManuallyLinkedTerms	Removed
  HyperlinkComponent	findAutomaticallyLinkedTerms	Removed
  HyperlinkComponent	findLinkedTerms	Removed
  CommunityComponent	getCommunities	Removed
  AttributeComponent	getNumericAttribute	Removed
  MappingComponent	findMapping	Removed

• Data Catalog
• Required JDBC driver updates:
  • Due to Snowflake JDBC driver changes introduced in version 3.13.19 and 3.13.22, we have updated the Snowflake meta data synchronization process. If you are using a driver older than 3.13.22, make sure to update the driver in your Edge connection to version 3.13.22 or higher. (ticket #102862)
  • If you are using a CDATA driver older than 21.0.7970 (released on October 2021) on Edge for metadata synchronization and profiling, you must update the driver to a higher version to be compatible with Java 17.
• In an effort to reduce the overall duration of the profiling activity, we have made several changes:
  • The database profiling via Edge now allows to profile multiple schemas at the same time. By default, four schemas are processed in parallel. You can configure the parallel profiling process via the new setting "Parallel schema profiling via Edge". As a consequence, the "Parallel database profiling via Edge" setting has been removed.
    Note that running multiple schemas also means that your database can be queried multiple times.
  • You can define the scope of the profiling via Edge by including or excluding tables based on Name or Type. This allows you to register all data metadata and only profile high-priority tables. Note that your Edge version must be upgraded as well.(Idea #DCC-I-1347, DCC-I-118)

• Data Governance
• The new import wizard is now enabled by default. The improved import wizard uses version 2 of the Import API for better performance, with a refreshed interface and more intuitive mapping. To switch this feature off, contact Collibra Support.
• You can now manage who can import or export data with two new Import and Export global roles and global permissions. Collibra users that don't have a role with the Import or Export permissions do not have the option to import or export assets and complex relations. (Idea #DGCPLAT-I-494)
  

• Data Lineage
• The new MicroStrategy integration method, via the lineage harvester, is now generally available. The new integration method has the following benefits:
  • Supports technical lineage with stitching
  • Supports the latest MicroStrategy APIs.
  • Supports project filtering.
  • Allows you to view the source code for all tables and transformations.
• Power BI integration via the Power BI harvester will reach end-of-life on August 1, 2023. If necessary, migrate to Power BI via the lineage harvester or via Edge, by August 1.
• With the optimization of Collibra Data Lineage for Informatica PowerCenter, it is now four times faster to create technical lineage for Informatica PowerCenter.

• Edge

• You can now control when your Edge site is upgraded with the new Manual upgrade mode. This feature is available for new and existing Edge installations starting from the 2023.08 version. If enabled, your Edge site alerts you when an upgrade is available and if the upgrade is required. Edge sites that require an upgrade will be in read-only mode until the upgrade has been successfully completed. Additionally, with Manual upgrade you can:

  • Retrieve a software bill of materials to review and perform security evaluations on the images included in a new Edge site version.
  • Setup your own custom repository that can pull from and mirror the Edge repository in the Cloud to scan images from available version upgrades.
  • We no longer provide support for Edge sites installed before 2022.08 with k3s 1.20. If your Edge site is impacted, you will be notified on the relevant Edge site pages. These Edge sites may continue to work, but will be at risk for incompatibility issues and bugs. We recommend reinstalling your Edge site to the latest Edge site version, which includes the latest Edge supported Kubernetes version.

• API

• As part of our preview program, Collibra is launching the Knowledge Graph API, a new GraphQL API, which simplifies the retrieval of Knowledge Graph data, including communities, domains, assets, and complex relations, in a synchronous manner.

  With the adoption of GraphQL, an industry standard language for querying data, integrating data retrieval into applications becomes much easier, resulting in faster integration and reduced development time.

  While the new API is a better alternative to the current REST Core APIv2 Assets resource, which requires making multiple calls to different endpoints, and the Output Module resource, which is based on a custom query language, the Knowledge Graph API is not intended to replace existing REST APIs. There are specific use cases where the Output Module may still be the preferred choice due to its support for certain types and sizes of data.

• For your security, you can allow or block GraphQL introspection through a new configuration option: "Enable schema introspection for public GraphQL APIs".

• Workflow Designer

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

• The Workflow Designer is now generally available on two GCP clouds: GCP US East 1 and GCP EU West 1! You can use the Workflow Designer to build and manage workflows. This is a powerful visual tool that provides drag and drop functionality and full control over the layout and behavior of workflow forms. The Workflow Designer makes it easier for teams to work together to create and use new workflows that allow you to automate business processes. Workflow Designer contains more than 20 ideas supported by over a 100 organizations. (Idea #DGCPLAT-I-162, DGCPLAT-I-674, DGCPLAT-I-586, DP-I-12, DCC-I-1196)

New features

Data Catalog

• Database profiling via Edge now allows you to profile multiple schemas at the same time, which reduces the overall duration of the profiling activity. By default, four schemas are processed in parallel. You can configure the parallel profiling process via the new setting "Parallel schema profiling via Edge". As a consequence, the "Parallel database profiling via Edge" setting has been removed.
  

  Note Running multiple schemas also mean that your database can be queried multiple times.

• The configuration of database profiling via Edge allows you to include or exclude tables based on Name or Type. This allows you to register all data metadata and only profile high-priority tables. (Idea #DCC-I-1347, DCC-I-118)
• You can now define the maximum duration of a profiling job via Edge.

• By default, profiling results processed via Edge are anonymized for columns of data type Text and Geo. To make sure that sensitive data is anonymized, an administrator can now decide to anonymize the profiling results for all columns.

Data Lineage and BI integrations

Note Data Lineage is a cloud-only feature.

• The new MicroStrategy integration method, via the lineage harvester, is now generally available. The new integration method has the following benefits:
  • Supports technical lineage with stitching
  • Supports the latest MicroStrategy APIs.
  • Supports project filtering.
  • Allows you to view the source code for all tables and transformations.
• The Tableau hostname mapping feature is now generally available. When integrating Tableau, you can use the optional “hostnameMapping” section in your <source ID> configuration file, to map Tableau technical database, server and schema names to the respective real names, to preserve stitching.
• CollibraData Lineage support for creating technical lineage for Azure Data Factory via Edge is now generally available.

Edge

• You can now control when your Edge site is upgraded with the new Manual upgrade mode. This feature is available for new and existing Edge installations starting from the 2023.08 version. Additionally, with Manual upgrade you can:
  • Retrieve a software bill of materials to review and perform security evaluations on the images included in a new Edge site version.
  • Setup your own custom repository that can pull from and mirror the Edge repository in the Cloud to scan images from available version upgrades.

Collibra Console

• You can now allow or block GraphQL introspection through a new security configuration option: "Enable schema introspection for public GraphQL APIs".

Enhancements

Data Catalog

• Due to Snowflake JDBC driver changes introduced in version 3.13.19 and 3.13.22, we have updated the Snowflake meta data synchronization process. If you are using a driver older than 3.13.22, make sure to update the driver in your Edge connection to version 3.13.22 or higher. (ticket #102862)
• If you are using a CDATA driver older than 21.0.7970 (released on October 2021) on Edge for metadata synchronization and profiling, you must update the driver to a higher version to be compatible with Java 17.
• When registering a database via Edge, you can now select assets with a child asset type of System. Previously, this resulted in an error. (ticket #94964, 108449)
• You can now start the Request Assets Access workflow for reports and data sets with inherited groups assigned as the Owner. You can download the latest version of the out-of-the-box workflows from the Resource Center. (ticket #107024)
• The S3 integration is now available via the "Register a data source" link in the "Register with Edge" section of the Catalog "Create" dialog box.
  See what this looks like

  
  

• When you create a capability for an S3 integration, you can now define how you want to handle assets that are removed from the S3 data source. By default, such assets get the status 'Missing from source' in Collibra. You can now define whether you want to ignore those assets or delete them in Collibra. (ticket #111295)
• If you move Table and Column assets that were integrated from Databricks to another domain and you run the integration again, we now recognize the originally integrated assets and move them back to their initial domain. If you would want to move assets to another domain permanently, you need to update the existing synchronization configuration or create a new capability that integrates the data in the new location.
• You can now integrate an AWS EC2 instance that is configured with role based authentication via Edge. If you create an AWS connection via Edge, you now see the “Authentication type” drop-down list with the options “EC2” or “IAM”. (Idea #DCC-I-1500)

Data Lineage and BI integrations

Note Data Lineage is a cloud-only feature.

• The relation type “BI Folder contains / contained in Data Asset” (UUID: 00000000-0000-0000-0000-120000000014) is now available between all Tableau Data Model and Tableau Project assets.
• When integrating MicroStrategy via the new integration method:
  • You can now view the source code for all tables and transformations, in the technical lineage Sources tab page. The source code shows information about the processes visible in the technical lineage and shows warnings and errors where a process has failed. This enhancement does not affect the success rate of metadata analysis.
  • The Source Type attribute is now included on MicroStrategy Data Entity and Data Attribute asset pages, to identify the MicroStrategy data object type, for example Attribute, Fact, Table, or Column.
• The Power BI and MicroStrategy global assignments are updated to show more details on respective asset pages.
• When you integrate Tableau:
  • Tableau Dashboard, Worksheet and Workbook asset pages now show the number of views in the Visits count attribute type.
  • The Tableau API analysis documentation is updated with the visits count.
• When integrating Power BI, datamart metadata is now ingested in Collibra as assets of the new asset type Power BI Data Mart.
• Collibra Data Lineage now supports the following Power Query M functions:
  • AnalysisServices.Databases
  • AnalysisServices.Database
    
    Note  

    • This function is fully supported if no MDX queries are used.
    • If MDX queries are used and they resemble SQL, they will be parsed by the SQL parser.
    • We don't currently support this function if used with MDX queries that resemble DAX, as the Collibra Data Lineage service instances can't parse such queries.
• When ingesting Snowflake data sources, the Collibra Data Lineage service instances now support LEVEL and CONNECT BY keywords. (ticket #115393)
• When ingesting PostgreSQL data sources, the Collibra Data Lineage service instances now support "x::typename" cast constructs, where "typename" contains a dot (.), for example "SELECT 'null'::qwerty.qwerty". (ticket #116821)
• Previously, when creating technical lineage for SQL Server Integration Services, Collibra Data Lineage filtered out some queries due to legacy limitations. Collibra Data Lineage no longer filters out queries. You may find increased successful lineage as well as increased parsing or analysis errors, as Collibra Data Lineage tries to parse more queries. This is a backend change, and the new behavior will be seen during the next synchronization of the technical lineage for SQL Server Integration Services.
• Collibra Data Lineage now processes and generates technical lineage for Informatica PowerCenter four times faster with the following changes:
  • Data Lineage now pre-processes data into pydantic models instead of using the slower xpath solution that existed previously.
  • Shortcuts are handled faster, by keeping necessary objects in memory on the Collibra Data Lineage service instances.
  • The Analysis Error messages are enhanced by adding information that is related to rejected files and unresolved parameters.
• Collibra Data Lineage now provides improved processing for sequence jobs, enhancing the technical lineage for DataStage.
• The new analyzeTemporaryTables property is added to the Snowflake SQL-API source ID file. With this property, you can decide whether Collibra Data Lineage should analyze the CREATE TEMPORARY TABLE statement.

Data Governance

• The new import wizard is now enabled by default. To switch this feature off, contact Collibra Support.
• The import wizard now defaults the asset type to Business Asset or a calculated value if the asset type or the asset ID are not mapped. (Idea #DCC-I-1825)
• You can now map the asset type when importing complex relations. This allows you to create new assets during a complex relations import.
• You can now tailor the notifications you get, with five additional notification preference options added to your profile. (ticket #115127)
• You can now search for all email addresses in comments without having to consider casing. (ticket #116444)

Data Marketplace

• The Data Marketplace search now allows for brackets (), [], {}. We also reviewed and optimized the search error messages to create more transparency for you.
• The look and feel of multi-select attributes in Data Marketplace asset previews has been updated.
• To align Data Marketplace and Catalog, we now sort columns by column position in the "Columns" tab of a Table asset preview. In other tabs ("Details") and in Data Set assets, columns are sorted alphabetically.
• When you delete a custom relation index, we start the relation reindexing instead of the full reindexing.
• In asset previews that show a table of columns or report attributes, we now also show the Description of the columns or attributes.
• When you create a custom relation index, you can now add other attribute types than text to your relation index path. The newly supported attribute types are Selection, Multiple Selection, Numbers, and Boolean (True/False). The attribute types Date and Script are still not supported.
  

  Note If the attribute type included in the relation index has a cardinality higher than 1, we only show the first alphabetically sorted occurrence of the attribute as a filter option in the Data Marketplace Filters pane. This limitation applies to Selection, Multiple Selection, Numbers, and Text.

Edge

• We no longer provide support for Edge sites installed before 2022.08 with k3s 1.20. If your Edge site is impacted, you will be notified on the relevant Edge site pages. These Edge sites may continue to work, but will be at risk for incompatibility issues and bugs. We recommend reinstalling your Edge site to the latest Edge site version, which includes the latest Edge supported Kubernetes version.
• A diagnostics file is now automatically generated if an Edge installation fails. To access the file, follow the file path found in the installation log Creating diagnostics file, in the following format: Create /path/to/diagnostics/<diagnostics_file>.tgz.
• An Edge Service Account, which is used by an Edge site to communicate with Collibra Platform, has now increased password security. The default password length is now 40 characters, unless the password length is defined otherwise in Collibra Console.
  • If, in Collibra Console, the minimum password length is greater than 40, the Edge Service Account's password length will be set to that minimum length. For example, if the minimum password length is 45, then the Edge Service Account's password length will be 45.
  • If, in Collibra Console, the maximum password length is smaller than 40, the Edge Service Account's password length will be set to that maximum length. For example, if the maximum password length is 32, then the Edge Service Account's password length will be 32.
  • In all other cases, the Edge Service Account's password length will be 40.

Search

• Search relevance is now improved by allowing search results that contain special characters and prioritizing search results that match the search keywords. This includes improved matching of URLs, matching with CamelCase and with words linked by underscores, as well as, improved ranking of partial matches.
• Indexing is now performed asynchronously, and as a result, the "Asynchronous indexing" field is removed from the configuration settings.

Fixes

Data Catalog

• If you were using the Snowflake 13.3.13 driver version or older to profile columns of type TIMESTAMPTZ in Snowflake, you need to upgrade to at least version 3.13.22 for profiling to work correctly. (ticket #104898, 112896)
• The "Privacy Context" section, introduced in 2023.05, has been renamed to "Categorization". (Idea PE-I-1400)
  See what this looks like

  
  

• Modifications to Jobserver driver configuration properties that are already used by ingested schemas, no longer cause an error when opening the "Refresh Schema" dialog for a schema. (ticket #110125, 113195)
• The error message displayed when we cannot get a list of databases or schemas now shows the correct Edge job ID. (ticket #105407)
• The database synchronization via Edge no longer runs indefinitely if it contains a schema with the status "Removed from Source". (ticket #117090, 117356, 119213)
• The database registration via Edge now synchronizes the descriptions for tables and columns from Microsoft SQL server data sources. Before, these descriptions were not synchronized. (ticket #111287, 112765)
• We now synchronize the Snowflake Tags via Edge in Schema assets, even if the Schema doesn't contain tables.
• We now synchronize Snowflake Tags via Edge for tables created with lower case characters in the table name. (ticket #118665)
• If you create a synchronization schedule, you can only schedule on the hour, from the available hours. For example, you can add a synchronization schedule at 8, but not at 8:45. If you try to add it at 8:45, we will default it to 8. (ticket #114153)
  If you don't want to schedule on the hour, you can use a cron expression.
• Regional settings now impact the profiling charts. This has an impact on, for example, date formats. (ticket #117075)
• The Databricks Unity Catalog Metadata integration now supports the ingestion of the STREAMING_TABLE tables in addition to EXTERNAL, VIEW, MANAGED tables. (ticket #118679)

Data Lineage and BI integrations

Note Data Lineage is a cloud-only feature.

• When integrating MicroStrategy, you can now use the optional "microStrategyLibraryUrl" property in your configuration file, if you need to specify a custom URL for your MicroStrategy Library.
• Fixed Datastage lineage harvester bug where table-level lineage wasn't being generated appropriately if Collibra Data Lineage did not have column-level information. Now, you can see more lineage in the Objects view where appropriate. (ticket #117233)
• Previously, data objects would be put into incorrect schemas, so they wouldn't stitch, and the technical lineage graph would stop where there should be more lineage. After this bug fix, stitching is improved and technical lineage is shown in full. (ticket #120439)
• Technical lineage for PowerCenter now includes an ANALYZE_ERROR called CONFIGURATION if there are undefined connection values in the source_id.conf file if you use the lineage harvester or the Source Configuration field in the technical lineage for Informatica PowerCenter capability on Edge.

Data Governance

• Fixed an issue where validation rules with a backslash in the name weren't executed correctly.
• You will be notified on Collibra Platform (CDIC) if a restore is unsuccessful and informed that you can't start CDIC until a successful restore is applied.
• Fixed a performance issue when removing a single responsibility from a group with more than 50k users. (ticket #104366)
• You can now unassign a group that has up to 100k users from any global role.
• If you disable a user account, they will now be logged out and no longer able to access Collibra. (Idea #DCC-I-1665) (ticket #109162)
• We have fixed an issue that, in specific circumstances, made assets disappear from search after Tableau ingestion. (ticket #110002)
• All action buttons, more buttons, pop-over icons buttons, and other buttons with drop-down options now work as expected, by opening on the first click and closing on the second click. (ticket #109814)
• When adding a characteristic on an asset page you can now search all characteristics, even if they are not shown in the initial 300 displayed options. (ticket #112406)
• Switching off the Detailed Relation Export Format configuration option no longer causes incorrect relation column headers in the exported file. (ticket #118302, 118366)
• You can again correctly import complex relations. (ticket #117465, 117888, 118366, 119350, 119424)

• You will now see the correct message depending on whether the asset type has subtypes with inherited assignments or not. (ticket #104922)

• Migration report links for attribute types and complex relation types now point to respective list views in the operating model.

• You will no longer see asset types in the suggestion tab of the Global Create for domains where that asset type can't be added.

• Scoped assignments are now properly taken into account in filters and column picker for Domain Asset Table

• You can once again upload a new license file through Collibra Console without getting an error from EdgeBootstrap. (ticket #85999, 95969, 110232, 114938, 115018, 115108)

• Improved permission checking on the asset types shown in Global Create for users with System Administration permissions.

Data Marketplace

• A link in an asset description to another asset now opens the correct page instead of a dashboard.
• Filter names can no longer contain the characters [, ], and >.

  Note If you have created relation indexes with these characters in their name, we will replace them with a - during the upgrade. For example, "hello>world" will change to "hello-world". If this change results in a duplicate filter name, the name won't be updated. We recommend you to verify the filter names after the upgrade.

Diagrams

• When the loading time for a diagram exceeds the backend limit, a notification is now shown to indicate that the diagram could not be loaded.

Workflows

• Workflows that start when a user is added, no longer prevent the creation of new SSO users when the start event is asynchronous. (ticket #115184, 117201, 117202, 117209, 117337, 117422, 117568, 117689, 117813)
• You can again deploy workflows that you could previously deploy in 2023.04 or older but not in 2023.05, 2023.06, or 2023.07. (ticket #114720)
• If you have multiple pages in your list of workflows and you delete a workflow on any page other than the first, you now remain on the page from which you deleted the workflow, instead of being returned to the first page.
  Also, if your pagination is set to show more than 50 workflows per page and you delete a workflow on any page other than the first, you now remain on the page from which you deleted the workflow. Previously, the system would return you to the first page and reset the number of workflows per page to 50. (ticket #108747)

Edge

• We have improved the security of Edge.
• The diagnostics script can now run regardless of whether the remote script is available or not. If the remote script is unavailable, the local script runs instead.

Search

• Assets from the Metamodel Community are no longer shown in any search results. (ticket #110259)
• The count of results of a search filter in the left pane now matches the count of results returned. (ticket #113832)

Collibra Console

• In the email configuration settings of Collibra Console, the host, port, and email fields are now required.
• For descriptions of backups and backup schedules, we now remove dangerous HTML content (for example <script> tags). For user names, backups, backup schedules, environments, nodes, repo clusters, and diagnostics files, the following special characters are not allowed: <>:"/\|?*$'&. (ticket #114107, #116646)
• Any non-basic characters ("[^a-zA-Z0-9-_.]",) in file names will be replaced by an underscore ( _ ) when the file is either uploaded as a backup or downloaded. (ticket #115045)
• We have updated Swagger specs to support direct API calls to Collibra Console APIs, and no longer require a cookie to be present, as a part of the implementation of Spring CSRF. (ticket #117023)

Miscellaneous

• The global views for Data Sources now load properly when the Data Classification column is enabled. (ticket #117424)
• The page titles of the Homepage and landing pages of Usage Analytics and Data Marketplace now show Data Intelligence Cloud instead of Data Governance Center. (Idea #DCC-I-1614)

Collibra maintenance updates

Collibra 2023.08.1

• Fixed a Remote Code Execution vulnerability in workflows.
• Existing custom Import or Export global roles are renamed "Import - renamed for 2023.08" and "Export - renamed for 2023.08" to accommodate the introduction of new Collibra out-of-the-box roles with the same name.
• Migrating from Jobserver to Edge no longer duplicates the migrated data. (ticket #122099)
• Restoring a backup as a user with the ADMIN role in Collibra Console no longer causes an unauthorized exception error. (ticket #121841, 122098, 122105, 122139, 122172, 122188, 122209, 122212, 122216, 122228, 122263, 122294, 122329, 122332, 122348, 122393, 122413, 122421, 122422, 122430, 122441, 122458, 122479, 122487, 122517, 122555, 122557, 122609, 122630, 122636, 122652, 122661, 122716, 122798, 122830, 122932)

Collibra 2023.08.2

• We have improved the security of our authentication, authorization, cryptography, and session management.