What is correct about work Queues in Blue Prism?
Answers
Answered by
7
Almost every Blue Prism Process will make use of a work queue, which is essentially a list of jobs, or cases. New cases can be fed into the queue, and the queue can be updated with results as each case is worked.
A work queue provides the following features:
Multiple machines can work from the same queue at the same time, each retrieving different cases to work.An individual case can be marked as “complete” if it has been worked satisfactorily, or marked as an “exception”, if it could not be completed.Queued work can be monitored and maintained from Control Room.MI such as volumes, performance levels, and exception details can be extracted from queue data.
A Blue Prism Process is intended to obey instruction to do a repetitive task. That instruction could be some kind of list feeding the Process with work, for example a spreadsheet. Alternatively, a Process might be designed to wait for work to appear on an ad hoc basis, for example files appearing in a folder.
Realistically we should expect there will be problems and accept that some cases will succeed and some will not. We may also instruct Blue Prism to purposely disregard certain cases. Whatever happens, we will need to record results.
If there are too many cases for one instance of Blue Prism to cope with, we may want to run the same Process on multiple machines to share out the workload.
The Work Queue feature provides this functionality to store, manage, share, and report on Process work.
A work queue provides the following features:
Multiple machines can work from the same queue at the same time, each retrieving different cases to work.An individual case can be marked as “complete” if it has been worked satisfactorily, or marked as an “exception”, if it could not be completed.Queued work can be monitored and maintained from Control Room.MI such as volumes, performance levels, and exception details can be extracted from queue data.
A Blue Prism Process is intended to obey instruction to do a repetitive task. That instruction could be some kind of list feeding the Process with work, for example a spreadsheet. Alternatively, a Process might be designed to wait for work to appear on an ad hoc basis, for example files appearing in a folder.
Realistically we should expect there will be problems and accept that some cases will succeed and some will not. We may also instruct Blue Prism to purposely disregard certain cases. Whatever happens, we will need to record results.
If there are too many cases for one instance of Blue Prism to cope with, we may want to run the same Process on multiple machines to share out the workload.
The Work Queue feature provides this functionality to store, manage, share, and report on Process work.
Answered by
0
Blue prism is a very busy site that a couple of individuals use when advertising their ads or posting what they may feel its necessary to the clients, therefore emerging to be as one of the busiest sites.
The queues in this prism is due to the pressure as per the number of clients in use of the site. thus therefore one has to be p[atient. as waiting for his time to come.
Similar questions