Do I need a work queue for a proccess? BluePrism












0














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.










share|improve this question



























    0














    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.










    share|improve this question

























      0












      0








      0







      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.










      share|improve this question













      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






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 21 '18 at 14:31









      jakubB

      103




      103
























          1 Answer
          1






          active

          oldest

          votes


















          1














          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.




          1. We do not need to get status(error/completed) of an item.

          2. Business do not need the status report

          3. 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




          1. It will keep track of number of records got processed

          2. Easy to generate business report (how many requests got executed successfully or got exception)

          3. For each record item it will give us the status whether it is been executed successfully or got exception

          4. We can easily track the error.

          5. 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 using work 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






          share|improve this answer





















          • Thanks a lot. You explained it very good now I understand the principle
            – jakubB
            Nov 22 '18 at 19:08











          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
          });


          }
          });














          draft saved

          draft discarded


















          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









          1














          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.




          1. We do not need to get status(error/completed) of an item.

          2. Business do not need the status report

          3. 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




          1. It will keep track of number of records got processed

          2. Easy to generate business report (how many requests got executed successfully or got exception)

          3. For each record item it will give us the status whether it is been executed successfully or got exception

          4. We can easily track the error.

          5. 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 using work 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






          share|improve this answer





















          • Thanks a lot. You explained it very good now I understand the principle
            – jakubB
            Nov 22 '18 at 19:08
















          1














          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.




          1. We do not need to get status(error/completed) of an item.

          2. Business do not need the status report

          3. 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




          1. It will keep track of number of records got processed

          2. Easy to generate business report (how many requests got executed successfully or got exception)

          3. For each record item it will give us the status whether it is been executed successfully or got exception

          4. We can easily track the error.

          5. 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 using work 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






          share|improve this answer





















          • Thanks a lot. You explained it very good now I understand the principle
            – jakubB
            Nov 22 '18 at 19:08














          1












          1








          1






          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.




          1. We do not need to get status(error/completed) of an item.

          2. Business do not need the status report

          3. 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




          1. It will keep track of number of records got processed

          2. Easy to generate business report (how many requests got executed successfully or got exception)

          3. For each record item it will give us the status whether it is been executed successfully or got exception

          4. We can easily track the error.

          5. 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 using work 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






          share|improve this answer












          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.




          1. We do not need to get status(error/completed) of an item.

          2. Business do not need the status report

          3. 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




          1. It will keep track of number of records got processed

          2. Easy to generate business report (how many requests got executed successfully or got exception)

          3. For each record item it will give us the status whether it is been executed successfully or got exception

          4. We can easily track the error.

          5. 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 using work 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







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 22 '18 at 8:02









          Vijay Dodamani

          663




          663












          • 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




          Thanks a lot. You explained it very good now I understand the principle
          – jakubB
          Nov 22 '18 at 19:08


















          draft saved

          draft discarded




















































          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.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • 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.




          draft saved


          draft discarded














          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





















































          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







          Popular posts from this blog

          404 Error Contact Form 7 ajax form submitting

          How to know if a Active Directory user can login interactively

          Refactoring coordinates for Minecraft Pi buildings written in Python