Mixing
Do I need a work queue for a proccess? BluePrism
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 '18 at 14:31
jakubBjakubB
103
add a comment |
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 '18 at 14:31
jakubBjakubB
103
add a comment |
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 '18 at 14:31
jakubBjakubB
103
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 '18 at 14:31
jakubBjakubB
103
asked Nov 21 '18 at 14:31
jakubBjakubB
103
asked Nov 21 '18 at 14:31
jakubBjakubB
103
asked Nov 21 '18 at 14:31
jakubBjakubB
103
asked Nov 21 '18 at 14:31
jakubBjakubB
103
103
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
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 '18 at 8:02
Vijay DodamaniVijay Dodamani
763
Thanks a lot. You explained it very good now I understand the principle
– jakubB
Nov 22 '18 at 19:08
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
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 '18 at 8:02
Vijay DodamaniVijay Dodamani
763
Thanks a lot. You explained it very good now I understand the principle
– jakubB
Nov 22 '18 at 19:08
add a comment |
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 '18 at 8:02
Vijay DodamaniVijay Dodamani
763
Thanks a lot. You explained it very good now I understand the principle
– jakubB
Nov 22 '18 at 19:08
add a comment |
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 '18 at 8:02
Vijay DodamaniVijay Dodamani
763
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 '18 at 8:02
Vijay DodamaniVijay Dodamani
763
answered Nov 22 '18 at 8:02
Vijay DodamaniVijay Dodamani
763
answered Nov 22 '18 at 8:02
Vijay DodamaniVijay Dodamani
763
answered Nov 22 '18 at 8:02
Vijay DodamaniVijay Dodamani
763
763
Thanks a lot. You explained it very good now I understand the principle
– jakubB
Nov 22 '18 at 19:08
add a comment |
Thanks a lot. You explained it very good now I understand the principle
– jakubB
Nov 22 '18 at 19:08
Thanks a lot. You explained it very good now I understand the principle
– jakubB
Nov 22 '18 at 19:08
Thanks a lot. You explained it very good now I understand the principle
– jakubB
Nov 22 '18 at 19:08
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
