V39 Release Notes

V39 Release Notes

Versions 39.1.x and 39.2.x are available to SaaS customers only.

39.2.19 (23 Apr 2025)

Classification

Updated

Font-rendering consistency in Microsoft documents - We’ve updated the support for Microsoft fonts to ensure consistent rendering of documents, such as .docx, across environments. In previous versions, certain .docx files displayed unexpected layout differences when converted to images, which impacted Structured Classification accuracy in downstream processes. This issue was caused by missing Microsoft fonts that were previously available as part of the LibreOffice library but were removed in later versions of the library. This update improves reliability for classification use cases that are dependent on layout structure.

NOTE: You may notice differences in how .txt files are rendered in v39.2.19 and later. These differences are due to a change in LibreOffice behavior introduced in their March 2025 release, which affects text-to-image conversion when exporting to PDF. To learn more, see LibreOffice documentation (opens in new tab).

39.2.18 (15 Apr 2025)

Updates

This version includes a number of updates that optimize our internal testing and deployment processes.

39.2.17 (6 Mar 2025)

Training Data Management

Fixed

Previewing pages in Training Data Management (TDM) for Classification models — We've fixed an issue that caused delays in loading preview images of pages in TDM for Classification models.

Flows

Fixed

Submission processing and size of database transactions — We've fixed a database-transaction issue that delayed the advancement of submissions through flows.

39.2.16 (19 Feb 2025)

Updates

This version includes a number of updates that optimize our internal testing and deployment processes.

39.2.15 (3 Feb 2025)

Updates

This version includes a number of updates that optimize our internal testing and deployment processes.

39.2.14 (17 Jan 2025)

Updates

This version includes a number of updates that optimize our internal testing and deployment processes.

39.2.13 (6 Dec 2024)

Training Data Management

Fixed

Migration of data to Training Data Management – We've fixed a data-migration issue that caused database deadlocks to occur when training data was sent to Training Data Management. This issue affected data coming from completed submissions that contained more than 500 pages.

Flow Blocks

Updated

"Scope" setting for HTTP REST Blocks – We've added a Scope setting to HTTP REST Blocks, which allows you to specify a scope for requests authorized with OAuth 2.0. This setting is available only if the block's Authorization Type is set to OAuth 2.0 Client Credentials.

39.2.12 (21 Nov 2024)

Updates

This version includes a number of updates that optimize our internal testing and deployment processes.

39.2.11 (19 Nov 2024)

Large Language Model (LLM) Blocks

Fixed

Execution of LLM Install Flow – We've fixed an issue that caused the execution of the Hyperscience-provided LLM Install Flow to fail with the error ModuleNotFoundError: No module named 'authlib'.

39.2.10 (6 Nov 2024)

Updates

This version includes a number of updates that optimize our internal testing and deployment processes.

39.2.9 (25 Oct 2024)

Updates

This version includes a number of updates that optimize our internal testing and deployment processes.

39.2.8 (11 Oct 2024)

Submission Pre-processing

Fixed

Processing of email attachments ingested through the Email Listener – We've fixed a pagination issue in the Submission Initialization Block that prevented email attachments from being ingested through Email Listener connections in some situations.

Layouts and Models

Fixed

Messaging about latest layout and model versions not being live – We've resolved a version-comparison issue that caused incorrect "Latest version is not live" warning messages to appear on the details pages for layouts and models.

39.2.7 (4 Oct 2024)

Connections

Updated

Specifying AWS regions for S3 Notifier connections – We've added an AWS Region setting to S3 Notifier Output Blocks, which allows you to specify the region of the S3 bucket that notifications are being sent to (e.g., us-west-2). Specifying a region helps to prevent location-constraint errors from occurring when attempting to connect to the notifications' S3 bucket.

39.2.6 (26 Sept 2024)

Updates

This version includes a number of updates that optimize our internal testing and deployment processes.

39.2.5 (13 Sept 2024)

Training Data Management

Updated

Contents of Training Data tab for Classification models – To enhance the user experience, we've made the following updates to the Training Data tab for Classification models:

Fixed

Classification training data in exports – We've fixed an issue that caused some Classification training data to be incorrectly assigned to excluded layouts when training data was exported.

39.2.4 (28 Aug 2024)

Training Data Management

Fixed

Responsiveness of Training Data Management (TDM) for Classification after upgrade – We've fixed a data-migration issue that caused deadlocks and delays in TDM for Classification upon upgrading to previous versions of v39.2.

"Download Classification Model and Data" action or TDM for Classification – Because Classification training data cannot be imported to v39.2 of the application, we have removed the Download Classification Model and Data option from the menu in the upper-right corner of the Training Data page for Classification models.

Selecting rows in the tables on the Training Data page for Classification models – We've fixed an issue that prevented users from selecting all of the rows in the Training Data and Excluded Training Data tables. As part of this update, you can now choose to select all rows on the current page of the table or all rows on all pages of the table. In previous versions, only the rows visible in the table could be selected, not rows on other pages of that table.

39.2.3 (19 Aug 2024)

Training Data Management

Updated

Uploading training data for Classification models – We've reduced the amount of time required to upload training for Classification models. To make this optimization possible, the system now performs pre-processing calculations after the upload process is complete and before training begins.

Reporting

Fixed

Generating Field Exception Reports for one-month periods – We've fixed an issue that caused out-of-memory errors to occur when Field Exception Reports were generated for a one-month period in some instances. As part of this update, these reports are now exported as CSV files rather than ZIP files.

39.2.2 (1 Aug 2024)

Models

Updated

Version information on the model details pages for Field Identification models – We've removed the Version column from the Model History table on the model details page.

Custom Supervision

Fixed

Viewing full page images during Custom Supervision – We've fixed a CSS issue that caused portions of page images to be hidden in Custom Supervision. This issue prevented keyers from finding the information needed to complete Custom Supervision tasks in some situations.

Connections

Fixed

CURL_CA_BUNDLE and ActiveMQ connections – We've fixed an issue that caused the ActiveMQ Message Queue Listener and Notifier Output Blocks to fail when the CURL_CA_BUNDLE ".env" file variable did not have a value.

Security

Fixed

Addressing security vulnerabilities in basepython packages – To ensure security, we've updated the following packages to their latest versions:

39.2.1 (17 Jul 2024)

V39.2.x Known Issue

Models

[Addressed in v39.2.2] “Verion” in Model History card – In v39.2.0 and v39.2.1, the Version shown in the Model History card on the model details page does not match the trainer version the model was trained on. We are working to address this inconsistency, and a fix will be included in a future version of v39.2.

Machine Identification

Fixed

Detecting text in Semi-structured documents – We've fixed an issue that prevented the machine from both detecting text and from generating Identification Supervision tasks in certain situations. Instead, submissions would halt in the flow's Machine Identification Block.

LLM Blocks

Updated

"Completion Parameters" setting for OpenAI (ChatGPT) Block– We've added the Completion Parameters setting to the OpenAI Block, which allows you to add parameters for OpenAI’s /v1/chat/completions endpoint to your requests (e.g., {"response_format": {"type":"json_object"}}).

Audit Log

Updated

Changes to activity names – We've edited the names of some of activities for consistency and improved readability.

Authentication

Fixed

Restarting after entering SAML certificate information in “.env” file – We've fixed an issue that caused application restarts to fail after entering values for SAML_METADATA_URL and SAML_METADATA_CERT_PATH in the ".env" file. The issue affected environments with SAML configured as the primary identity provider.

Security

Fixed

Addressing security vulnerabilities – To ensure security, we've updated:

39.2.0 (9 Jul 2024)

Training Data Management

Updated

Reanalyze data– We’ve implemented a new logic for training data analysis. You can now choose one of the following two options:

Ability to ignore anomalies– We’ve enhanced the Anomaly Detection feature by adding an Ignore Anomaly button. If a field is annotated correctly but has been flagged as an anomaly, you can click this button to prevent it from being considered an anomaly during training.

For more information, see Labeling Anomaly Detection.

Model Management page for Identification models– We’ve added more information in Training Data Management (TDM) for Identification models. You can now see the following:

Learn more in TDM for Identification Models.

Projected Automation chart– We’ve re-enabled the Projected Automation chart in TDM for Classification. You can now see the projected percentage of automation based on your target accuracy for Classification models.

Note that the Projected Automation chart appears only if a trained or imported model is available.

Audit Log

Updated

Enhancements to activity records – We’ve expanded and improved the records of activities covered in the Audit Log.

To learn more, see Audit Log (v39.1 and later).

Detailed audit logs saving— Users can now configure where detailed audit logs are saved, with options to send them to the database, standard output, or both. This update ensures that high-volume audit data is managed efficiently while maintaining existing infrastructure for log exports and UI visibility. The change provides greater flexibility in log storage without interrupting document processing flows.

Flows

Updated

Merging of Top-level Flows and All Flows pages – To streamline your access to all available information about your flows, we've combined the Top-level Flows and All Flows pages into a single Flows page. The new Flows page does not contain cards for each of your top-level flows. Instead, all of your flows—whether they be top-level flows and subflows—are listed in the All Flows table. You can filter the table's contents by flow status and tags, and you can sort the flows by flow name, the date and time of last save, status, and deployment date and time.

Flows SDK

New

Exporting multiple related flows as a single ZIP bundle – We’ve created a command-line interface (CLI) tool for the Flows SDK that facilitates the management of flows created with the SDK.

With this new tool, you can export multiple flows defined in Python into a single ZIP bundle, without having to export each one separately as a JSON file. For example, you can export a top-level flow together with all of its subflows, and you can also export all the flows required to implement a complex use case. The ZIP bundle contains a JSON file for each exported flow, along with any uploaded files (e.g., CSVs) that the flows may reference via the File data type. The format of the ZIP bundle is the same as the ZIP file that the system creates when you click Export All Flows for a top-level flow in a Hyperscience instance.

Optionally, Python functions that are used by Code Blocks can also be extracted as separate Python files inside the ZIP archive instead of being incorporated into the flows' JSON files as inline code. This option makes it easier to review the Python code and reuse it as flows are edited and created.

After you've created the ZIP bundle, you can then import it from the Flows page of a Hyperscience instance. Doing so imports all the flows inside it.

Authentication

New

Machine credentials – Our API now supports parts of OAuth 2.0, the industry-standard authorization protocol, for better security. In addition, we have developed a user-friendly interface for managing these credentials. Machine credentials are designed to replace API accounts for most types of programmatic access.

This feature will be enabled by default in a future version of v39.2. To learn more about machine credentials, or to enable the feature in the meantime, contact your Hyperscience representative.

Infrastructure

Fixed

Upgrading Django and its dependencies – To increase the functionality and security of your system, we've upgraded Django to 4.2.12. We've also upgraded its dependencies to the following versions:

Databases

Fixed

Django and inserting rows in Oracle databases – We've fixed a Django-related issue that prevented the django.db.models.functions.Now() function from inserting rows in the databases.

Submission Retrieval Store

New

Support for Microsoft Azure Blob Storage – You can now use Azure Blob Storage as a submission retrieval store. When connected to Azure Blob Storage, the system receives file URLs from Azure, which it then uses to download the files and process them as submissions. You can configure individual flows to ingest data from a blob by editing the Submission Bootstrap settings in each flow.

To learn more about using Azure Blob Storage as a submission retrieval store, see Flow Blocks.

SaaS

New

Monitoring cloud service status – With our new cloud service status page at https://status.hyperscience.net/ (opens in new tab), you can check the health of your SaaS deployment of Hyperscience. The ability to monitor the status of your deployment in near-real time allows you to take swift action to ensure your organization meets its SLAs.

Note that the status page provides general health information for all production deployments of our SaaS offering; it does not include information about the status of specific production deployments or particular system components (e.g., databases, file stores).

To learn more about the cloud service status page, see SaaS Service and Support.

New

License cards in the System & Health page—  SaaS users will now see a new License card on the System & Health page. This card provides information about your license. Note that Hyperscience automatically manages and updates the licenses.

39.1.5 (1 Aug 2024)

Machine Identification

Fixed

Custom Supervision

Fixed

Viewing full page images during Custom Supervision – We've resolved a CSS issue that caused portions of page images to be hidden in Custom Supervision. This issue prevented keyers from finding the information needed to complete Custom Supervision tasks in some situations.

LLM Blocks

Updated

Connections

Fixed

Informative error messages from UiPath Notifier Output Blocks – We've resolved an exception-handling issue In UiPath authentication that made it more difficult to troubleshoot failures in the UiPath Notifier Output Block.

Authentication

Fixed

39.1.4 (3 Jul 2024)

Updates

This version includes a number of updates that optimize our internal testing and deployment processes.

39.1.3 (20 Jun 2024)

Models

Fixed

Using undeployed Identification models – We've fixed an issue that resulted in the continued use of undeployed Identification models in submission processing in some circumstances.

Training Data Management

Updated

Projected Automation chart– We’ve added the Projected Automation chart in TDM for Classification. You can now see the projected percentage of automation based on your target accuracy for Classification models.

Note that the Projected Automation chart is available only if a trained or imported model is available.

Flexible Extraction

Fixed

Transcribing fields in manually reclassified Structured documents – We've resolved an issue that prevented fields from appearing in Flexible Extraction tasks for Structured documents that had been manually reclassified.

Security

Fixed

Addressing security vulnerabilities – To increase the functionality and security of your system, we've upgraded:

39.1.2 (6 Jun 2024)

Models

Fixed

Memory consumption by flows containing several models – We've fixed a memory-consumption issue that caused runtime errors in the Machine Identification Block when processing submissions in a flow for the first time. The issue occurred in flows containing several models, particularly models for nested tables.

Flow Blocks

Updated

Reprocessing Block optimizations – We've updated the implementation of the Reprocessing Block to allow it to both gather available input and generate tasks dynamically, increasing its overall efficiency.

Connections

Fixed

Filename output of attachments ingested through the Email Listener – We've fixed a character-decoding issue that caused filenames of email attachments to appear incorrectly in the output of the Email Listener. The issue occurred when the filenames contained Unicode characters.

SaaS

Fixed

Training of Table Identification models – We've resolved a memory-leak issue that caused the training of Table Identification models to take longer than expected and ultimately fail. The issue primarily affected models for tables containing large amounts of data (e.g., nested tables, tables with a large number of columns).

39.1.1 (23 May 2024)

Training Data Management

Fixed

Showing anomalies in table annotations – We've fixed an issue that prevented detected anomalies in table annotations from being shown in the application in some situations.

Flows

Fixed

Steps in importing flows – We've resolved an issue that resulted in 400 errors at various points in the flow-import process in some instances. The issue was caused by a mismatch between the next step in the process and the step associated with the passed transaction ID.

Machine Classification

Fixed

Image Correction for documents with large, dark areas – We've fixed an issue that prevented Image Correction from detecting the incorrect orientation of documents that contained large, dark areas (e.g., images of checks on a dark background).

Machine Identification

Fixed

Asterisk as custom character for splitting segments – We've resolved an issue with text-segment detection that resulted in IndexError: list index out of range during Machine Identification. The issue occurred when custom_char_for_splitting_segments was set to * in /admin.

Connections

Fixed

Testing for Apex classes in Salesforce Listener connections – We've fixed an issue where test connections for the Salesforce Listener did not verify the presence of Apex classes permissions. The issue resulted in successful test connections for the Salesforce Listener, even when the Listener was not able to ingest submissions.

Authentication

Fixed

Authenticating through LDAP – We've addressed a race condition that prevented users from authenticating through LDAP in some situations.

Kubernetes

Fixed

Supporting multiple Python versions – We've fixed an issue related to our support of multiple Python issues that prevented Kubernetes deployments from starting.

SaaS

Fixed

Passing credentials to authentication functions – We've resolved an issue that prevented authentication functions from being called with a username, password or both. This issue resulted in session-token failures.

39.1.0 (7 May 2024)

Submission Processing

Updated

Using Ghostscript to process PDFs – To reduce the time required to process PDF files in submissions, we've updated the system to use Ghostscript to process PDFs by default rather than Mutool. Mutool is now used as a fallback option only. If necessary, you can reverse the order in which these tools are used by editing the PDF_PAGINATION_LIBS variable in your ".env" file. In previous versions, the system preferred Mutool over Ghostscript, and there was no option to change that preference.

For more information about these updates, see Processing PDFs.

Training Data Management

Updated

Document Anomaly filter- We’ve introduced a Document Anomaly filter in Training Data Management (TDM), which allows you to find documents with anomalies or Model Validation Tasks (MVTs). By activating the filter, you can focus solely on affected documents. Anomalies remain visible until you re-analyze your data, so your team members can review the anomalies at their pace. These improvements help you efficiently address anomalies and improve overall data quality.

Fixed

Page links in warning messages for tables - We've addressed an issue in table-annotation pages in TDM where clicking a page link in a warning message didn't change the focus of the middle panel to the selected page. With this update, you can directly access the mentioned page by clicking its link in the right-hand panel while annotating tables.

Flows

New

Support for Python 3.11 – In preparation for Python 3.9's end-of-life in October 2025, we now support the use of Python 3.11 in custom code, custom flows, and Python packages, as well as the use of Python 3.9. This support ensures the continued security and reliability of your operations as you upgrade your code and flows to use Python 3.11.

The default flows included in Hyperscience have been updated to use Python 3.11. While you can use either or both Python versions in Hyperscience v39.1, we recommend upgrading the entirety of your flows' code to use Python 3.11 as soon as possible.

More information about Python 3.11 support can be found in the PythonBlock (opens in new tab) section of the Flow SDK’s Source Documentation.

Flows SDK

Updated

Flows SDK for v39.1 – We’ve released an updated version of our Flows SDK for v39.1, which includes several enhancements to subflows to make them easier to use.

More information about the new Flows SDK version can be found in our Flows SDK documentation (opens in new tab).

Custom Supervision

Updated

Mandatory transcription fields – You can now mark transcription fields as mandatory when configuring Custom Supervision tasks. Keyers cannot complete tasks with these fields until they provide transcriptions for them.

Note that checkbox and signature fields cannot be mandatory fields in Custom Supervision.To learn more about configuring Custom Supervision tasks, see our Flows SDK documentation (opens in new tab).

Connections

Updated

Universal Folder Listener enhancements— To improve the experience of using the Universal Folder Listener, we’ve made the following updates:

To learn more about these enhancements, see Universal Folder Listener.

Audit Log

Updated

Increased logging of actions in the Audit Log - Audit logging offers enhanced visibility, allowing you to track and monitor actions in your system more effectively. This tracking helps your organization to ensure adherence to security and compliance measures. We’ve expanded the coverage of our Audit Log, starting with SaaS customers, by recording more activities, such as events related to Training Data Management, settings changes, and access to PII data.

To view the Audit Log, go to the Audit Log page ( Administration > Audit Log). You can filter the list of activities by date range, activity name, operator (human or machine), and username. You can also download a CSV file of the filtered list, which contains all of the information shown on the page.

For detailed descriptions of all activities in the Audit Log, see Audit Log (v39.1).

Security

New

Security restrictions on lambda functions – To increase the security and reliability of flows, we've added restrictions to the operations which can be executed in lambda functions.