Tag each Child item with the same relationship key When all child items are

Tag each child item with the same relationship key

This preview shows page 22 - 25 out of 29 pages.

Tag each Child item with the same “relationship key” . When all child items are added, add a single item to the “Parent” Work Queue. The Item Key will be the same as the relationship key Item Tag added to the child items. The item data for the Parent item could include all the item keys of the child items, this can then drive the output once all child items have been worked. Tag each item with the Item Tag “Parent Created” After following these steps, you will now have Child Items ready to be worked by your Blue Prism process, and a closely related Parent Item in a separate “Parent” Work Queue.
Image of page 22
Advanced Work Queues | 23 Commercial in Confidence 7.2.4. Using the Parent / Child Relationship Once you have created your Child and Parent Work Queue items, the following steps outline the main process flow: Your main process flow will get work from the main Child queue using the Get Next Item action. Once the Item is Worked and Marked as Completed or Exception, the following steps can be taken: o Use the Get Report Data action to search for unworked items in the Child Work Queue with the same relationship tag as the item just worked. o If there are unworked items found, no further action is required, and your process can continue onto the next case, skipping the following steps. o If there are no unworked items found with the same relationship key, it means that all the child items have now been worked. o Get the Parent item to work using Get Next Item. If the Parent Item is not available, it means that another robot has already worked or is currently working the Parent Item. Your process can continue to get the next child case to work, skipping the following step. o If the Parent item is successfully locked, it can be worked. Any Parent level actions that need to be taken by the process can be taken (i.e. sending a work complete confirmation email), and the Parent item can be marked as completed. 7.2.5. Ensuring the Parent / Child Relationship It is important to ensure that the Parent/Child Relationship of your work items is maintained. A poorly designed solution might have the following risks: An “orphaned relationship” where some or all child items are added to the Child Work Queue, but no Parent Work Queue item exists for them. A “broken relationship” where at least one of the following exists: o Work on Child items starts before all Child items and the Parent item is added to the Work Queue. o Not all Child items are added to the Work Queue but the Parent item is created.
Image of page 23
Advanced Work Queues | 24 Commercial in Confidence o Something occurs after the Work Queues are populated to delete a Child or Parent item from the Work Queue (i.e. a Controller manually deletes them). A problem or exception when working the Parent Work Queue item leaves the final Parent workflow incomplete, and therefore all the child items are also incomplete. 7.2.6. Integrity Checking To circumvent the risks of a Parent/Child Work Queue relationship, an “Integrity Check” work flow is recommended. The integrity flow may either be in the process that works the business process, or in a totally separate checking process ran daily.
Image of page 24
Image of page 25

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