Documentation Index

Fetch the complete documentation index at: https://help.hyperscience.ai/llms.txt

Use this file to discover all available pages before exploring further.

V43 Release Notes

Prev Next

Versions 43.0.x are available to SaaS customers only.

43.0.3 (5 Jun 2026)

Releases

Fixed

Locking releases with "duplicate layouts" — We've fixed an issue that prevented releases from being locked when they contained layouts where the Blanking tool was used. In these situations, an error message falsely indicated that the releases contained duplicate layouts.

Training Data Management

Updated

Improved training data table CSV exports — Training data table CSV exports now include status names instead of numeric status codes and provide layout names alongside layout version identifiers. These changes make exported data easier to review, filter, and analyze. We've also updated exports to include only the most relevant columns for each model type, resulting in cleaner and more focused CSV files.

43.0.2 (21 May 2026)

Custom Supervision

Fixed

Required document metadata fields — Document metadata fields marked as required in Custom Supervision tasks can no longer be left empty when completing a task. This update improves validation for tasks that rely on required metadata input and helps prevent incomplete submissions during review.

Reporting

Updated

New CSV files in the Usage Bundle — We've added the following CSV files to the Usage Bundle:

  • entry_accuracy — Includes data on the daily accuracy of Identification and Transcription tasks based on QA results. This data is grouped by flow and layout and differentiates between tasks performed by the machine and those performed by keyers.

  • classification_qa_layout_revisions — Provides the names of the Semi-structured layouts predicted by the system and the layouts chosen by keyers during Classification QA. Its data is grouped by flow and layout.

Infrastructure

Fixed

Podman 5.6.0 compatibility during container startup — We’ve fixed an issue where deployments using Podman 5.6.0 could fail during container initialization due to changes in the Podman API behavior. This update improves compatibility with Podman 5.6.0 environments and helps prevent startup failures during deployment.

43.0.1 (9 May 2026)

Notifications

Updated

Hiding previously viewed notifications — To increase the visibility of unread notifications, we've divided the notifications in the Notifications panel into Unread and Read sections. The contents of the Read section are hidden by default but can be revealed by clicking on the Read section heading.

Layouts

New

"Notes" setting for fields in a Structured layout — We've added a Notes setting in the Layout Editor for fields in Structured layouts. These field-specific settings are optional and can be used to record information on the field's contents for your team's reference and for use in custom flows.

Training Data Management

Updated

Contents of "Actions" drop-down lists for Classification, Field Identification, and VLM Field Extraction training data — We've updated the training data Actions drop-down list for Classification, Field Identification, and VLM Field Extraction models for consistency across the three model types.

Fixed

Scope of bulk deletion of training data — We've fixed an issue that caused all training documents for a model type (e.g., VLM Field Extraction) to be deleted when a user requested the deletion of all training documents for single model.

Cases

Updated

Data in "Stats" card on the Case Details page — We've updated the Stats card on the Case Details page to include the following data:

  • Total documents

  • Completed documents

  • Total submissions

  • Completed submissions

  • Halted submissions

These statistics provide more information on the status of a case's submissions, making it easier to understand the status of the case as a whole.

Flow-based permissions and access to cases — Access to cases is now determined by the flow-based permissions for each case's submissions.

As part of this update, we've made following changes to the Cases user experience:

  • Cases page

    • If a user does not have access to any of a case's submissions, the name of the case will be grayed out on the Cases page, and they will not be able to click on the name of that case.

  • Case Details page

    • Users are not able to interact with documents, unmatched pages, and data types that flow-based permissions restrict their access to.

    • Deleting a case or editing its deletion date requires access to all pages in the case.

    • Updating Notes for a case requires access to at least one page in the case.

  • Cases API endpoints

    • Documents and unmatched pages are redacted in responses.

    • The contents of submission_files and submissions elements are filtered based on the permissions for the submission's flows.

    • A 403 response is returned if the user has no access to any of the case's pages.

    • Responses from the Listing Cases endpoint omit information cases that are inaccessible to the user.

Fixed

"Show layout information" icon for users without the View Layouts permission — We've fixed an issue where the Show layout information icon on the Case Details page was shown to users who did not have the View Layouts permission. When they clicked on the icon, an authorization error occurred.

Custom Supervision

Updated

Viewing a bounding box for a single field — We've added a Toggle focused bounding boxes button to Custom Supervision tasks. When enabled, only the bounding box for the field selected in the right-hand sidebar is shown on the document. This option improves the readability of documents where the bounding boxes for multiple fields overlap.

Reporting

Updated

Flow-level Classification accuracy data in the Usage Bundle — We've added a classification_accuracy CSV file to the Usage Bundle's product_analytics folder. This file indicates the number of pages whose classifications were checked during Classification QA during the reporting period and how many of those classifications were correct. The data is provided at the flow level.

43.0.0 (6 May 2026)

Highlights

A leader in intelligent document processing, Hyperscience strives to consistently add value, drive innovation, and improve the user experience with every new version of Hypercell. As such, we’re introducing the following key features in Hyperscience v43.

Flow Studio

Flow Builder — With the Flow Builder in Flow Studio, you can add and delete blocks from a flow directly in the application, eliminating the need to edit the flow's code to make these updates. If your flow has Code Blocks, you can update the code for those blocks in the application, as well. As a result, the Flow Builder allows you to experiment with new flow blocks and iterate quickly on your changes.

You can access the Flow Builder by toggling the Build Mode switch in the upper-left corner of the flow's canvas. When this switch is in the ✔ position, Add block (+) buttons appear in the flow where you can add blocks.

Clicking on an Add block button reveals options to add flow controls, like Routing or Output Blocks, or blocks that are included in the Document Processing subflow. You can also click Get More Blocks to download additional sets blocks from the Flows SDK documentation.

When you click on a block, you can edit the block's settings. For some settings, you can specify the output of any preceding block as an input.

If you need to delete a block, you can click on the Delete button that appears above it.

Note that this feature does not replace the Flows SDK; you can still use the Flows SDK to create and edit flows.

For more information about the Flow Builder, see Editing Flows in Flow Studio.

Upgrade notes

These updates may impact your upgrade process or affect initial processing times after upgrading. For more information or assistance, contact your Hyperscience representative.

Python versions

Supported Python versions — Beginning in v43, the use of Python 3.11 in flows, including Code Blocks and external Python packages, is no longer supported. For more information on supported Python versions, see Developing Flows.

Submission retrieval storage

Deprecation of OCS (Open Computer and Software Inventory) submission retrieval storage — We are deprecating support for OCS submission retrieval storage in v43. If you are using an OCS submission retrieval store, you need to migrate to another storage option before support for OCS ends in v46.

For information on supported options for submission retrieval storage, see Submission Retrieval Storage Overview.

Additional features and enhancements

User experience

Login banner in FedRAMP deployments — We've added a banner to the Hypercell login page in FedRAMP deployments, which contains messaging required for government information systems. This banner appears above the Username and Password fields on the login page.

Models

Open list view filtered to a single task — You can now open the model list view pre-filtered to a single task (e.g., Field extraction, Field location) using URL parameters. This feature allows you to share links that take users directly to specific task content. The page and tab behavior have been updated to ensure the view renders correctly when scoped to a single task.

Training Data Management

View group information in the annotations page — You can now view group information directly in the annotations page for Identification models. Groups are assigned during Training Data Analysis, which organizes similar documents based on patterns in text and layout. This update makes it easier to review grouping behavior and validate your training data without interrupting the annotation process.

To learn more, see Training Data Analysis.

Managing document tags from the annotations page — You can now add, edit, and remove document tags directly in the annotations page for Classification, Identification, and VLM Extraction models. This update allows you to manage tags while reviewing documents, without switching back to the Training Data table.

For more information, see TDM for Classification Models, TDM for Identification Models, and TDM for ORCA VLMs.

Exporting training data table to CSV — You can now export training data table for Classification, Identification, and VLM Extraction models as a CSV. Doing so allows you to bulk download your training data table and work with the dataset outside the system. You can export the entire training data table or a selected subset of rows. The exported data includes all table columns, along with a link to each document’s ground truth item.

More information can be found in TDM for Classification Models, TDM for ORCA VLMs, and TDM for Identification Models.

VLM field extraction annotation experience — We’ve improved how bounding-box adjustments update transcriptions in the VLM field extraction annotation experience. Each transcription now reflects all text included in its bounding box.

To learn more, see TDM for ORCA VLMs.

VLM field extraction renaming — Model names can now be updated directly in the VLM field extraction Model History table. This feature allows you to rename VLMs without creating new entries, improving clarity and consistency when managing model versions. Changes apply only to the model name and do not affect the underlying model configuration or history.

For more information, see TDM for ORCA VLMs.

Flows

Configurations for low-latency processing — We've introduced a set of ".env" file variables that can be used to reduce latency in the processing of submissions. Note that the values of these variables should be changed only on the recommendation of your Hyperscience representative.

To learn more about the available ".env" file variables for low-latency processing, see Reducing Submission Latency.

Flow Blocks

Document Renderer Block includes download URLs in submission output — The Document Renderer Block now includes rendered document metadata directly in each document within the submission output. The metadata includes a download URL for each rendered document. This update eliminates the need to customize flows to generate the download URLs.

file_uuid removed from Submission Bootstrap Block output — We’ve removed the file_uuid field from page-level output in the Submission Bootstrap Block. This field was previously interpreted as a file identifier, which led to incorrect usage in some scenarios. Access to the original file remains available through the origin object.

Full Page Transcription raw_segments output removal — We’ve removed support for returning raw_segments in Full Page Transcription Blocks. This update reduces output size and improves performance, especially for text-dense documents. Raw segments are still available and can be accessed separately using the provided segment identifier.

Improved custom entity detection across lines and pages — The Entity Recognition Block now supports detecting entities that span multiple lines or pages. This update improves detection accuracy for real-world documents where values are often split across lines or continued on the next page.

For more details, see Entity Recognition Block.

Submissions

Support for BMP and GIF files — We've added support for the processing of BMP and GIF files in Hypercell.

More information about supported file types can be found in the What is a Submission? article.

Classification

Visual indication of expected document pages — When creating new documents manually, the page editor now shows page boxes that indicate how many pages are expected. These boxes guide you when working with layout variations that contain multiple pages. They are visual aids and do not restrict adding additional pages.

To learn more, see Structured Document Classification.

Flexible Extraction

Field location overlay on documents — During Flexible Extraction for Structured documents, field locations are now displayed directly on the document to guide data entry.

  • For registered pages, field locations are shown precisely.

  • For unregistered pages, approximate locations are indicated.

Selecting a field in the right-hand sidebar highlights its corresponding location on the document.

For more information, see Flexible Extraction.

Custom Supervision

Validating Submission objects — We've added a submission-validation step to the Custom Supervision Block, which checks the contents of the Submission object and halts the submission if the fields required for Custom Supervision tasks are missing or invalid. If the submission is halted as a result of this validation, a detailed error message is provided that describes why the validation failed.

To learn more about Custom Supervision, see the Flows SDK documentation.

Adding and removing table rows — Keyers can now add and remove table rows during Custom Supervision tasks. By right-clicking on a table or using keyboard shortcuts, keyers can delete a specific row or all rows in the table. They can also insert a row above or below a selected row. This update makes the Supervision user experience more consistent across types of Supervision tasks, helping to increase keyer efficiency.

For more information about Custom Supervision, see our Flows SDK documentation.