Queue Configuration

Queue Configuration

The queue configuration helps the user to set up and manage queues. Queues are used to store and manage items fields, often in a First-In-First-Out (FIFO) order, for processing by robots. It can be customized to meet the needs of the user, such as setting different priorities, limits, and expiration times for different types of work items.

Proper queue configuration and management are essential for orchestrating complex processes efficiently and ensuring that your robots work seamlessly.

How to configure queues for your project?

The users will be able to configure the queues after fields has been set up. Follow the below documentation to walk through the Queue configuration page.

Queue Types

There are 6 queue types in which the fields are configured to set rules. Each queue type has its own set of parameters and rules that can be configured. This makes it easier to manage workload and keep the robots running smoothly. Additionally, queues can be used to manage exceptions and errors, ensuring that any issues that arise are handled quickly and efficiently.

Use Case

The following illustration helps you to understand how to configure queues against the project.

In this scenario, the input will consist of an Excel file containing a list of OS details. Using the information provided, including the OS type, RAM, HDD, and Applications, the server is to be created. Once the server creation process, specific to the relevant OS, is completed, it must be recorded back into the Excel file. The fields and queues can be established according to our specific use case. Here we are continuing the process from field configuration step.

Now let’s configure the queues:

The following steps helps you to set up the queues in your project.  In our specific use case, 6 queues need to be created and configured.

Queue 1 – Processing:

The processing queue enables the transactions to move into process for execution of the automation. The fields that need to be processed can be configured. Let’s see how this works. After setting up the fields, they need to be managed with rules during the automation process. This processing queue will move the transactions into the execution process to initiate the automation. Follow the below steps to create a queue name for processing queue.

1. Select the project in which you want to configure the Interact. Here chooses the project as “Server creation”.
2. Navigate to the “Smart Interact” at the left-hand side of the page.
3. You will be directed to the project configuration page.
4. Select the queue configuration step.
5. Choose the queue type as “Processing” from the drop-down list.
6. Enter the queue name as “FetchData”.
7. Select the “Click here” option on the queue access to provide the access to the users available in the project. (Refer queue access to know more).
8. Select the “Click here” option on the field Access to configure the fields to process. (Refer field access to know more).
9. Select the regex script and add script against the field name. (Refer custom scripts to get detailed information).
10. Select the Custom script and provide the javascript for the fields to process. 

Queue 2 – Harmony AI:

Harmony AI refers to the process of extracting meaningful information from structured & unstructured documents, such as text files, PDFs, images, and scanned documents.
This framework will facilitate the processing of incoming files, from file digitization to extracted information validation, all in an open, extensible, and versatile environment. It helps combine different approaches to extracting information from multiple document types. The main aim is to make the process of extracting data as easy as possible: creating one single workflow that will extract data from a variety of documents. The acceptable cards are Aadhar, PAN card, Voter card and driving license. Follow the below steps to create a queue name for business exception. Here we are continuing from Fetch data queue.

1. Select the project in which you want to configure the Interact. Here chooses the project as “Server creation”.
2. Navigate to the “Interact Workflow” at the left-hand side of the page.
3. You will be directed to the project configuration page.
4. Select the queue configuration field.
5. Choose the queue type as “HarmonyAI” from the drop-down list.
6. Enter the queue name as “Aadhar Card”.
7. Click here to know about the queue access for the fields.

How to upload the cards for processing through Harmony AI?

1. Select the “click here” on the Harmony AI.
2. A pop-up will appear on the window.
3. Upload the sample Aadhar card to be processed by the bot.
4. Click on the upload option and select the file from the local system.
5. Once the file has been uploaded, the type will be automatically chosen as “Aadhar card”.
6. Click on the Get taxonomy button to extract the details from the provided Aadhar card.

Queue 3 – Business exception:

The business exception refers to a situation where the workflow process is disrupted due to unexpected or abnormal conditions that occur while the bot is executing the automation. These exceptions can be caused by various factors such as data errors, system issues, user interactions or any other unexpected events that the bot may encounter while execution. To notify these exceptions to the user, the cases can be automated to move to business exception queue so that the user may take actions to prevent this in future. Follow the below steps to create a queue name for business exception. 

Queue 4 – System Exception:

The system exception refers to an unexpected error or issue that arises from the underlying technical systems or software applications with which the bot interacts. Unlike business exceptions, that re related to deviations from normal business rules or processes, system exceptions grow from problem like software crashes, connectivity errors, server downtime or any other technical glitches that disrupt the automation workflow. To notify these exceptions to the user, the cases can be automated to move to system exception queue so that the user may take actions to prevent this in future. Follow the blow steps to create a queue name for system exception. 

Queue 5 – Rejected:

The transactions which do not have sufficient information or incorrect data to proceed with the automation process can be categorized under rejected queue. These transactions need to be manually verified to check the accuracy of the data provided. If the data is accurate, then these transactions can be re-processed. Otherwise, the transaction can be cancelled. Follow the blow steps to create a queue name for Rejected. 

Queue 6 – Completed:

Once all automation process has been completed successfully and performed the required tasks, the transactions can be moved to completed queue. This queue enables you to view the completed transactions on the Manager portal. Follow the blow steps to create a queue name for business exception.