Release notes v4.1.0.0
This page outlines all of the updates and enhancements in this release. For more information on upgrading, see How to Upgrade Connectivity Hub.
February 2025 - Connectivity Hub v4.1.0.0
The following features and updates are new in this release of Connectivity Hub:
System enhancements
| Feature | Description |
|---|---|
| Connectivity Hub licensing enhancements |
In Connectivity Hub 4.1.0.0, a new licensing module for on-premise deployments has been introduced to validate the status of your Connectivity Hub license during numerous processes and display the current status in the UI. You must contact Upland BA Insight support (bainsight-support@uplandsoftware.com) to obtain a license, which will expire at the same time as your Connectivity Hub subscription. When your license is close to expiring, the Connectivity Hub UI will display a banner message, reminding you that your subscription is about to expire. Once the license has expired, you will still be able to access the Connectivity Hub administration portal, however, Connectivity Hub will stop processing any documents and a license expired error is returned on all API calls. For more information on adding your license to your Connectivity Hub environment, see Adding your Connectivity Hub license. |
| AI/Vector search enhancements for Elasticsearch and OpenSearch |
Expanding on functionality introduce in Connectivity Hub 4.0, Connectivity Hub now offers a streamlined mechanism to index content for AI/Vector search when integrated with AutoClassifier For Elasticsearch and OpenSearch search engines. AutoClassifier can seamlessly chunk content, while Connectivity Hub ensures that all chunks are indexed and chunk records in the index are automatically refreshed when documents are added, modified or deleted. For more information, see Adding AI Search capabilities to your ElasticSearch content and Adding AI Search capabilities to your OpenSearch content. |
| Backup and restoration support |
Connectivity Hub can now backup all configuration settings, targets, connections, content source, datasets, and dataset connections in a Connectivity Hub environment to a .json file, and restore those settings to a new configuration database. When restoring, the Connectivity Hub UI will display the number of new and existing settings that were found in the .json file. After clicking Restore, the Connectivity Hub configuration will be rewritten with the backup specifications. For more information, see Backup and restore your Connectivity Hub configuration. |
| Import and Export support for connections and content sources |
Admins can now export their configuration specifications for an individual content source or connection to a .json file. The configuration can then be imported into a new content source or connection. For more information, see Export and import a content source and Export and import a connection. |
| Crawl history reporting |
This release of Connectivity Hub introduces improved crawl history tracking and reporting for admins. Admins can now view reports that detail the entire history of all crawl jobs. For more information, see view detailed historical information on your previous crawls. |
| Extracted metadata property enhancements |
The metadata property extraction mechanism has been enhanced to better manage metadata properties extracted by Tika. As a result, content related properties (properties with the escbase_<content> prefix) are no longer created when you generate your metadata. In the Test Bench results, Connectivity Hub will now display a message if there are unused metadata properties that were extracted from the content source. If you would like to add these properties to your index, you must manually add them. For more information, see Managing extracted metadata properties. |
| Microsoft Copilot enhancements |
In the target specific settings for Microsoft Search targets, you can now specify Base URLs in the URL To Item Resolver field. By doing so, Copilot and Microsoft Solutions can detect when users interact with URLs that were shared through Microsoft 365 apps, and resolve a respective Item ID to the URL. This helps to boost indexed documents that have been interacted with by members of your organization in your search results. |
| Automatic index management |
Connectivity Hub has introduced a new target specific setting to automatically index metadata as vector fields for Microsoft Azure indexes. When enabled, this setting will automatically assign the type, dimensions, and algorithm to use for your vector embeddings. These settings can also be manually configured if necessary. For further customizability, you can also specify advanced settings for your vector embeddings. For more information, see Adding AI Search capabilities to your Azure AI Search content. |
Fixed issues
The following issues have been fixed in this version of Connectivity Hub:
-
In some scenarios, the authentication method that was specified in the dataset connection settings was not being passed to the applicable connector. (BAI-17319)
-
If a datastore was deleted or disabled, Connectivity Hub was not deleting all previously crawled items after an incremental crawl was run. (BAI-17192)
-
When setting a content source with a Microsoft Search target, in some scenarios the "target Specific" tab did not appear in the configuration settings. (BAI-17054)
-
Items that were flagged for a recrawl by AutoClassifier would cause the subsequent Connectivity Hub crawl to fail. (BAI-16978)
-
An outdated BA Insight logo was the icon used in the Windows Control Panel. (BAI-16972)
-
In Test Bench, some properties were unable to be expanded. (BAI-16941)
-
When switching from advanced connection mode to basic connection mode for your configuration database, the Connectivity Hub UI would still show that you are connected via the advanced connection mode. (BAI-16405)
-
Incremental crawls were incorrectly running as full crawls. (BAI-16311)
BREAKING CHANGES
The following are breaking changes that may affect your integration. Please ensure that you carefully review this list before upgrading to Connectivity Hub 4.0 and later:
-
Due to the new crawler logic, the number of sync threads is now applied as a content specific setting. The number of sync threads that were specified will now be applied to every job that is concurrently running for the same target.
-
When upgrading Connectivity Hub 4.0 and later to integrate with AutoClassifier 7.0 and later, the URL that is used in the service URL to communicate with AutoClassifier must be updated. For more information, see "Using AutoClassifier components to enhance metadata" in the Configure Your Azure Cognitive Search Target documentation.
-
Layer 4 load balancers (NLB) are no longer supported if they must preserve the client IP. Layer 7 load balancers (ALB) must be used instead.
-
The default installation folder is now <program files>\Upland BA Insight\ConnectivityHub\. Please follow the install and upgrade instructions to ensure a seamless transition when upgrading to Connectivity Hub 4.0 and later.