Archived BA insight release notes

Connecitivty Hub

November 2025 - Connectivity Hub 4.3.0.2

System enhancements

There were no system enhancements in this release.

Fixed issues

The following issues were fixed in this version of Connectivity Hub:

  • Calls to the advanced security module were failing when an Okta target directory was configured. (1836681)

  • Pagination for advanced security module group retrieval was not working for Okta target directories.

November 2025 - Connectivity Hub v4.3.0.1

System enhancements

There are no system enhancements in this release.

Fixed issues

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

  • For some users, calls to the advanced security module were taking excessively long to complete. (1851107/1850946/1841066)

  • If the source ID for the user mappings of a connector had the same target directory account in Azure Active Directory, calls to the advanced security module would fail. (1837531)

November 2025 - Connectivity Hub v4.3.0.0

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.

October 2025 - Connectivity Hub 4.2.0.2

System enhancements

There were no system enhancements in this release.

Fixed issues

The following issues were fixed in this version of Connectivity Hub:

  • In some scenarios, security sync jobs were failing with a "Violation of PRIMARY KEY constraint 'PK_GroupUser'. Cannot insert duplicate key in object 'dbo.GroupUser'." error. (1796949)

September 2025 - Connectivity Hub 4.2.0.1

System enhancements

There were no system enhancements in this release.

Fixed issues

The following issues were 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.

August 2025 - Connectivity Hub 4.2.0.0

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 Elastic search 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)

July 2025 - Connectivity Hub 4.1.0.3

System enhancements

There were no system enhancements in this release.

Fixed issues

The following issues were fixed in this version of Connectivity Hub:

  • In some scenarios, after an initial successful security sync task, the subsequent security sync would fail. (BAI-18189)

  • After upgrading from Connectivity Hub 2.x to Connectivity Hub 4.1.0.2, crawl jobs had a significant delay before they were processed. (BAI-18033)

  • After upgrading from Connectivity Hub 2.x to Connectivity Hub 4.1.0.2, there were increased delays when requesting Access Control Lists through the Connectivity Hub API. (BAI-18025)

  • Due to limitations with the Microsoft Graph API, security sync tasks were not populating groups with group members for Microsoft Search targets and connections. (BAI-18011)

  • Due to limitations with the Microsoft Graph API, in some scenarios, security sync tasks with Microsoft Search targets were failing. (BAI-17926)

April 2025 - Connectivity Hub 4.1.0.2

System enhancements

There were no system enhancements in this release.

Fixed issues

The following issues were fixed in this version of Connectivity Hub:

  • In some scenarios, after upgrading from Connectivity Hub 3.x to Connectivity Hub 4.x, incremental crawls were failing with errors in the crawl service logs. (BAI-17885)

  • If you ran a security sync task directly after a successful security sync task, the task would fail. (BAI-17862)

  • On datastore based connectors, modified items were not being detected during an incremental crawl. (BAI-17861)

  • In some scenarios, crawl jobs were stuck with a "running" status, despite being completed. (BAI-17827)

  • In some scenarios, if a job was stopped then restarted, the job status remained as "interrupted". (BAI-17827)

  • Retry behavior was added when a security sync was experiencing incorrect behavior from Microsoft Graph. (BAI-17788)

  • In some scenarios, you were unable to save scheduled tasks. (BAI-17780)

  • In some scenarios, if a crawl job was paused then resumed, an error was returned. (BAI-17711)

  • Security sync jobs were running exceedingly slow. (BAI-17686)

  • In some scenarios, crawl jobs were stuck with a "stand by" status. (BAI-17681)

  • After upgrading from Connectivity Hub 3.x to Connectivity Hub 4.x, you were not able to pause jobs. (BAI-17674)

  • When running a crawl with the iManage connector, errors appeared stating that the "All Users Group" was missing. When the "All Users Group" was manually added, the crawl would fail. (BAI-17664/BAI-17819)

April 2025 - Connectivity Hub 4.1.0.1

System enhancements

There were no system enhancements in this release.

Fixed issues

The following issues were fixed in this version of Connectivity Hub:

  • In certain edge cases, incorrect logic was causing crawl request authentication to fail. (BAI-17643)

February 2025 - Connectivity Hub 4.1.0.0

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

  • 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)

March 2025 - Connectivity Hub 4.0.0.2

System enhancements

There were no system enhancements in this release.

Fixed issues

The following issues were fixed in this version of Connectivity Hub:

  • An incompatibility with the Log4Net library was causing logging to fail (BAI-17398)

  • In some scenarios, the authentication method that was specified in the dataset connection settings was not being passed to the applicable connector. (BAI-17319)

February 2025 - Connectivity Hub 4.0.0.1

System enhancements

There were no system enhancements in this release.

Fixed issues

The following issues were fixed in this version of Connectivity Hub:

  • When a crawl was run using a SOLR target, all the properties were missing from the crawl results. (BAI-17286)

  • After upgrading to Connectivity Hub 4.0.0.0, Smart Previews was failing to generate previews. (BAI-17264)

  • If a SharePoint Online site was included in a security sync and then deleted in SharePoint Online, the subsequent security sync job would fail. (BAI-17252)

  • When Connectivity Hub was configured with an iManage connector, the security sync job was not returning user properties. (BAI-17239)

December 2024 - Connectivity Hub 4.0.0.0

System enhancements

Feature Description
Upland Software, Inc rebranding

Numerous UI updates were made for Connectivity Hub to match the standard Upland Software, Inc format. The following will now match the Upland style:

  • The Connectivity Hub installation wizard

  • The Connectivity Hub end user license agreement

  • The UI in the Connectivity Hub administration portal
AI/Vector search enhancements

When integrated with AutoClassifier 7.0, Connectivity Hub offers a streamlined mechanism to index content for AI/Vector search. 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. This functionality is currently only supported for Microsoft Azure Search targets.

If you need both an AI/Vector index and a traditional full-text index for a given content source, you must configure two content sources within Connectivity Hub.

For more information, see Adding AI Search capabilities to your Azure AI Search content.
Microsoft Copilot support

Microsoft Copilot is now supported in this release of Connectivity Hub, enabling you to leverage Microsoft Copilot capabilities in the content indexed by your connectors. In this release, the following features were added:

  • The following semantic labels were added to allow Microsoft Copilot to answer user queries more precisely:

    • CreatedBy

    • LastModifiedBy

    • CreatedDataTime

    • FileName

    • IconUrl

    • ContainerName

    • ContainerUrl

  • Admins can specify meaningful descriptions for their content sources that are indexed by Microsoft Search targets.

For more information, see Target specific settings to enhance Microsoft Copilot functionality and Metadata specific settings to enhance Microsoft Copilot functionality.
Distributed crawl and Security Sync improvements

This release of Connectivity Hub features a new distributed crawler, allowing for better scaling, fail-over, and overall improved stability. For more information see How to deploy or upgrade a multi-server configuration.

Note the following:

  • The distributed crawl model uses a single Quartz instance that runs across all servers, allowing admins to schedule, start, and stop jobs by interacting with a single Quartz job in the farm.

  • Security Sync jobs have been enhanced to significantly improve performance and reduce the time it takes to complete a security sync.

  • Layer 7 load balancers are supported.

  • Layer 4 load balancers are supported if the client connections are terminated at the load balancer and the client IP is not preserved.

  • Upland BA Insight strongly recommends using HTTPS for secure communication with the Connectivity Hub administration portal.
Configuration settings enhancements Email addresses that were specified in the Configuration Settings for your Connectivity Hub instance will now auto-populate when creating a crawl job or related task.
SQL Server support Support for SQL Server 2012 has been removed in this release. Connectivity Hub now supports SQL Server 2016 and later.
SQL Client default encryption

Due to a vulnerability fix on SQLClient, the default encryption flag for SQL connections and Connectivity Hub database connections has been set to True. If you do not support encryption in your database connections, you must override the default encryption flag in the advanced connection settings by specifying Encrypt=false in the connection string.

For more information, see index your own database using the SQL connector.

Managed Identity for SQL database connections support

Connectivity Hub now supports using managed identity authentication to connect to a Microsoft Azure SQL database. The following authentication methods are supported:

  • SQL authentication

  • Microsoft Azure Active Directory username and password authentication

  • Microsoft Azure Active Directory Integrated authentication

  • Microsoft Azure Active Directory Service Principal authentication

  • Microsoft Azure Active Directory Managed Identity or Managed Service Identity (MSI) authentication

For more information, see Enable managed identities.
Automatic dependency upgrades Connectivity Hub will now automatically update all libraries and dependencies when your environment is upgraded. For a current list of all dependencies, see Third-Party Dependencies.

Fixed issues

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

  • Empty folders were still displaying even if the "Hide Empty Folder" option was enabled in TestBench for your content source. (BAI-3845)

  • During a crawl job, the memory was not properly deallocated after the crawl was finished. (BAI-8325)

  • If your summary page for a crawl job contained a high number of errors, the page would fail to load. Connectivity Hub will now group similar error messages to ensure the UI will display properly. (BAI-10196)

  • When performing a crawl in PowerTools for datastore connectors, Connectivity Hub was failing. (BAI-10531)

  • Microsoft Azure Active Directory group lookup did not handle special characters or empty values. (BAI-10839)

  • FileShare security was not compatible with Microsoft Azure Active Directory targets. (BAI-10840)

  • The datastores selection filter was incorrectly displayed in the repositories connectors page. (BAI-10986)

  • Connectivity Hub would crash when multiple scheduled jobs were running concurrently. (BAI-11023)

  • Users may have seen errors after clicking View Items for crawl logs for items that were grouped under the same entry. (BAI-11510)

  • When adding new web service content, SQL connections were also displayed in the Connections drop-down list. (BAI-11618)

  • If a user clicked the Test/Load metadata button multiple times when creating a content source, all verification messages would display under each other. (BAI-11651)

  • Including HTML characters, such as '<', in the content source Enumeration Query field, would produce an error. (BAI-11651)

  • If you attempt to connect to a cache database that does not exist, Connectivity Hub will now display an appropriate error message. (BAI-11968)

  • Connectivity Hub will now display an error in the crawl log if it determines that a multi-value property was received for a single value property. (BAI-12078)

  • When running a full crawl using PowerTools with the max file size specified, the crawl would include attachments that exceeded the max file size. (BAI-12079)

  • Security sync jobs would display the number of modified groups as equivalent to the number of added groups. (BAI-12257)

  • Users were redirected to the content sources page after clicking the save button on a connection. (BAI-12273)

  • The overall performance speed of the UI and crawl service on the first request has been improved. (BAI-14344)

  • In PowerTools, navigating to a specific folder was not possible. (BAI-14595)

  • Search results that relied on multi-level security permissions would not display correctly according to the permission logic. (BAI-15064)

  • Improved error handling when configuration errors that occurred during a crawl job on an Amazon Kendra target. (BAI-15981)

  • The implementation of SQL queries were modified to improve the performance on Connectivity Hub during crawls. (BAI-16240)

  • The Connectivity Hub API displayed passwords in the response for various endpoints. (BAI-16590)

AutoClassifier

September 2025 - AutoClassifier 7.2.0.0

System enhancements

Feature

 Description
Support for Python scripting

This release of AutoClassifier adds a new Python Scripting component, allowing you to utilize the capability of a Python script of your choosing. For example, you can use Langchain text splitters to break down content from Confluence and HTML pages, improving the relevancy and accuracy of retrieved results from your indexed content, while also enhancing AI-driven functionality such as content summaries and contextual answers. For more information, see Using Python script capabilities.

To be able to integrate Python scripting functionality in your AutoClassifier environment, you must install the AutoClassifier Python Script Runner Rest API when you install the AutoClassifier engine. For more information, see Install AutoClassifier Engine Components.
Improved event logging The AutoClassifier logs now provide in depth relevant information on administrative events, such as configuration updates, setting modifications, and logging modifications, to enhance the auditing and tracking experience for AutoClassifier. For more information, see View detailed information on admin actions.
Support for on-demand annotation testing In the AutoClassifier SharePoint add-in, you can now test the annotation of a single document in your SharePoint environment for debugging, configuration issues, or pipeline validation on-demand. For more information, see Annotating your documents on-demand for testing.
Document Chunking enhancements In the Document Chunker component, the default value for the Max Text To Extract field is now set to 2MB. For more information, see Configure the document chunker component.
Video Indexer enhancements In addition to local storage, the Microsoft Video Indexer component now supports network paths for storing and processing videos. For more information, see how to classify videos.

Bug fixes

  • When a metadata property was overridden using the AutoClassifier script component, existing metadata from parent properties were missing from the response.

  • When using the document chunker component on a PowerPoint presentation, the component was not inheriting the section title from the previous slide if the current slide did not explicitly define a section.

  • In some scenarios, AutoClassifier was failing to process requests from Connectivity Hub when it was deployed on a server that did not use the en-US regional settings.

  • The Azure Open AI Embeddings Generator component was generating metadata for metadata properties that did not exist in the pipeline.

  • In some scenarios, pipeline stages would perpetually run when specific documents were being tested. (1715804)

April 2025 - AutoClassifier 7.1.0.0

System enhancements

Feature

 Description
AI metadata extraction

This release adds the OpenAI information extractor component. The Azure OpenAI information extractor component allows you to use and configure natural language queries from Azure OpenAI and OpenAI LLMs to extract information from your documents. The component can generate suggestions of metadata and questions based on documents that you provide during configuration.
Contextual Metadata Merger This release adds the Contextual Metadata Merger component. This component can refine, filter, and concatenates your metadata to only include relevant information. Additionally, this component can prefix your concatenated metadata to another metadata property, such as the Chunk body property from the document chunker, to enhance document retrieval with more accurate results.
OpenAI and Azure OpenAI embeddings generator components This release adds the OpenAI and Azure OpenAI embeddings generator components. These components allow you to automatically apply vector embeddings to specified properties in your documents. When applied, these embeddings can be used to enhance the accuracy of your search results and provide a better natural-language experience for your users.
RESTful API compatibility

The Restful API Caller component allows you to integrate AutoClassifier with any RESTful APIs (LLMs, AI Cloud Services, etc.) by enabling flexible endpoint configurations, request customizations, and API response management to facilitate efficient data transformation and metadata generation.

For more information, see Apply RESTful API functionality to your content.
AI Visual Interpreter This release adds the AI Visual Interpreter component. This component allows you to use an AI model to analyze visual content, such as images, graphs, and non-structured data, from your documents. When this information is interpreted and extracted, it can be appended as metadata and used to enrich chat bots with context-aware responses. Users will then be able to query their documents for information that is interpreted from non-textual assets.
Document Intelligence enhancements

The Document Intelligence component has been updated to support the following:

  • You can now use the Output format style setting to specify whether you would like your output in text or markdown format.

  • You can now use the Max Pages Per Request setting to divide your documents into segments based on the specified number of pages. This allows the Document Intelligence component to support documents with more than 2000 pages.

Document Chunker enhancements

The Document Chunker component has been updated to support the following:

  • You can now use the Excel Chunking Settings to add additional chunking capabilities for Microsoft Excel files such as splitting by sheets, extracting a specified number of rows as headers, specifying the size of your excel chunks, and specifying the output format.

  • The ChunkPageNumber metadata property has enhanced logic for capturing the respective worksheet number and slide number for Microsoft Excel and PowerPoint files.

  • The output metadata now returns the ChunkBodyForVectorization property, which provides the plain text of ChunkBody property, removing the HTML tags.

  • The output metadata can now include the following metadata, depending on your configuration:

    • ChunkWorkbookName: This property displays the name of your Microsoft Excel workbook.

    • ChunkWorkSheetName: This property displays the name of your Microsoft Excel sheet.

    • ChunkSlideTitle: This property displays the title of the PowerPoint slide.

    • ChunkSlideSectionName: This property displays slide section name of the PowerPoint slide.
Video Indexer enhancements The Video Indexer component has been enhanced to now support extracting subtitles that are included in videos. To use this feature, you must enable the Extract OCR field in the component configuration.
Credential storage enhancements

You can now store your credentials and sensitive information in Azure Key Vault for retrieval by the AutoClassifier scripting component. This prevents sensitive information from being included or exposed in your AutoClassifier scripts.

For more information, see Configuring your Azure key vault storage in the Configure your configuration settings topic.
Scripting enhancements

The following updates are new to the AutoClassifier script component in this release:

  • The AutoClassifier script component can now retrieve the entire list of item properties for a content source in either XML or JSON format. For more information, see Using custom logic.

  • AutoClassifier no longer stores API keys, access keys, or other secrets in Pipeline Stages and configuration files. Now, all credentials are stored in Azure Key Vault storage. For more information, see Configuring your Azure key vault storage in the Configure your configuration settings topic.

  • The script component can not execute or spawn any external processes. Only importing libraries is permitted within the script component.

Bug fixes

  • In some scenarios, the AutoClassifier document chunker component would cause Connectivity Hub crawls to fail. (BAI-17350)

  • When selecting the settings icon in the script component, the Namespaces window displayed in an incorrect location. (BAI-17159)

April 2025 - AutoClassifier 7.0.0.1

System enhancements

Feature

 Description
Scripting enhancements

The AutoClassifier script component has been updated to not allow external executables or powershell commands from being executed. The script component only allows importing and using libraries. For more information, see how to use custom script logic.

Fixed issues

There were no fixed issues in this release

August 2024 - AutoClassifier 7.0.0.0

System enhancements

Feature

 Description
Upland Software, Inc rebranding

UI updates were made for AutoClassifier to match the standard Upland Software, Inc format. The following will now match the Upland style:

  • The AutoClassifier installation wizard

  • The AutoClassifier end user license agreement (EULA)

  • The UI in the AutoClassifier administration portal
Document chunking components

When using AutoClassifier 7.0.0.0 to implement vector search, you can now use our new chunking pipeline stage to break down large documents into small segments.

The chunking stage can be configured to specify the number of characters per chunk, the chunk overlap percentage, and the chunk separator characters. Our chunking stage also provides optimized logic for Microsoft Office documents to generate the ideal chunk sizes based on chapters, slides, and sheets. Additionally, the recorder component will now save child item and chunk item properties. For more information, see Applying chunking capabilities to your data.

Document Intelligence support

This release of AutoClassifier adds the Azure Document Intelligence component to integrate with the Microsoft Azure Document Intelligence Service to extract plain text and insights from documents using AI technologies. This component automatically performs optical character recognition (OCR) on graphical information within documents, extracts specific structured fields from document content, processes tabular data, and outputs it in formats that are easily understandable and consumable by AI models in generative AI processes and vector search.

Additionally, the Document Intelligence component includes the following key features:

  • Expanded file format support

  • Selective field extraction with confidence scoring

  • Enhanced plain text extraction with page information

  • Optimized table data processing

For more information, see Azure Document Intelligence component.
AutoClassifier licensing enhancements

In AutoClassifier 7.0.0.0, a new licensing module for on-premise deployments has been introduced to validate the status of your AutoClassifier 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 AutoClassifier subscription.

When your license is close to expiring, the AutoClassifier 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 AutoClassifier administration portal, however, AutoClassifier 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 AutoClassifier environment, see Adding your AutoClassifier license.
Administration portal functionality enhancements

AutoClassifier has implemented a new UI design for the administration portal, which provides additional functionality to admins. The following UI functionalities are new in this release:

  • Admins can now edit the name of their taxonomies by clicking the Edit button on the Manage Taxonomies page.

  • Whenever admins perform an action in the administration portal, a snackbar message will appear with a relevant message for the action that was performed.

  • If there are unsaved changes in a pipeline, a warning banner will now display at the top of the screen.

  • The left side panel can now be viewed in a collapsed or expanded state.

  • Admins will now receive a confirmation dialog before they can delete an item in the administration portal.

  • On the manage taxonomies screen, when selecting a new component type, additional descriptive text now displays for the selected component type.
Support for Microsoft video indexer offline pipeline

The configuration settings for the Microsoft Video Indexer component hav been updated to address changes with the Azure AI Video Indexer.

Admins can now add the Microsoft Video Indexer component to an offline pipeline. For more information, see How to Classify videos.
Support for Managed Identities

This release of AutoClassifier adds support for managed identities authentication. AutoClassifier is now able to connect with the AutoClassifier database in the following authentication methods:

  • Microsoft Azure Active Directory username and password authentication

  • Microsoft Azure Active Directory Integrated authentication

  • Microsoft Azure Active Directory Service Principal authentication

  • Microsoft Azure Active Directory Managed Service Identity (MSI) authentication

To configure one of these authentication methods, a valid connection string is required. For more information, see AutoClassifier Engine Post-Installation Configuration.
Deprecated endpoints The Content Enrichment Web Service (CEWS) is deprecated and will be removed in a future release. Upland BA Insight recommends using the Enrichment Web API when integrating with Connectivity Hub.
Removed services

The following services and functionalities have been removed from AutoClassifier 7.0.0.0:

  • Term suggestions

  • Carrot2 clustering
Removed Components

The following components have been removed from AutoClassifier 7.0.0.0:

  • Named Entity Recognition

  • Docuvision

  • Clustering Service

Bug fixes

  • The Section Information Extractor component did not return the correct number of results. (BAI-11878)

  • The error messages to indicate a failure during the machine learning training process page were displayed in green text. (BAI-12165)

  • The error received when exporting a Machine Learning stage and importing it to a pipeline stage, has been updated to be more informative. (BAI-12166)

  • Attempting to train a machine learning provider with an invalid secret ID would cause the process to infinitely load. (BAI-12171)

  • Request retry attempts for NetDocuments adapter crawl jobs would start at 0 instead of 1, meaning retry attempts would not be equivalent to the value specified in the UI. (BAI-12240)

  • When an adapter had an idle status, the actions menu showed actions that should not have been available to the adapter. (BAI-12241)

  • The names of adapters in the existing adapters list are now truncated to prevent UI errors. (BAI-12244)

  • During a crawl job, items that failed to be processed in AC will now be recrawled during the next crawl job. (BAI-15327)

SmartHub

October 2025 - SmartHub 7.2.0.0

System enhancements

Feature Description  
Chat with documents in conversational search

You can now use the chat with documents feature in your conversational search configuration to allow users to restrict their conversational search bot queries to only search specified documents for an answer. Users can select a document to chat with from the search results page, the related documents panel, and the SmartHub basket.

For more information, see Using chat with documents.

  
User feedback for conversational search results

When using SmartHub conversational search, you can now enable the ability for users to provide feedback on the documents that are returned by the conversational search bot's response. When a user provides feedback, an email is generated to a configured email address stating question asked by the user, the answer generated by conversational search, the status of the document feedback (liked or disliked), and additional details provided on the feedback module.

For more information, see Applying feedback to your conversational search responses.

  
Developer mode for conversational search

You can now use developer mode for conversational search to easily access debug information that is normally only available on the internal logs when the SmartHub log level is set to Debug.

For more information, see Using developer mode for conversational search.

  
Content container enhancements

When configuring the content container module, you can now specify the following setting:

  • TriggerNewQueryOn: This setting specifies the name(s) of the event(s) that, when triggered, will execute a new query and render the results. If this is left empty, then the container only renders after being invoked by the API.

For more information, see Adding the Content Containers Module.

  
Conversational Search enhancements

When configuring the conversational search module, you can now specify the following settings:

  • DisableOnRefinersInteraction: When this setting is set to true, the conversational search bot will not trigger a new question if the user applies or has applied search refiners on the page.

  • RefinersAppliedSearchBoxPlaceholder: This setting specifies the placeholder text for the searchbox when filters are applied and DisableOnRefinersInteraction is set to true.

  • HybridModeSearchTabIds: In hybrid mode, this setting specifies a semicolon separated list of search vertical IDs to restrict the conversational search query to one or multiple search verticals. By default, this setting is empty, meaning that the query will execute on all search verticals.

For more information, see Configure the conversational search module for your SmartHub pages.

  
Improved event logging

The SmartHub logs have been improved to now display relevant information on administrative events, such as configuration updates, setting modifications, and search engine and tuning stage updates, to enhance the auditing and tracking experience for SmartHub.

For more information, see view detailed information on admin actions.

  
Search vertical enhancements

The SmartHub search vertical settings now include the option to preserve any applied refiners when the tab is changed.

For more information, see Configure Search Verticals.

  
Saved queries sorting Saved queries are now displayed in chronological order, with the most recently saved query appearing at the top of the list.  
Support for overlapping range facets

SmartHub now supports configuring both overlapping and non-overlapping range facets for date, size, and time, allowing your users to specify how flexible or accurate they want their refined search results to be.

For more information, see Specify custom intervals for ranged refiners.

  
Custom page settings When creating a new custom settings file for your SmartHub pages, they will now have human-readable names, allowing for increased flexibility when transferring settings to a new SmartHub environment. If you are upgrading your SmartHub instance, SmartHub will maintain your existing settings nomenclature to ensure backward compatibility.  

Fixed issues

The following issues were fixed in this release:

  • After upgrading from SmartHub 6.x to SmartHub 7.x, type-ahead query suggestions were not displaying correctly. (1821463)

  • Exporting to excel for a SharePoint Online embedded page was not able to find the path to export template. (1811586)

  • In some scenarios, after returning to the SmartHub landing page from the results page, certain settings, css, and JavaScript configurations were not applied. (1797773)

  • In some scenarios, the conversational search response was retuning a "Something went wrong. Please contact administrator" error message as the chat answer. (1797335)

  • In some scenarios, when a search query contained a term that was spelled incorrectly, expertise searches were not showing suggested search results. (1797234)

  • In some scenarios, the conversational search response was inserting extra spaces in the middle of words and splitting sentences onto a new line. (1788547/1797335)

  • When in mobile mode, type-ahead was not maintaining updates made to the sort order. (1779020)

  • When a PowerPoint work hubs integration was opened in a browser, a "something went wrong, missing redirect URL parameter" error appeared after sign in. (1768485)

  • When two or more search engines were configured, date range facets were not sorting in default order. (1760761)

  • In some scenarios, applying a refiner to a hybrid conversational search instance would return an error.

  • In an Akumina integrated page with type-ahead configured, the search box border was appearing as too small when typing a query.

  • When a specific file type refiner was excluded, all other file type refiners would disappear.

August 2025 - SmartHub 7.1.0.1

System enhancements

There were no system enhancements in this release.

Fixed issues

The following issues were fixed in this release:

  • If a conversational search conversation returned more than 3 source documents, then a subsequent conversation also returned more than 3 source documents, the list of source documents in the subsequent conversation were the same as the initial conversation.

  • Conversational search in hybrid mode was not limited to specific tabs.

  • Clicking New Chat in a conversational search conversation was not clearing the related documents list from the previous conversation. (1803783)

  • In the conversational search response, only a single source document was displayed despite multiple documents being referenced as citations by the LLM. (1803776)

  • Applied refinement filters were not being passed to the answer API of the conversational search service. (1802282)

  • In some scenarios, conversational search refiners were stuck in a loading loop and were not being applied to the answer API. (1802282)

  • In the conversational search response, the title of the source document displayed incorrectly when it was hovered over. (1802282)

  • In some scenarios, the conversational search response was replaced with a "Something went wrong. Please contact administrator" error message. (1797335)

  • In some scenarios, the conversational search response was inserting extra spaces in the middle of words and splitting sentences onto a new line. (1788547/1797335)

  • If a conversational search query was executed while the answer to another search query was processing, the summary of the second search query was displaying the first queries answer. (1784477)

June 2025 - SmartHub 7.1.0.0

System enhancements

Feature Description
Related documents in split-screen view

This release of SmartHub adds support for displaying related documents in a split-screen view, allowing users to receive the functionality of traditional SmartHub search and SmartHub conversational search from a single page.

When enabled, a new pane displays with related results that are most similar to the user's last conversational search message. For more information, see Configure the conversational search module for your SmartHub pages.
Support for conversational search filters

You can now configure search refinement filters that users can apply to their Conversational Search chats to fine-tune the AI-generated responses for parameters such as author, category, format, etc.

These filters work similar to SmartHub refiners, but they are applied to the knowledge sources that are used by your chosen LLM to provide answers. After applying filters, they will be taken into consideration when a subsequent question is asked. They will not be used for any question that was asked before the filter was applied. Users also have the option to clear their applied filters, and all filters will be cleared when a new conversation is started or the page is refreshed.

For more information, see Using Conversational Search filters.
Document previews in chat interface

When using SmartHub conversational search, users will now be able to preview the relevant sources that powered the conversational search bot's response. By clicking the Sources button under the response, a list of documents will display. Selecting one of these documents will allow users to go directly to the source or preview the document.

When previewing the document, a new panel will open to the right of the conversational search response, opening the preview on the relevant page from the document. For more information on configuring Smart Previews settings for conversational search, see Configure the conversational bot settings.
RESTful query tuning stage

This release of SmartHub adds the RestfulPostman tuning stage, allowing you to use the functionality of any Restful API (LLMs, AI Cloud Services, etc.) of your choosing to enhance your user's search experience.

For more information, see Apply Restful API functionality to your search queries.
Vector embedding generator tuning stages

This release of SmartHub adds two new user experience tuning stages for Azure OpenAI and OpenAI vector embedding generation. These stages can automatically transform user search queries to apply vector embeddings to the query during runtime.

For more information, see Apply vector embeddings to user queries with the OpenAI embeddings generator and Apply vector embeddings to user queries with the Azure OpenAI embeddings generator.
SmartHub Analytics enhancements

The SmartHub analytics mechanism has been updated with the following enhancements:

  • SmartHub analytics now provides detailed information on the state of a user's search query. This includes the keywords, as well as all refiner properties and values that were applied to the query when it was executed. For more information, see Events captured in the SmartHub Analytics default schema.

  • The search module now tracks when a refiner is removed, recording information about the query, the refiner, and the user. For more information, see Tracking user queries and selections
Elasticsearch Authentication enhancements

You can now configure your Elasticsearch search engine to use an API key for authentication.

For more information, see Configure your Elasticsearch search engine to use API key for authentication.
Support for Vector search with Elasticsearch and OpenSearch Elasticsearch and OpenSearch search engines now support vector search and hybrid search queries. In the Elastic Translator user experience tuning stage, you can enable the Enable Pure Vector Search field to allow SmartHub to submit pure vector or hybrid search queries. For more information, see Translate queries into an Elastic search query with the Elastic Translator
Updated behavior for pure vector searches with Azure AI Search

Pure vector search is now enabled by default when using the Azure Query Translator user experience tuning stage. If a user's search query does not have vector embeddings, this setting is ignored.

For more information, see Translate queries into an Azure search query with the Azure Query Translator.
Date Refiner support for Microsoft Search Items

In this release of SmartHub, enhancements were made to flatten specific properties received from the Microsoft Graph API. Depending on the Microsoft Graph response structure, this update may remove the need to map to the tree-based metadata structure from the Microsoft Graph API response. When configuring the property mapper tuning stage, you now only need to provide the property names for driveItem and listItem fields, and externalItem properties for your mapping.

If you are upgrading from a previous version of SmartHub, the property mapper tuning stage must be reconfigured.

For more information, see Microsoft Search Items.
Conversational search enhancements

You can now specify the text rendering mode for your conversational bot's response. The following 3 modes are available:

  • character: This instructs the page to render each letter of a received chunk, one by one.

  • chunk: This instructs the page to render each chunk of the bot response, one by one.

  • nonstream: This instructs the page to render the full bot response all at once. This will use the FullMessage event instead of the Message event.

For more information, see Configure the conversational search module for your SmartHub pages.

Fixed issues

The following issues were fixed in this release:

  • After upgrading from SmartHub 6.x to SmartHub 7.x, type-ahead query suggestions were not displaying correctly. (1821463)

  • Exporting to excel for a SharePoint Online embedded page was not able to find the path to export template. (1811586)

  • In some scenarios, after returning to the SmartHub landing page from the results page, certain settings, css, and JavaScript configurations were not applied. (1797773)

  • In some scenarios, the conversational search response was retuning a "Something went wrong. Please contact administrator" error message as the chat answer. (1797335)

  • In some scenarios, when a search query contained a term that was spelled incorrectly, expertise searches were not showing suggested search results. (1797234)

  • In some scenarios, the conversational search response was inserting extra spaces in the middle of words and splitting sentences onto a new line. (1788547/1797335)

  • When in mobile mode, type-ahead was not maintaining updates made to the sort order. (1779020)

  • When a PowerPoint work hubs integration was opened in a browser, a "something went wrong, missing redirect URL parameter" error appeared after sign in. (1768485)

  • When two or more search engines were configured, date range facets were not sorting in default order. (1760761)

  • In some scenarios, applying a refiner to a hybrid conversational search instance would return an error.

  • In an Akumina integrated page with type-ahead configured, the search box border was appearing as too small when typing a query.

  • When a specific file type refiner was excluded, all other file type refiners would disappear.

June 2025 - SmartHub 7.0.0.1

System enhancements

Feature Description
Support for Dynamics Hub in PowerApps (mobile support)

If you have configured a Microsoft Dynamics Hub, you can now open SmartHub in a browser when accessing it from the Microsoft PowerApps mobile app.

Fixed issues

  • In some scenarios, the conversational bot was not displaying a message to a users query. (BAI-17958)

  • In some scenarios, when SmartHub was integrated with SharePoint Online, the user was prompted to login to both SmartHub and SharePoint Online. (BAI-17948)

  • When a document was converted to markdown format and chunked into sections, the chunks contained incorrect formatting and the markdown syntax displayed as plain text. (BAI-17644)

April 2025 - SmartHub 7.0.0.0

System enhancements

Feature Description
SmartHub UI enhancements

This release of SmartHub provides a redesigned user interface for your users. This update enhances and modernizes your SmartHub search and results pages, allowing users to efficiently navigate their search results and provide them with additional control.

For more information on customizing your user's search experience, see How to use the UI Editor.
Conversational search support

This release of SmartHub introduces the Conversational Search API. The conversational search solution allows you to configure a conversational bot that your users can interact with to ask specific questions related to your indexed content. For more information, see Conversational Search.

By using SmartHub conversational search, you agree to the terms and conditions listed in the Upland AI disclaimer.
SmartHub licensing enhancements

This release of SmartHub introduces a new licensing module for on-premise deployments to validate the status of your SmartHub 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 SmartHub subscription.

If you do not have a license configured, admins will be able to use the SmartHub administration portal to configure SmartHub, but no search results will be returned.

For more information, see adding your SmartHub license.
Refiner enhancements The data-use-radio-buttons property has been added to the refiner settings in this release. This setting changes the refiner to use radio buttons instead of checkboxes to allow for only single value selection. For more information, see Add Refiners to Your Search Results.
Learn-To-Rank enhancements The Learn-To-Rank component has been enhanced to boost and suggest documents based on interaction between users with similar classifications. For example, document search results can be prioritized if a user shares the same or similar role, location, job type, etc. as a user who previously interacted with a document. For more information, see Learn-to-rank settings.
Spellcheck and spelling suggestion enhancements

For Azure AI Search, SharePoint Online, Elasticsearch, and OpenSearch search engines, the spelling suggestion mechanism has been upgraded to suggest spelling alternatives for misspelled personal names, company names, and specific terms that are relevant to the user. For more information, see Configure the spellchecker function.

If you are using an Azure search engine, you must specify the suggester name for your Azure index. For more information, see Connect SmartHub to the Azure Cognitive Search Engine.

If you are using an Elastic search engine, you must configure the SuggestionFields setting. For more information, see configure Your Elasticsearch search engine.
Support for Microsoft Azure access token exchange

SmartHub now supports token exchange, allowing SmartHub to accept authentication tokens generated by another Azure App on behalf of an authenticated user.

For more information, see allow SmartHub to accept authentication tokens from other Azure app registrations.
Sorting enhancements The URL for your SmartHub search results will now contain your sort parameters. This allows you to reload or share the results page while maintaining the specific sort parameters. For more information, see How to Sort Search Results.
Results per page You can now select the number of results that you want to return on the search results page by utilizing the ShowRowsPerPage, RowsPerPage, and RowsPerPageLabel content container parameters. For more information, see How to Add the Content Containers Module.
Security hardening Various enhancements were implemented to improve the overall security of SmartHub and it's connections.
SmartHub Analytics component compatibility The SmartHub Analytics component can now be configured with Elasticsearch/Kibana version 8.8.0 and later. For more information, see configure the Analytics component.

Fixed issues

  • The SmartHub Analytics component could only be configured with Elasticsearch/Kibana version 8.7.1 and earlier. (BAI-15576)

  • In some scenarios, when running a search query containing less-than ("<") or greater-than (">") symbols combined with specific dates, incorrect dates were returned. (BAI-14994)

  • The error messages that appeared when running a wild query or complex query with vector search were not descriptive. (BAI-14908)

Smart Previews

August 2025 - Smart Previews 4.1.0.0

System enhancements

Feature Description
Smart Previews in SmartHub Conversational Search

When using SmartHub conversational search, users will now be able to preview the relevant sources that powered the conversational search bot's response. By clicking the Sources button under the response, a list of documents displays. Selecting one of these documents allows users to go directly to the source or preview the document.

When previewing the document, a new panel opens to the right of the conversational search response, opening the preview on the relevant page from the document. For more information on configuring Smart Previews settings for conversational search, see Configure the conversational bot settings in the SmartHub documentation.

Fixed Issues

  • When the figures and table preview feature was enabled, the table button was in an incorrect location and the feature would obfuscate the document preview content for files containing tables and figures.

  • Calls to PreviewStatus have been optimized to improve the performance and efficiency of Smart Previews. (1757149)

  • In some scenarios, document previews for PDF files were displaying as blank pages. (1745449)

  • Various output issues were present in generated document previews. Previews may have had missing text elements, images, or labels. Additionally, certain images may have rendered incorrectly or were obfuscated. (1727589)

  • In some scenarios, documents were failing to be previewed due to a "memory limit exceeded" error. (1735886/1705857)

  • In some scenarios, previews were not generated for documents due to a conversion error. (1748565/1705857)

April 2025 - Smart Previews 4.0.0.0

System enhancements

Feature Description
Smart Previews licensing enhancements

In Smart Previews 4.0.0.0, a new licensing module for on-premise deployments has been introduced to validate the status of your Smart Previews 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 Smart Previews subscription.

When your license is close to expiring, the Smart Previews 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 Smart Previews administration portal, however, Smart previews will stop displaying any document previews and a license expired error is returned on all API calls.

For more information on adding your license to your Smart Previews environment, see Adding your Smart Previews license.
Manged Identity for SQL database connections support

This release of Smart Previews adds support for managed identities authentication. Smart Previews is now able to connect with the Smart Previews database in the following authentication methods:

  • Microsoft Azure Active Directory username and password authentication

  • Microsoft Azure Active Directory Integrated authentication

  • Microsoft Azure Active Directory Service Principal authentication

  • Microsoft Azure Active Directory Managed Service Identity (MSI) authentication

For more information, see Enabling managed identities.
Support for Amazon storage Admins can now select Amazon Storage as their storage type when creating configuration databases for Smart previews for SmartHub and SmartPreviews for SharePoint O365.
Smart Previews Hybrid configuration Admins can now configure Smart Previews hybrid and fetchers settings through PowerShell. For more information, see modifying your Smart Previews Hybrid configuration using PowerShell.
Support for custom actions Admins can now configure custom actions that users can perform on selected text in their generated previews. For example, a custom action could be configured to add selected text to a database. For more information, see Applying custom actions to selected preview text.
Search Inside enhancements Users can now use quotation marks ("") when searching inside their document previews to use exact keyword matching rather than stemming for search inside results. This allows users to be more precise with the terms that they are searching for in previews. For more information, see the key features listed in About Smart Previews.
Upland Software, Inc rebranding

Numerous UI updates were made for Smart Previews to match the standard Upland Software, Inc format. The following will now match the Upland style:

  • The Smart Previews installation wizard

  • The Smart Previews end user license agreement (EULA)

  • The Smart Previews administration portal UI
SMask (Soft Mask) support Smart Previews can now use SMask functionality for PDF rendering. This ensures that Smart Previews can accurately display assets in PDF documents that incorporate soft masking to produce transparency effects.
Smart Previews Hybrid enhancements You can now modify the Smart Previews configuration through PowerShell. This allows you to programatically update settings, such as individual fetcher settings, through console commands. For more information, see Modifying Hybrid configuration using PowerShell.

Fixed Issues

  • If you didn't specify environment variables for password encryption when you installed and set up the Smart Previews Import Server, only the configuration database will be encrypted when you add or change the environment variables. (BAI-15190)

  • If your Smart Previews web services authenticated through Smart Hub with Azure storage, sections of a preview that were saved to the users workspace would not load. (BAI-12087)

  • Previews were not regenerated when the LastModifiedTime value was more recent than the date associated with the preview in the database. (BAI-10884)

  • When Smart Previews for SharePoint was configured on a SharePoint Subscription Edition Server, the Smart Previews service did not appear in the farm features/service section of SharePoint after the SharePoint Solution Packages (.wsp) were uploaded and deployed. (BAI-9651)

  • Smart Previews did not support pattern cell fill in OpenXML. (BAI-9633)