
Queue Manager
Queue Manager Overview
Features
The queue is implemented using a transactional database (MySQL or Microsoft SQL Database). This ensures that a task is pulled only once for processing. There can be multiple queues differentiated by the name of the robot that processes the tasks.
- Robots will either add tasks to a queue or process tasks from a queue, or they might do both (process a task and add a new task).
- Data transfer is achieved by persisting information as XML documents. Using XML as a generic container, the queue can be used to process all kinds of data.
- Each queue has its own configuration that specifies a schedule responsible for starting one or more process task robots.
- Various timing parameters like number of retry attempts, timeout until a task is overdue or a delay until a task is started, can be applied for each configuration.
- A controller schedule is responsible for activating schedules if there are due tasks in the queue or to deactivate them if not. It will maintain the status of tasks and can be used to implement alerts in case tasks are overdue.
Benefits
Having a solution like this is crucial, especially for Desktop automation. A fail-safe robot orchestration is a must have because of the fragile nature of a desktop environment.
Many RPA projects need to handle a large volume of processes. Data driven batch processing is a key requirement in such a project.
Having such a solution will make a huge difference when it comes to the questions of
- How to orchestrate the execution of robots
- How to setup parallel processing
- How to provide transparency about processes that were successful or had errors.
The framework will speed the development of robotic projects. It provides a blueprint and a best-practice guide. And it will save many hours that RPA experts on our customer side have faced.
Technical Details
Inputs
Any data
Outputs
Any data


