Parent and Child Object

Viral

New Member
Hi all,

I am looking for more information about parent and child object.

Does anyone has any idea about it.


Thank you,

Viral Shah
 

harish17

Active Member
Hi Viral,
Did you get any info on Parent and child objects ?, if it is please share with me , it will be helpful.

Thanks,
Harish
 
Is there something called Parent and Child Object at all?
I know of Child Element, Child Index, but never come across Child Object.
Do share here if you find anything.
 

VJR

Well-Known Member
Hi all,

I am looking for more information about parent and child object.

Does anyone has any idea about it.


Thank you,

Viral Shah
If you are referring to the parent and child relationship in a Work Queue then you can know more about it from the Work Queue guide pdf available on the Blue Prism portal.
 

harish17

Active Member
If you are referring to the parent and child relationship in a Work Queue then you can know more about it from the Work Queue guide pdf available on the Blue Prism portal.
Hi VJR,
In work Queue Guide(24th page) Parent /child Relationship They referred this steps

Get new work from the work source (i.e. Excel, Web Service, Database, Workflow System etc...)
• Add child items to the “Child” Work Queue. Store the Item ID for the new child items so that they can be subsequently tagged
• 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”

Could you please elaborate on BOLD Letter words
1) what is relationship key is it the key which we are uniquely adding as a key name in System manager > Queue Detail>key name or just we need to create Tag name with some name?
2)how can i add single item in Parent work queue (if we have 500 child items)?
3) What is Item Key ?
4) how can we make child and parent relationship?
 

kalam shaik

New Member
Does any one explain how to configure a parent child work queue Concept in Blueprism and can we explore for the process.
 

lakshmis

New Member
Hi, Please someone explain on Parent Child relationship queue. How a single item can be added to Parent Queue which have data of all child items. This is some what confusing.
 

Azharudeen

New Member
Parent/Child Relationships are where individual Work Queue items must remain linked in some way to other items in the same Work Queue to which they have a relationship.
For example:
• A business process is triggered by an Excel spreadsheet containing hundreds of items to work. Multiple spreadsheets may be received to work throughout the day
• A Work Queue item is created for each item in the Excel spreadsheet
• When all the items in a spreadsheet have been worked, an email needs to be sent with details specific to the items on that spreadsheet.
In this example the Blue Prism solution requires a method of knowing when all items that came from the same Excel spreadsheet source have been worked, and retrieve information from those related work items for the output email.
Creating a Parent/Child Relationship
The recommended way to maintain Parent/Child Relationships is by:
• Tagging related child items with a “Key” Item Tag that only they are tagged with
• The use of an additional Parent Work queue, providing a single view of the related work
Tagging related items
As you add the child items to the Work Queue, tag them with a key value that will be unique to all the related items. For example, you could rag the item with the name of their source, (i.e. an Excel filename), and/or tag the datetime that the request was received.

Creating a Parent Work Queue item
It is a good idea to give the Child and Parent Work Queues the same name, but with a “Child” and “Parent” suffix on the queue names. This will ensure the Work Queues can be easily viewed together in Control Room.
Only if all the child items are successfully added to the “Child” Work Queue should the Parent Work Queue item be created. A Tag such as “Parent Created” can then be added to all the Child Items used by the process that works the queue to ensure items are only worked if that tag exists.
The flow of adding Parent/Child items to Work Queues is as follows:
• Get new work from the work source (i.e. Excel, Web Service, Database, Workflow System etc...)
• Add child items to the “Child” Work Queue. Store the Item ID for the new child items so that they can be subsequently tagged
• 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.
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:
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
If there are unworked items found, no further action is required and your process can continue onto the next case, skipping the following steps

If there are no unworked items found with the same relationship key, it means that all the child items have now been worked
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 on to get the next child case to work, skipping the following step
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.
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:
Work on Child items starts before all Child items and the Parent item is added to the Work Queue
Not all Child items are added to the Work Queue but the Parent item is created
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.
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.
The integrity check flow should:
• Ensure that all parent items have the correct number of child items, and all child items have a “Parent” Work Queue item.
• Ensure no “Child” items are “trapped” within the solution. This could be a simple check upon the age of child and/or parent items
• Ensure that all Parent items with all child items completed are successfully worked

The Integrity Check could simply send an alert to the Blue Prism controller if any issues are found.
 
Top