Release notes v4.3.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.

November 2025 - Connectivity Hub v4.3.0.0

The following features and updates are new in this release of Connectivity Hub:

System enhancements

Feature Description
Support for stemming analyzers in AWS OpenSearch targets

Connectivity Hub can now apply analyzers to Elasticsearch, Azure AI Search, and OpenSearch target indices to determine how text is processed, indexed, and searched across search engines. These analyzers break down text into searchable tokens, applying filters such as lower-casing or stemming, and remove irrelevant elements like stop words, ensuring that user queries return accurate and relevant results, regardless of differences in case, tense, or formatting.

For more information, see Configure analyzers for specific targets
Security mapping enhancements

When making calls to the SmartHub Advanced Security Module, Connectivity Hub now supports specifying the connection ID when retrieving the user group membership for the query, allowing SmartHub to restrict group membership retrieval to only specific connections. For organizations with large Upland BA Insight implementations, this enhancement helps to improve the query efficiency and search result reliability for users.

Connectivity Hub logging enhancements

The Connectivity Hub log settings have been enhanced with the following configurable settings:

  • Enable Audit logging: This is a checkbox that, when enabled, will turn on audit logging functionality.

  • Cache database: This setting allows you to specify the cache database you are using for your audit logging.

Microsoft Azure target batching

You can now configure the index batch size to specify the number of documents that you want to send to your index in a single index request. Larger batch sizes can improve indexing throughput by reducing the number of API calls, while smaller batches help manage memory consumption and reduce the impact of individual failures. Adjusting the batch size setting allows you to optimize indexing behavior based on your data volume, network capacity, and service limits.

For more information, see Configure the index batch size for Azure AI Search targets.

Fixed issues

The following issues have been fixed in this version of Connectivity Hub:

  • When the group expansion threshold of a connection was set to All Expanded and expanded group change handling was enabled, crawling would fail on subsequent documents if two or more documents had identical security groups. (1839260)

  • In some scenarios, items deleted in the source system were still displayed in the index and database. (1834821)

  • After upgrading to Connectivity Hub 4.2.0.1, calls to the advanced security module were failing. (1836681/1837531)

  • In some scenarios, security sync jobs were failing with a "Cannot insert duplicate key in object 'dbo.@groupUserItems'" error. (1827255)

  • In some scenarios, after upgrading to Connectivity Hub 4.2, an extra log purge job was incorrectly created. (1799379)

  • Due to a limitation on the request size for Azure App Service on IIS, large files were failing to be indexed. (1795573)

  • During enumeration, if a connector returned duplicate items, the enumeration would fail, resulting in discrepancies in the search results. (1786374/1774157)

  • In some scenarios, after installing a new version of Connectivity Hub, resetting services, or deleting the cache may return a "The connection string is empty. Please make sure that Connectivity Hub is connected to a configuration database." error on the UI.

  • If a user was removed from an expanded group in the source system, that user was still being displayed in the ACL after a security sync.

  • After creating a cache database using an SQL account with proper permissions, attempting to reassign the db_owner permission to another SQL account was producing an error and the database would not be reassigned.

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.