Release Notes v. 3.0.0

May 2023 - v. 3.0.0.0

System Enhancements

Clone Content Sources and Connections

New features have been added to our platform, allowing users to easily clone any content source and connect via the UI without having to recreate each source from scratch.

This saves time and effort, making it easier to manage and maintain content sources.
With this update, users can quickly and easily replicate content sources, as well as establish connections with external data sources directly through the platform's user interface.

These improvements enhance the user experience and streamline workflows.

Token Based Crawling

This update enables the development of connectors that don't rely on dates for pagination in API.

With the support for pagination and incremental crawl based on sync/delta tokens, developers now have the flexibility to implement pagination based on tokens rather than using dates.

This enables a more versatile and reliable approach to managing data sources, enhancing the overall functionality of the platform.

Share Metadata across Content Sources

Introduced a new feature that enables users to share metadata across content sources.
This update enables users to use a content source's metadata as a master and synchronize it from the parent into the child.
Additionally, users can import metadata from another content source and manage them independently afterward, providing greater flexibility and control.
This update simplifies the management and maintenance of metadata across multiple content sources, reducing the risk of inconsistencies and errors.

Automatic Text Extraction

Text extraction no longer requires manual configuration.

Connectivity Hub v3.0 now performs this function automatically.

Open Search Target

With this update, users can now index their data directly into OpenSearch Targets.

Elasticsearch v8.x Support

Elastic Target v8.x is now supported

This update enables users to take advantage of the latest features and enhancements in Elastic Target, ensuring compatibility and reliability.

Resolved Issues

Issue	Summary	Resolution
BAI-6915	Custom file names for the load-doc API not supported. File names are a randomly generated GUID created by Connectivity Hub.	Issue fixed. Load-doc API now accepts custom file names for the downloaded file. Previously, the API would generate a random GUID as the filename, which caused confusion for end-users who expected the downloaded file to have the correct filename from the original fileshare connector. With the new enhancement, a filename parameter such as `&Filename=myfile.doc` can be passed in the API URL to specify the desired filename for the downloaded file. This parameter is optional. If it is not provided, the API generates a filename using the GUID as done previously.
BAI-7431	Connectivity Hub does not include the name of the active Content Source/Connection in the title of the page. Users may find it difficult track their work, especially with multiple connections and content sources open in multiple browser tabs.	Issue fixed. The name of the Connection/Content Source/Dataset is part of the title of all pages, enabling users to easily identify which connection or content source they are working on at all times.
BAI-7530	Crawl Log UI renders HTML content found in errors. Connectivity Hub experienced a vulnerability where error messages returned by its components are not properly escaped before rendering in the crawl log user interface, which poses a risk for HTML/JavaScript injection.	Issue fixed. The updated version trims these error messages to the first 200 characters and properly escapes them to mitigate this risk.
BAI-7746	Browser tabs do not display proper page titles. Name of the section is not specified.	Issue fixed. Connectivity Hub now includes section names in page titles to improve user productivity and reduce confusion when multiple tabs are open. With this enhancement, users can identify the section they are currently viewing, even when using multiple tabs.
BAI-7815	Ability to specify file names for Doc Loader requests are unsupported.	Issue fixed. The latest implementation in Connectivity Hub 3.0 enables users to configure user-friendly names for documents downloaded using DocLoader. Users can now define the name for the downloaded documents, making it easier to identify and manage files in Smart Hub.
BAI-7895	Connectivity Hub silently ignores syntax errors for the list of properties to return from external content enrichment. The previous version of the system exhibits unexpected behavior when saving changes to a Content Source in the Advanced tab settings for the list of properties to be returned from external content enrichment. If the user enters a format that is invalid for a property, such as using a comma instead of a semicolon to separate properties, the system silently removes the affected property without displaying an error message. This can result in the loss of important properties that are needed for the Content Source to function properly.	Issue fixed. In the updated version of the system, the user is notified of the error when attempting to save the Content Source and is prompted with a message indicating the format is invalid for the property in question, along with the string extracted for declaring that property. This prevents the loss of properties due to formatting errors and enables users to make the necessary corrections to ensure the Content Source is configured correctly.
BAI-10571	Graph API experiences a long response time as a result of using default pagination The previous version of Connectivity Hub makes a call to Graph API, but the request is paginated on default page size, which causes slow response times when querying group membership.	Issue fixed. The updated version enables the Graph API limit to be configured. This improves performance by enabling users to set a more appropriate page size for their needs. With this change, users are able to customize the page size and prevent slow response times caused by requesting 100 results per page by default. In addition to enabling the configuration of the Graph API limit, the updated version of ConnectivityHub includes optimization of database queries to ensure less processing time. This optimization will help improve the overall performance of the system, resulting in faster response times for queries that involve database access. With these optimizations, users experience improved system efficiency and better response times across the platform.
BAI-10762	Connectivity Hub shows an improper count for tasks on hover. An issue caused the item count displayed in the hover status of crawl tasks to mismatch the counts in task details. If a crawl task had over 1000 items, the counts displayed in the hover status were inaccurate and did not match the counts in the task details.	Issue fixed.