Do I need a work queue for a proccess? BluePrism
up vote
0
down vote
favorite
I have to develop a Robot which has to work for 7 days. I've created the proccess and my question, do I have to create a Work Queue and configure my Proccess or how do I do that.
blueprism rpa
asked Nov 21 at 14:31
jakubB
82
add a comment |
up vote
0
down vote
favorite
I have to develop a Robot which has to work for 7 days. I've created the proccess and my question, do I have to create a Work Queue and configure my Proccess or how do I do that.
blueprism rpa
asked Nov 21 at 14:31
jakubB
82
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have to develop a Robot which has to work for 7 days. I've created the proccess and my question, do I have to create a Work Queue and configure my Proccess or how do I do that.
blueprism rpa
asked Nov 21 at 14:31
jakubB
82
I have to develop a Robot which has to work for 7 days. I've created the proccess and my question, do I have to create a Work Queue and configure my Proccess or how do I do that.
blueprism rpa
blueprism rpa
asked Nov 21 at 14:31
jakubB
82
asked Nov 21 at 14:31
jakubB
82
asked Nov 21 at 14:31
jakubB
82
asked Nov 21 at 14:31
jakubB
82
asked Nov 21 at 14:31
jakubB
82
82
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
Work queue creation is not a compulsory task, it all depend on process to process until and unless we do not require any output from the BOT and not a large volume of data i.e.
- We do not need to get status(error/completed) of an item.
- Business do not need the status report
- We do not need to keep track of the items got completed and pending
But, I would suggest you to create and use a Work queue as
- It will keep track of number of records got processed
- Easy to generate business report (how many requests got executed successfully or got exception)
- For each record item it will give us the status whether it is been executed successfully or got exception
- We can easily track the error.
- And the most important : If suppose BOT execution is getting failed due to some reason and we need to restart the BOT then,
A. BOT will not pick the executed item if we are usingwork queue. It will pick the next pending item from work queue
B. If we are not using work queue, BOT will/can pick the items which were executed previously. There is no point to pick the items which were already got processed.
You can also refer the documentation provided by Blue Prism on their portal:
Work Queue Guide
answered Nov 22 at 8:02
Vijay Dodamani
523
Thanks a lot. You explained it very good now I understand the principle
– jakubB
Nov 22 at 19:08
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
Work queue creation is not a compulsory task, it all depend on process to process until and unless we do not require any output from the BOT and not a large volume of data i.e.
- We do not need to get status(error/completed) of an item.
- Business do not need the status report
- We do not need to keep track of the items got completed and pending
But, I would suggest you to create and use a Work queue as
- It will keep track of number of records got processed
- Easy to generate business report (how many requests got executed successfully or got exception)
- For each record item it will give us the status whether it is been executed successfully or got exception
- We can easily track the error.
- And the most important : If suppose BOT execution is getting failed due to some reason and we need to restart the BOT then,
A. BOT will not pick the executed item if we are usingwork queue. It will pick the next pending item from work queue
B. If we are not using work queue, BOT will/can pick the items which were executed previously. There is no point to pick the items which were already got processed.
You can also refer the documentation provided by Blue Prism on their portal:
Work Queue Guide
answered Nov 22 at 8:02
Vijay Dodamani
523
Thanks a lot. You explained it very good now I understand the principle
– jakubB
Nov 22 at 19:08
add a comment |
up vote
1
down vote
accepted
Work queue creation is not a compulsory task, it all depend on process to process until and unless we do not require any output from the BOT and not a large volume of data i.e.
- We do not need to get status(error/completed) of an item.
- Business do not need the status report
- We do not need to keep track of the items got completed and pending
But, I would suggest you to create and use a Work queue as
- It will keep track of number of records got processed
- Easy to generate business report (how many requests got executed successfully or got exception)
- For each record item it will give us the status whether it is been executed successfully or got exception
- We can easily track the error.
- And the most important : If suppose BOT execution is getting failed due to some reason and we need to restart the BOT then,
A. BOT will not pick the executed item if we are usingwork queue. It will pick the next pending item from work queue
B. If we are not using work queue, BOT will/can pick the items which were executed previously. There is no point to pick the items which were already got processed.
You can also refer the documentation provided by Blue Prism on their portal:
Work Queue Guide
answered Nov 22 at 8:02
Vijay Dodamani
523
Thanks a lot. You explained it very good now I understand the principle
– jakubB
Nov 22 at 19:08
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
Work queue creation is not a compulsory task, it all depend on process to process until and unless we do not require any output from the BOT and not a large volume of data i.e.
- We do not need to get status(error/completed) of an item.
- Business do not need the status report
- We do not need to keep track of the items got completed and pending
But, I would suggest you to create and use a Work queue as
- It will keep track of number of records got processed
- Easy to generate business report (how many requests got executed successfully or got exception)
- For each record item it will give us the status whether it is been executed successfully or got exception
- We can easily track the error.
- And the most important : If suppose BOT execution is getting failed due to some reason and we need to restart the BOT then,
A. BOT will not pick the executed item if we are usingwork queue. It will pick the next pending item from work queue
B. If we are not using work queue, BOT will/can pick the items which were executed previously. There is no point to pick the items which were already got processed.
You can also refer the documentation provided by Blue Prism on their portal:
Work Queue Guide
answered Nov 22 at 8:02
Vijay Dodamani
523
Work queue creation is not a compulsory task, it all depend on process to process until and unless we do not require any output from the BOT and not a large volume of data i.e.
- We do not need to get status(error/completed) of an item.
- Business do not need the status report
- We do not need to keep track of the items got completed and pending
But, I would suggest you to create and use a Work queue as
- It will keep track of number of records got processed
- Easy to generate business report (how many requests got executed successfully or got exception)
- For each record item it will give us the status whether it is been executed successfully or got exception
- We can easily track the error.
- And the most important : If suppose BOT execution is getting failed due to some reason and we need to restart the BOT then,
A. BOT will not pick the executed item if we are usingwork queue. It will pick the next pending item from work queue
B. If we are not using work queue, BOT will/can pick the items which were executed previously. There is no point to pick the items which were already got processed.
You can also refer the documentation provided by Blue Prism on their portal:
Work Queue Guide
answered Nov 22 at 8:02
Vijay Dodamani
523
answered Nov 22 at 8:02
Vijay Dodamani
523
answered Nov 22 at 8:02
Vijay Dodamani
523
answered Nov 22 at 8:02
Vijay Dodamani
523
523
Thanks a lot. You explained it very good now I understand the principle
– jakubB
Nov 22 at 19:08
add a comment |
Thanks a lot. You explained it very good now I understand the principle
– jakubB
Nov 22 at 19:08
Thanks a lot. You explained it very good now I understand the principle
– jakubB
Nov 22 at 19:08
Thanks a lot. You explained it very good now I understand the principle
– jakubB
Nov 22 at 19:08
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53414341%2fdo-i-need-a-work-queue-for-a-proccess-blueprism%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
