Table Identification QA tasks are specific to Semi-structured documents with tables. Table Identification QA tasks are part of the Identification QA task queue in Tasks > Perform Tasks .  Note that Field Identification QA tasks are also loaded into the Identification QA task queue. To learn more about Field Identification QA tasks, see Field Identification Quality Assurance . To enable Table Identification QA, you need to: Go to Flows . Click on a flow. Enable Table Identification Quality Assurance in the left-hand sidebar. Click Save . Table Identification QA Sampling Rate Documents that are matched to Semi-structured layouts with tables are eligible for QA sampling. The QA sampling rate can be configured separately for each flow by following the below steps: Go to Flows . Click on a flow. Edit the value for Transcription QA Sample Rate . Click Save . Note that Table Identification QA samples on a document level. For example, if you …

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 …

tudio project, including the XAML definition file, is attached. Import the XAML file in UiPath Studio as a UiPath Activity. The Activity can then be added in larger workflows and set up to process notifications on Hyperscience document submission state changes received on a UiPath Queue. Finally, the Activity should be configured to forward the notification data for further processing depending on your business rules and processes. The following occurs when a UiPath robot executes this workflow: If the queue is empty, the robot waits some time (e.g. 10 seconds) before checking the queue again. If the queue is not empty, a notification is retrieved, acknowledged, and sent for further processing. The contents of the notification are saved in a variable called notification , which is in the format of a Hyperscience submission object as it has been defined in our API documentation . The Flow Switch routes the UiPath robot …

an error, the callback will be called with message_type === MessageType.ERROR and info will be an Error object. Completed tasks - when all tasks are complete, the callback will be called with message_type === MessageType.COMPLETE , and info is an object with Purpose types as keys and the corresponding number of completed tasks as values. One of the following parameters: submission_id: string | number To complete tasks for a given submission ID. document_id: string | number To complete tasks for a given document ID. case_id: string | number To complete tasks for a given case ID. task_uuid: string To complete a specific task. purposes: Array To complete tasks for specific task purposes. You can find an example of the init function below: const hyperscienceCallback = (message_type, info) => { if (message_type === HyperscienceWidget.MessageType.ERROR) { console.error(info.message); } else if (message_type === HyperscienceWidget.MessageType.COMPLETE) { console.log('Tasks Completed …

In the Layout Editor for both Structured and Semi-structured layouts, there are several functions available to assist in creating and editing layouts.  The sections below list the Layout Editor functions that can be accessed via the toolbar above the layout page image, as well as keyboard shortcuts you can use.  For layout drafts that were created using the “Copy to new layout variation” feature, you can see the name of the source layout or layout variation by clicking on the information icon ( ). Note that the layout source information only appears for draft layouts or uncommitted layout variations, not for locked layouts or committed layout variations. Toolbar functions Semi-structured layout editor From left to right on the toolbar: Filter  – search for a field or field group within the layout. Undo  and  Redo  – allows recent changes to fields (resizing or moving bounding boxes, or defining metadata) to be undone or …

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 …

Overview If you create a new Semi-structured layout version, there will be no models immediately available. For optimal layout performance, train a model on the newest layout version. Recall that identification models are trained at the layout level. Increase Field ID model performance (accuracy and automation) by retraining with additional Field ID Supervision and QA documents.  Increase Table ID model performance (accuracy and automation) by retraining with additional documents that have gone through Table ID Supervision and Table ID QA.  The application can be trained on-premise and  deployed to a distinct machine in order to separate model training resources from document processing resources. For more information about this, see  What is the Trainer? Training requirements The document requirements for training Field ID and Table ID models are the same. Field ID uses Field ID Supervision and Field ID QA data, while Table ID uses Table ID Supervision and …

Custom Supervision task. Keyers can use this additional context on the Custom Supervision task’s page as they work on a task. Apply custom decisions To apply custom decisions to fields, table cells, pages, documents, or cases, you can configure custom drop-down menus on the Custom Supervision task. For example, a Custom Code Block can use business logic to approve documents. If the block fails to approve a document, a Routing Block can send this document to Custom Supervision where a keyer can manually review the unapproved document and apply a custom decision to it. Custom decisions for fields, pages, documents, and cases are displayed in the right panel, while custom decisions for table cells are displayed at the bottom of the middle panel inside the table editor. To reveal the decision drop-down menu for a given cell in the middle panel, you need to select the cell …

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 …

2. Create a bounding box for the field’s occurrence. To remove a field’s occurrence, click the Remove occurrence button ( ) next to the occurrence’s name in the right-hand sidebar. To capture additional text segments for a given field, you can add additional bounding boxes. To add an additional bounding box, follow the steps below: a. Click Add another text segment . b. Draw a bounding box for the additional text segment. Note that you can repeat steps 1 and 2 until you identify all text segments of a field. To remove a field’s bounding box, select the bounding box and click its X button. Click Save Changes . To view annotations for specific fields only: Expand the Show Fields drop-down menu at the top of the page. In the drop-down list that appears, select the fields whose bounding boxes you would like to review. View …

after a decimal are mandated, yet the printed vertical line on the underlying template may not always be a reliable indicator of this separation. Values are returned with a dot to separate up to two decimals. If decimals aren't written, the last two digits are assumed to be the decimals. If the figure is surrounded by parentheses, the value will be normalized to negative. Numeric, special character "-" to signify negative amounts, "$" and cents written out by default, entered numbers are expressed right-to-left. "100000" "1000.00" Separated Currency - X.XXX XX String ending with a comma and two digits This currency format expects dots to group thousands and is to be used where two digits after a decimal are mandated, yet the printed vertical line on the underlying template may not always be a reliable indicator of this separation. Values are returned with a comma to separate …

Accessing this feature Depending on your license package and pricing plan, you may not have access to the feature described in this article. To learn which features are available to your organization and how to add more, contact your Hyperscience representative. 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 …

User Experience Tooltips when moving the pointer from one text box to another – When a user hovers over a text box, a tooltip is shown, but when the user hovers over another text box, a tooltip for that text box is not shown. This issue affects various portions of the application, but it primarily affects the Layout Editor for Structured layouts. Using calendars in date filters – Using the drop-down menus in calendars to select different months sometimes causes the calendars to automatically close. Workaround: To select different months, use the Previous ( ) and Next ( ) buttons that are located next to the drop-down menus. Layouts and Layout Variations Multiple live versions of a layout variation – The system allows you to deploy multiple versions of a layout variation across different flows, as it does not perform any validation in this area when assigning a release to a flow. However, since we …

API accounts have been deprecated and will be removed from the platform in a future version. For information on authenticating API requests, see Machine to Machine (M2M) Authentication with OAuth 2.0 . Hyperscience SaaS uses an authentication scheme that requires a client ID and password to authenticate and send API requests. Client IDs and passwords can be obtained on the API Accounts tab in the Users section of the platform. Our API documentation outlines the steps required to connect to your Hyperscience SaaS environment via API. Managing API accounts If you have System Admin permissions, you can create and delete API accounts in the application. You can also create new passwords for API Accounts you've already created.  Creating a new API Account You can create API Accounts for users in a particular permission group. After you've created the account, you will need to distribute the credentials to the …

When you click the Document ID for a submission in the Documents table, you will be taken to the Document Output page. The Document Output page contains the original page image, the machine and manual transcriptions, and some additional details that may assist in debugging and performance investigation. This page has three main sections: the document summary, the field list, and the image viewer. Document summary This section is at the top of the Document Output page and contains the aggregate stats of all pages in that document. This section is hidden by default, so to view this section click on the blue downward arrow next to the document name. Status If there are outstanding Supervision tasks for the document, a link will appear that allows you to complete those tasks. Upon completing the task, you will be redirected back to the Document Output page. If there are no available …

Annotations link. For nested tables, the Table-level Automation table separates the parent and child columns into two subtables. Viewing a table column’s training data If you are interested in reviewing the ground-truth, or training, data for a particular table column, you can do so by following the steps below. Troubleshooting table columns with low automation rates If the Table-level Automation table shows that a particular table column has a low rate of automation, you can troubleshoot it by following these steps. To view a table column’s annotations: In the Automation table, click View Annotations in the table column’s row. View the table column’s bounding boxes in the given document and make any necessary edits, as described in View and edit table column annotations . Click → at the top of the page to see the table column’s bounding boxes on the next available document.

Field Identification QA tasks are specific to Semi-structured documents. All fields’ occurrences and bounding boxes are eligible for Field Identification QA sampling. If the Continuous Field Locator model improvement setting is enabled in the "Identification" section of Administration > System Settings , Model Validation Tasks will also be loaded into this queue. These tasks look identical to Field ID QA tasks. For more information about these tasks, see Model Validation Tasks . To start a Field Identification QA task, follow these steps: Go to  Tasks > Perform Tasks . In the  Quality Assurance Tasks  card, click  Perform Tasks  for  Identification QA. In order to improve performance, it is imperative to perform QA tasks using the best practices. For more information on these, see  Best Practices for Field ID Supervision and QA . Field Identification QA tasks During Field Identification QA, you need to review all fields that are sampled for QA within a document and …

all submissions created in three versions before your target version must be completed. The table below outlines the compatibility between submissions and versions of Hyperscience. Before upgrading to… …submissions from this version must be completed: v35 v32 V34 V31 V33 V30 V32 V28 (there is no V29) For example, before upgrading to v35, any submissions created in v32 need to be completed in v32, v33, or v34. There is no filter in the application to determine which submissions were created in which versions, but you can look for older submissions in one of the following ways:  Use the submission date and the dates in your upgrade history as a guide — For example, submissions created in v28 or earlier have a Submission Date that predates your upgrade to v30 or v31.  Check Administration > Jobs — You can use the Legacy Jobs view of the Jobs table to find submissions created in older …