Although it would be undesirable a termination here is necessary to show that

Although it would be undesirable a termination here

This preview shows page 11 - 15 out of 27 pages.

is deliberately left unhandled in order to cause a termination. Although it would be undesirable, a termination here is necessary to show that control has been lost and the processing cannot continue without attention.
Image of page 11
Commercial in Confidence Page 12 of 27 Case Recovery Case recovery is the ability to resolve a case after a process restart. For example, if an external issue causes Blue Prism to fail completely while the process is midway through a case, what will happen to that case? Is it enough to simply say that it will be handed over to a manual team as an exception? Or, should the process have the ability to continue the case from the previous position, and if so, how will that be achieved? The current state of the case can be recorded by updating the queue item as the case moves forward. Then in the event of a sudden shock, when the case is picked up again, either by a Blue Prism process or a manual team, its previous level of progress will be known. In the abstract below, the state of the case is recorded at each step until a problem occurs after step 3. When the case is reworked it can be started at step 4. To illustrate this consider the following example. The Account Closure work queue has been configured to allow up to three attempts per case. Blue Prism uses this property to clone a queue item when it is marked as an exception, creating a new pending item.
Image of page 12
Commercial in Confidence Page 13 of 27 The Account Closure process below has been designed to use the queue item Status property to track case progress. There are four steps to the process Check, Cards, Mandates and Close, and following each successful step the status is updated. This ensures that any retry case presented to the process will navigate to the correct next step. Additionally, when exceptions are sent for manual review, the status value will indicate to the manual team where the case was when it failed.
Image of page 13
Commercial in Confidence Page 14 of 27 Database Recovery How a Production database would be recovered may need to be considered as part of the solution design. Where a Production database is not replicated or mirrored in real time, it is possible that a back-up will need to be restored in order to recover from a disaster. If this was ever to happen, then cases that were worked after the backup was taken could appear as unworked in the queue, and the effect of the solution attempting to rework these cases would need to be considered. Consider an example where 1000 cases have been loaded to a work queue and midway through processing there is a critical database failure. A backup service provides incremental backups every four hours, but when the latest back up is restored, all cases are shown as pending. Simply restarting the process would rework the 500 already worked cases. Mitigating the effect of restoring an aged production database is best achieved during the design phase.
Image of page 14
Image of page 15

You've reached the end of your free preview.

Want to read all 27 pages?

  • Summer '09
  • ramana rao
  • 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