Release notes v4.2.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.
August 2025 - Connectivity Hub v4.2.0.0
The following features and updates are new in this release of Connectivity Hub:
System enhancements
| Feature | Description |
|---|---|
| Automatic index management |
Expanding on support introduced in Connectivity Hub 4.1, Connectivity Hub now offers a new target specific setting to automatically index metadata as vector fields for Elasticsearch and OpenSearch 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 OpenSearch content and Adding AI Search capabilities to your Elasticsearch content. |
| Improved event logging | The Connectivity Hub logs have been improved to now display relevant information on administrative events, such as configuration updates, setting modifications, and user access updates, to enhance the auditing and tracking experience for Connectivity Hub. For more information, see view detailed information on admin actions. |
| Support for semantic_text |
This release of Connectivity Hub adds support for the semantic_text field for Elasticsearch. This field type allows you to automatically generate embeddings for text content on a specified metadata property, enhancing Connectivity Hub's ability to perform semantic searches on your data. To enable semantic search for your Elasticsearch metadata, you must turn on the Index as Semantic Field in the target specific metadata settings. For more information, see Semantic search with semantic_text in the Elastic documentation. |
| Support for Okta Target Directory configuration | Connectivity Hub now supports Okta Directory when configuring your target directory, allowing you to specify Okta users and groups for authentication when a user runs a search query. |
| Crawl enhancements for expanded groups | During a security sync, the Connectivity Hub crawl mechanism will now recognize when an expanded groups membership within a source system has changed, and automatically flag that group to be recrawled on the subsequent incremental crawl job. For more information see Manage security for users and groups. |
| Support for script connectors | Connectivity Hub now includes support for script sub-connectors, allowing you to simulate and test connector behaviors. These script connectors can be used to emulate specific use cases, such as unexpected data, timeouts, performance testing, etc. For more information, see Configure script connectors for testing. |
| TestBench enhancements | TestBench has been redesigned and re-factored to improve the user experience and provide more context for your connector tests. For more information, see Testing Your Connector Configuration. |
| Security optimization | Security Syncs and the Advanced Security Module have been enhanced to improve database interaction, query logic, indexing mechanisms. |
| Quartz Memory optimization | The memory consumption of the Quartz scheduler has been optimized in this release, alleviating the over consumption of memory when running your Connectivity Hub tasks. |
Fixed issues
The following issues have been fixed in this version of Connectivity Hub:
-
When selecting metadata from an Elasticsearch target, the Target Specific tab was not displaying. (BAI-17821).
-
When an additional onPremisesSamAccountName property was configured in the Connectivity Hub target directory alongside a user loading script to retrieve a user by the specified attribute and value via the getUserByAttribute function, the call to retrieve the user would fail in a security sync. (BAI-17816)
-
If you configuring a content source with a dataset mapping, then deleted the initial dataset content, the deleted content would appear as a blank entry in the Dataset Mappings table. (BAI-17750)
-
In some scenarios, if a crawl job was paused then resumed, an error was returned. (BAI-17711)
-
Calls to the advanced security module were not returning the parent native groups of the static groups. (BAI-17455)
-
When selecting Leave File on Disk from TestBench for a content source, the file created on the disk had the wrong size and content. (BAI-16589)
-
TestBench was returning incorrect security access information for a specific article. (BAI-16446)
-
Scheduled jobs were unable to be created when used with a cron template. (BAI-15475)
-
In TestBench, the Validate User Access text box was incorrectly case-sensitive (BAI-14510)
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 from versions prior to Connectivity Hub 4.0 or later to integrate with AutoClassifier 7.0 or later, the Service URL that is used to communicate with AutoClassifier must be updated. For more information, see Using AutoClassifier components to enhance metadata.
-
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.