To circumvent that risk your options include Ensure that there are always

To circumvent that risk your options include ensure

This preview shows page 14 - 17 out of 29 pages.

To circumvent that risk your options include: Ensure that there are always enough robots working the process to clear all work each day. Design a solution that uses more than one method of prioritising, adding logic to your design that works lower priority items if they are over a configured age.
Image of page 14
Advanced Work Queues | 15 Commercial in Confidence Include SLA monitoring and alerting to your solution to ensure Blue Prism Controllers are informed if work items are at a risk of missing their SLAs. The Controller can then take the appropriate action if required. SLA monitoring could take the form of either an occasional check within your processes, or a separate process that runs throughout the day, querying your Work Queues to check the age of the oldest unworked item. 5. Encrypting Work Queues The data held by each work item is stored in plain text on the database by default. The queue can be configured to encrypt the data automatically when it is saved to the queue and decrypt it automatically when it is retrieved from the queue. To enable encryption on a queue, an Encryption Scheme must be configured for the current environment. To change the encryption scheme or disable encryption, go to System and select Work Queues which can be found under the Workflow option. Then select the desired queue and use the checkbox and drop-down list to choose the encryption state of the queue. Figure 12: Setting Work Queue Encryption
Image of page 15
Advanced Work Queues | 16 Commercial in Confidence 6. Item Resolution Best Practice When a Work Queue is used to feed a process or recording MI, queue items are finished by being marked as “Exception” or “Completed”. We know to expect Business Exceptions and System Exceptions, and in all probability, there will be different types of each. Similarly, there may well be more than one way to successfully complete an item. In other words, an item will have many potential resolutions, both successfully completed and uncompleted for either business or system reasons. 6.1. Tagging Completed Items If a process is successfully completed to a conclusion (no more working is required on the case) the work queue item should be tagged as completed, with a brief completion type. For example, an item might be tagged as “Completed – Account Closed” or “Completed, Account Already Closed”. There may be numerous completed statuses depending on the complexity of the process, and each should be tagged. Because tags show up on the Blue Prism Performance Report, tagging completed statuses provides an easy way to keep track of how many cases complete with each completion reason. 6.2. Tagging Main Exception Categories The Blue Prism product allows developers to create as many types of exceptions as they wish. However, all exception types will fall into one of two main categories, System Exception or Business Exception, and a work queue item being marked as an Exception should always be tagged with one of these categories. The System Exception and Business Exception tags are used to summarise exception category details on the Blue Prism Performance Report.
Image of page 16
Image of page 17

You've reached the end of your free preview.

Want to read all 29 pages?

  • Summer '09
  • ramana rao
  • Business process modeling, Blue Prism

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

Stuck? We have tutors online 24/7 who can help you get unstuck.
A+ icon
Ask Expert Tutors You can ask You can ask You can ask (will expire )
Answers in as fast as 15 minutes