If you want to use Hyperscience to automate the processing of submissions in multiple languages, keep the following details in mind during your planning efforts.  For more information on the languages Hyperscience supports, see Supported Languages . Multiple languages within a submission When a submission is ingested into Hyperscience, the system matches its pages to one or more layout variations for automation. Each set of pages matched to a layout variation becomes a document , and each layout variation has a single language assigned to it. Therefore, each document within a submission can be automated in a single language, but each submission can include documents in multiple languages (e.g., two French documents and one English document). To learn more about creating layouts, see Creating Structured Layouts , Creating Semi-structured Layouts , and Creating Additional Layouts . Using a layout across languages Hyperscience does not support the use of duplicate layouts in an …

Aug 8, 2025 - Helm Chart 12.0.0 Release Today we release version 12.0.0 of our Helm Chart. In this version, we’ve removed multiple configuration keys from the values.yaml file that have been deprecated for several releases. Before you upgrade, make sure you are no longer using these keys. A list of the removed keys and their replacements appears below. app.nodeAffinity.platform , replaced by app.nodeAffinity .app.nodeAffinity.trainer , replaced by trainer.nodeAffinity .app.nodeSelector.platform , replaced by .app.nodeSelector .topologySpreadConstraints , replaced by .app.topologySpreadConstraints and .blocks.topologySpreadConstraints resources.idp_sync_block_process , replaced by resources.idp_sync_manager July 14, 2025 - Helm Chart 11.0.0 Release Today we release version 11.0.0 of our Helm Chart. No actions are required to upgrade. The default Hyperoperator version has been upgraded to 7.0.0. It changes the Trainer resource from a Job to …

Accessing the features mentioned in this article Your access to some of the features mentioned in this article depends on your license package and pricing plan. To learn which features are available to your organization and how to add more, contact your Hyperscience representative. In v41, models for flows created in v39 and above are forward compatible , meaning that you can use them in v41 without having to retrain them during the upgrade process. As a result, forward-compatible models allow you to: upgrade v39 or v40 models after upgrading the application to v41, maintain the automation levels achieved in v39 or v40, and continue existing training efforts for any use cases that may be in implementation when upgrading to v41. Which models are forward-compatible In v41, the following types of models are forward-compatible: Identification models Classification models The following types of models are not forward compatible, so …

Each connection in an Input or Output Block has two types of settings: Connection-specific settings, which vary by connection and are described in Input Blocks and Output Blocks , and  Universal settings: Block Details – common across all blocks. See Flow Blocks for more information . Submission Processing Settings – common across all Input Block connections. Payload Options – common across all Output Blocks. Universal settings can be found in the bottom portion of a connection’s settings.  Submission Processing Settings When adding or editing a connection for an Input Block, you can configure any of the settings below. Task Restrictions If you want to make sure that only certain users can perform Supervision tasks on this connection's submissions, you can define task restrictions for the connection based on your permission groups. After you have created a task restriction in the Users section of the application, you can select it from the Task …

process to determine the "correct" answer. For more information on the consensus process, see  Scoring Transcription Accuracy  and  Scoring Field Identification Accuracy . This QA data is used to improve transcription accuracy and reduce manual intervention by identifying patterns in the data. For more information on this, see Transcription Settings . QA for Semi-structured Documents For Semi-structured documents, individual documents are sampled according to a configurable sample rate and put through a QA process to measure Field Identification accuracy. For more information on this process, see the article  Field Identification Quality Assurance . This document-level QA data is also used for training models to automate Field Identification of Semi-structured documents. For more information on training models, see Training a New Field Identification Model .

the message queue is being run. Exchange Yes The exchange that the connection should send messages to. Routing Key Yes The routing key that the connection should add to messages before sending them to RabbitMQ. Setting up Message Queue Notifier Initial setup for all Message Queue Notifiers These steps apply to all supported Message Queue Notifier Blocks.  Log in to your Hyperscience instance. Navigate to Flows and choose any flow. Scroll to the end of the flow in the Flow Studio and click Outputs . Click Add and select Message Queue Notifier Output Block from the list. Click the Add Connection button. Configure the payload options – API Version , Export Type , and Routing Filter . From the Message Queue Type drop-down menu, select your Message Queue Type. Follow the additional configuration steps outlined for your Message Queue Type in the Connection-specific configurations section below. Connection-specific configurations In addition to the …

Each area of the application can be accessed by clicking on it in the left-hand sidebar or in the navigation bar across the top of the application. These options will be shown on all application screens, except for the Supervision and QA task views, the Layout Editor, Flow Studio, and the Release Editor. Below is a list and summary of each part of the application, along with the types of users who would typically use that specific area. The interface Navigation section Section purpose Users Perform Tasks tab ( Tasks > Perform Tasks , or click on the Hyperscience logo) Provides keyer access to manual tasks awaiting completion. System Admin, Business Admin, Data Keyer Admin, Data Keyer, Knowledge Worker Tasks Overview tab ( Tasks > Overview ) Displays metrics on in-progress and recently completed work. System Admin, Business Admin, Data Keyer Admin, Data Keyer, Knowledge Worker Task Queue  ( Tasks > Task Queue ) Lists outstanding …

Accessing the features mentioned in this article Your access to some of the features mentioned in this article depends on your license package and pricing plan. To learn which features are available to your organization and how to add more, contact your Hyperscience representative. The Model Management page allows you to see a list of all models trained on this instance. In this article, you'll learn how to navigate the pages for different types of models. To access the Model Management page, go to Library >  Models . Choose which type of models you want to see from the drop-down menu: Identification Models - Field ID or Table ID models Classification Models Learn how to manage your Identification and Classification models in our Training Data Management article. Text Classification Models Transcription Models Identification Models table Identification models are the default selected option in the drop-down menu at the top of …

Having a diverse, representative training set is crucial for a high-quality identification model. In v37, the Hyperscience application allows you to train a model with fewer annotations with minimal impact on performance.  How data is curated The Training Data Curator labels each training document as having high or low importance. The importance is calculated by determining which data would best contribute to the model’s performance. For each group of documents, the system labels the most impactful documents as having high importance.  Before using the Training Data Curator, make sure that you've: uploaded at least the recommended number of documents. The default minimum value is 100. Upload a diverse and representative sample of documents to achieve robust model performance. The goal is to improve the efficiency of the annotation process by requesting an optimal subset that reflects the variety of documents you expect to automate with the model …

Issue A page is incorrectly matched to a Structured layout. Affected versions All versions Affected configurations All configurations Causes The desired layout is not part of a live release. Duplicate or very similar layouts are part of a live release. Recommendations Make sure that the desired layout is part of a live release. Make sure that the page is exactly the same as the layout. Check for duplicate layouts. If there are multiple similar variations of a layout in a release, use layout identifiers to uniquely identify each variation and increase the machine’s confidence. Make sure that you use the same number of layout identifiers across all variations of a layout. To learn more, see " Best Practices for Using Layout Identifiers" ( v38 | v39 | v40 | v41 ) .

X,XXX.XX String beginning with an amount ending with a decimal and two digits, followed by a space and currency code or symbol if present This currency format is to be used when expecting multiple types of currencies (e.g., USD and EUR) in a given field. The normalized value will start with the amount, and it will use a dot to separate up to two decimals. If the figure is surrounded by parentheses, the value will be normalized to negative. Any currency code or symbol, if present, will be appended to the amount after a space. In the absence of a currency code or symbol, no space will be included. Supported currencies include $, €, £, ¥, all ISO abbreviations, and currencies written with Latin-based characters. Alphanumeric, all special characters allowed "USD 200" or "200USD" "200.00 USD" Currency with Unit - X.XXX,XX String beginning with …

Upgrading from previous versions If you are migrating data or upgrading from a version of Hyperscience that had "High," "Default," and "Low" priorities for submissions, we will assign deadlines as described in Upgrade Considerations and Known Issues . Migrating layouts Moving your Hyperscience layouts from one instance to another may affect your submission-processing deadlines. To learn more, see Importing & Exporting Settings . Next steps To learn how to edit the system-level SLA rule, see Application Settings Overview . To learn how to configure SLA rules for submissions based on their flow and Input Block, or layout variation, see SLA Rules Tab . To learn how to configure SLA rules from a layout details page, see Layout Priority .

This article walks you through the steps required to integrate your AWS Secrets Manager with Hyperscience. Configure AWS Secrets Manager To configure the AWS Secrets Manager integration, follow the steps below: Determine and configure your authentication scheme with AWS. If you’re using a Virtual Private Cloud (VPC) in AWS in which your EC2 machines use IAM roles with access to secrets, no additional configuration may be required for this step. If you’re using an access key approach with a pair of AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY keys, you’ll need to configure authentication. To learn more about environment variables, the shared credential file, and the AWS config file, see the “ Configuring credentials ” section of Amazon’s Boto3 Developer guide. Depending on the version used, the secrets.yml or .secrets file maps any secrets to retrieve the appropriate environment variables. In v32 to v35.0 …

Accessing this feature Your access to the feature described in this article depends on your license package and pricing plan. To learn which features are available to your organization and how to add more, contact your Hyperscience representative. With the Kafka Listener, you can integrate your Apache Kafka deployment with Hyperscience, allowing you to take advantage of Kafka’s low-latency, high-throughput messaging capabilities in your submission-creation process. When you set up a Kafka Listener connection in a flow’s Input Block, the Listener ingests messages from the Kafka topics you specify and creates submissions from those messages. Sample use cases I send submission information from external systems to a Kafka topic. I want to ingest that information into Hyperscience so I can create and process submissions there. My customers post relevant documents to a set of Kafka topics. I want to then ingest these documents into Hyperscience …

Your flow can have the following types of Transcription tasks: Field Transcription, Table Transcription, and Flexible Extraction. A Field or Table Transcription task can be generated in the following ways: The machine's transcription is below the transcription target accuracy thresholds. For more information on how to set thresholds, see Transcription Settings . If a field has Consensus or the "Supervision Always" setting enabled in the Layout Editor. Note that these tasks have escalated priority. Flexible Extraction tasks are generated in the following situations: A Structured page was originally marked as No Layout Found by the machine, but it was later manually matched to a layout in Document Classification Supervision. The code in a Custom Code Block sent a document to Flexible Extraction so a keyer could verify the content of specific fields. The code in a Custom Code Block sent a document to Flexible Extraction so a keyer could …

Overview With the information available in our Flows SDK and the help of your Hyperscience representative, you can include Custom Supervision in your flows. Custom Supervision allows you to tailor a Supervision task’s interface to a specific business process.  You can add multiple custom flows, and each of them can contain a different Custom Supervision logic and interface. Custom Supervision tasks can have their own custom task names. You can access Custom Supervision tasks through the Perform Tasks page, the Task Queue page, the Submissions table, and the Cases table. Prerequisites To enable Custom Supervision, you need to add a Custom Supervision Block to a custom flow with a Custom Code Block. To learn more, see the “Custom Supervision Block” section in Flow Blocks . Custom Supervision task interface The Custom Supervision task’s interface includes a page that contains three vertical panels - left, middle, and right panel. Left panel …