...
Screen Change Detection
...
1
...
1 Work Unit is used for every UI (User Interface) screen that needs detection.
Example: Entering values into a screen with 1 or more textboxes and buttons uses 1 Work Unit credit by default.
Depending on changes in the screen, this value may increase from 1 Work Unit to 2 or more.
Each time the UI changes and Aura must detect controls again, this costs 1 additional work unit for that ‘re-detection’.
10 or more Work Units are used for every PDF or Image file that is extracted from.
If a command is used to explicitly extract from a file, such as a PDF or Image, then Work Unit credits are used.
Example: Extracting content and values from an image or PDF file will use at least 10 credits. If the image or PDF file has many pages or the automation uses a command to auto-generate field values, additional Work Units are applied.
1 Work Unit is used for every Web Page that is extracted from.
If a command is used to explicitly extract from a website page, then additional Work Unit credits are used.
Example: Extracting text and table data from a web page will use additional Work Unit credits.
”Extract from $website” command would extract all contents from a website form into auto generated variable key-value pairs, this also includes tabular data, which are auto converted into datatables (see below).
10 or more Work Units are used for every Datatable that is extracted from.
If a command is used to explicitly extract from a datatable in a web or non-web application, then 1+ Work Unit credits are used.
Example: Extracting table data from a User Interface will use 1 Work Unit credits.
”Get datatables” command would extract all tabular tables on the screen (or image or pdf file provided) automatically into datatables.
...
Function
...
Cost in Work Units
...
Details
See table below for breakdown of Work Unit costs.
Cognillo Hosted** | Customer Hosted *** | ||
|---|---|---|---|
Function | Cost in Work Units | Cost in Work Units | Description |
Screen Change Detection | 1 | 1 | Used to detect screen text and controls in user interface. If the UI changes, a redetection occurs and will use work units as listed here. |
Extracting from Web page (Azure Form Recognizer) | 10 | 1 | If using the ‘Extract from’ command, and Azure Form Recognizer option is enabled, Aura will extract all text, table data and key-value pairs from a web page, and automatically generate variables for them. This could be a web page or any application with data that must be extracted, such as a web form. |
Extracting from Web page (Base64) | 20 | 1 | If using the ‘Extract from’ command, and Base64 option is enabled, Aura will extract all text, table data and key-value pairs from a web page, and automatically generate variables for them. This could be a web page or any application with data that must be extracted, such as a web form. |
Getting Table Data / Extraction (Azure Form Recognizer) | 10-20 | 1 | If user uses the ‘Get Datatables’ command is used, and Azure Form Recognizer option is enabled, this will auto detect all tables on the UI and store them as datatable variables. By default, both Azure Form Recognizer and Base64 options are used for optimal results. |
Getting Table Data / Extraction (Base64) | 20 | 1 | If user uses the ‘Get Datatables’ command is used, and Base64 option is enabled, this will auto detect all tables on the UI and store them as datatable variables. By default, both Azure Form Recognizer and Base64 options are used for optimal results. |
PDF & Image Extraction (Azure Form Recognizer) | 10 per page | 1 | Used to detect all text in PDFs and Images, providing user with key & value pairs automatically. This also automatically creates datatables from tables in a PDF or Image. By default, both Azure Form Recognizer and Base64 options are used for optimal results. |
PDF & Image Extraction (Base64) | 20 per page | 1 | Used to detect all text in PDFs and Images, providing user with key & value pairs automatically. This also automatically creates datatables from tables in a PDF or Image. By default, both Azure Form Recognizer and Base64 options are used for optimal results. |
All other commands | 0 | 0 | All other commands used for automations do not use additional work units. |
** Cognillo Hosted - Microsoft Azure Form Recognizer and Base64.ai are provided through Cognillo hosted services.
*** Customer Hosted - (Available only with Professional & Enterprise Editions) Customer subscribes to Microsoft Azure Form Recognizer and/or Base64.ai subscription services directly and inputs the endpoints from their subscription into the Aura Worker(s).
How can we reduce Work Unit credits used?
You can significantly reduce the number of Work Unit credits used by purchasing the Professional or Enterprise versions of the Aura Digital Workforce product, and configuring to use an on-premises deployment, or a customer hosted cloud deployment.
Once you have deployed the Aura Digital Workforce bots on-premises or to your cloud environment (such as Azure tenant), you need to configure the Aura Digital Worker settings to point to your on-premises or cloud hosted server(s).
Typically, this will reduce the number of Work Unit credits used by about 30-50% to give you more usage out of your Aura Digital Workers
subscribing to Microsoft Azure Form Recognizer and/or Base64.ai subscription services directly.
If you need further assistance, please contact us.
...