Release notes v4.2.0.1

This page outlines all of the updates and enhancements in this release. For more information on upgrading, see How to Upgrade Connectivity Hub.

September 2025 - Connectivity Hub v4.2.0.1

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

System enhancements

There are no system enhancements in this release.

Fixed issues

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

  • In some scenarios, connections to Microsoft Search targets were unable to be created. (1822974)

  • If a content source was related to a connection that was inheriting specific datastores from a master security connection, crawling that content source would incorrectly include all datastores that were enabled for the master security connection. (1819782/1819871)

  • In some scenarios, when the group expansion threshold was set on the connection, groups were incorrectly being created as expanded and native. (1816638)

  • In some scenarios, after running a subsequent crawl after a successful crawl, users were incorrectly removed from security groups. (1816634)

  • When using a connector that uses the All Users Group configuration, running a subsequent security sync after a successful security sync would incorrectly cause the all users group to become inactive with no membership. (1816632)

  • When using the SharePoint Online connector, security trimming was not applied correctly when a search was run by a user who was not in the security map, but was part of the "Everyone Except External" group. (1807102)

  • In some scenarios, content source creation would fail with an "Invalid attempt to read when no data is present" error. (1801932)

  • Connectivity Hub was failing when it received users with null identifiers from the connector. (1796949)

  • Security syncs would fail for connectors that contained an excessively large number of group members. (1797405)

  • The advanced security module web service was returning the wrong results for native groups and expanded groups.

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.