Question
Wipro
IN
Last activity: 4 Oct 2017 1:38 EDT
Access grand parent case page in sub child case
Hi All,
I have cases as shown below.
TopParent case is parent of MainChlid case and MainChlid is parent of SubChild case
Parent case--TopParent
Child case-MainChlid
Sub child case-SubChild
Now i need to access TopParent page(pyworkpage) in SubChild case.
How we can achieve this any suggestions...?
Thanks,
Hussain
***Moderator Edit: Vidyaranjan | Updated Categories***
Accepted Solution
Wipro
IN
Hi All,
Thanks for your all replies.
Finally got the solution to address this. We can achieve his two ways.
Approach1:
Propagate the grand parent pzInsKey to sub child through data propagation.
Save as PerformDefaults and OpenDefaults activities into your sub child context(applies to class).
Both activities will have below steps.
Define a page(GrandPage) which is having grand parent class in Pages&Classes tab
Do Page-New by giving name as GrandPage
Do obj-open-by-handle by using pzInsKey.
By doing this way on entire sub child case this page will be available.
But PerformDefaults activity will be executed when the case is on perform haness.
OpenDefaults will be executed when we are opening the case.
So this will have some performance issue.
Approach2:
Propagate the grand parent pyID to sub child through data propagation.
Create a datapage (D_GrandPage) by taking the scope as requestor.
Object type as Grand parent applies to class
In DataSource select lookup as source and class name would be Grand parent applies to class.
Call this data page by giving parameter as grand parent case id(pyID), where ever you required.Data page will be loaded only once for each case.
Hi All,
Thanks for your all replies.
Finally got the solution to address this. We can achieve his two ways.
Approach1:
Propagate the grand parent pzInsKey to sub child through data propagation.
Save as PerformDefaults and OpenDefaults activities into your sub child context(applies to class).
Both activities will have below steps.
Define a page(GrandPage) which is having grand parent class in Pages&Classes tab
Do Page-New by giving name as GrandPage
Do obj-open-by-handle by using pzInsKey.
By doing this way on entire sub child case this page will be available.
But PerformDefaults activity will be executed when the case is on perform haness.
OpenDefaults will be executed when we are opening the case.
So this will have some performance issue.
Approach2:
Propagate the grand parent pyID to sub child through data propagation.
Create a datapage (D_GrandPage) by taking the scope as requestor.
Object type as Grand parent applies to class
In DataSource select lookup as source and class name would be Grand parent applies to class.
Call this data page by giving parameter as grand parent case id(pyID), where ever you required.Data page will be loaded only once for each case.
This has given good performance in our scenario.
Once again thanks for all your replies.
Thanks,
hussain
Pegasystems Inc.
IN
Data Propagation should be the same way as it is for a simple parent to child scenario.
Data should be propagated from Top Parent to Main child. This should be configured in the Top Parent Case Settings -> Data Propagation tab.
Later the that data to be transferred from Main Child to Sub Child. Do this in MainChild Data Propagation tab.
You can also do it directly using a data transform involving the CoverPages carefully.
Wipro
IN
Hi Kakul,
Thanks for your reply.
If it is a simple page object, then we can follow this approach.But Dont think its a good way to propagate entire pyWorkPage kind of data to child case.
Please let us know if we have any other approaches.
Thanks,
Hussain
Tetco
SA
Hi Hussain,
you can propogate the pzinskey of the grand parent case to the child cases ... and later whenever required you can open the object using pzinskey easily and fetch the updated required data from the pyworkpage og grand parent case.
Please let me know your thoughts.
Wipro
IN
Hi Ahmed,
Thanks for your reply.Yes we can do that but i required grand parent data on entire sub child case assignment.
So every time opening that will be risky and huge performance impact.
There should be scenario which will open one time for a case then that would be better.
Thanks,
Hussain
Accepted Solution
Wipro
IN
Hi All,
Thanks for your all replies.
Finally got the solution to address this. We can achieve his two ways.
Approach1:
Propagate the grand parent pzInsKey to sub child through data propagation.
Save as PerformDefaults and OpenDefaults activities into your sub child context(applies to class).
Both activities will have below steps.
Define a page(GrandPage) which is having grand parent class in Pages&Classes tab
Do Page-New by giving name as GrandPage
Do obj-open-by-handle by using pzInsKey.
By doing this way on entire sub child case this page will be available.
But PerformDefaults activity will be executed when the case is on perform haness.
OpenDefaults will be executed when we are opening the case.
So this will have some performance issue.
Approach2:
Propagate the grand parent pyID to sub child through data propagation.
Create a datapage (D_GrandPage) by taking the scope as requestor.
Object type as Grand parent applies to class
In DataSource select lookup as source and class name would be Grand parent applies to class.
Call this data page by giving parameter as grand parent case id(pyID), where ever you required.Data page will be loaded only once for each case.
Hi All,
Thanks for your all replies.
Finally got the solution to address this. We can achieve his two ways.
Approach1:
Propagate the grand parent pzInsKey to sub child through data propagation.
Save as PerformDefaults and OpenDefaults activities into your sub child context(applies to class).
Both activities will have below steps.
Define a page(GrandPage) which is having grand parent class in Pages&Classes tab
Do Page-New by giving name as GrandPage
Do obj-open-by-handle by using pzInsKey.
By doing this way on entire sub child case this page will be available.
But PerformDefaults activity will be executed when the case is on perform haness.
OpenDefaults will be executed when we are opening the case.
So this will have some performance issue.
Approach2:
Propagate the grand parent pyID to sub child through data propagation.
Create a datapage (D_GrandPage) by taking the scope as requestor.
Object type as Grand parent applies to class
In DataSource select lookup as source and class name would be Grand parent applies to class.
Call this data page by giving parameter as grand parent case id(pyID), where ever you required.Data page will be loaded only once for each case.
This has given good performance in our scenario.
Once again thanks for all your replies.
Thanks,
hussain