There is a requirement where i need to navigate to parent case from child but i need to have parent case id as link in summary panel. can you pls guide on how to achieve this?
First of all, thereâs already a default link to the parent case. See the green box below. Thatâs also part of the summary panel, right?
But if you want to put it somewhere else, just create a case reference property. Create a data transform that maps your property to pyWorkCover. You can then place the case reference anywhere - see red boxes below. It automatically creates a link for you.
Hope this helps!
i m aware of this, after creation of this page property you want me to use this(PageProperty.pzInsKey) structure in view?
Did you create the data transform? This is what sets the ParentWorkObject field. Run it once the child case is created, and before you need to display anything.
In the DT, set ParentWorkObject to pyWorkCover. In Pages and Classes, define pyWorkCover with the class of the parent case type (for me, Uplus-UIExamples-Work-Hello).
Ok, but i have a question. we are already refering this property to parent case via case reference right. now we can access parent case data through this property. Why again we need to copy cover page to this property via DT ? How ever i tried mapping .ParentWorkObject=pyWorkCover as you mentioned in pyDefault data transform but again the same issue null value.
when i tried the same approcah in pyUpgradeOnOpen it worked. Can you help me to understan d this aswell? why not pyDefault? is this bcs of constellation?
When we created the case ref, you could only specify the class that the case ref points to. You still need to map the actual case at some point. Hence the need for a DT.
I didnât try pyDefault but thatâs not a bad idea. Did you set pyWorkCoverâs class in Pages and Classes? Maybe try a regular DT as a step in the child case just to test?
edit: I missed the part of your response about it working elsewhere but not pyDefault. I donât really understand why. But yes pyDefault does have some special behaviors. Perhaps pyWorkCover is not set yet when pyDefault happens? hereâs a description I got on ptWorkCover: âWhen a child case is opened in memory, Pega automatically loads the parent case context onto this clipboard page. â. So pyWorkCover isnât immediately available - only when the case is opened in memory.
@RamS17794658 I hope you got it working. If not, the syntax for getting the value into your case reference property is: Set .parentCaseRef.pyID = âyourParentCaseIDHereâ. If you check the property ruleform for .parentCaseRef, you will see it uses a self reference to .parentCaseRef.pyID to look up your parent case. So what you do is effectively store pyID as a lookup key into that page in the clipboard/case.
As for how you get the pyID of your parent to be available: pyWorkCover might not always be available as youâve already mentioned in thread. But .pxCoverInsKey should be available. And you can wrap it in @pxGetCaseIDFromRefObjKey(.pxCoverInsKey) to get the correct pyID format to set into .parentCaseRef.pyID.
i have seen issue that the value is being null if i resolve the child case while i copied .ParentObject = pyWorkCover(in pyUpgradeOnOpen).
How i can make it available everytime even if child is resolved. is this property .parentCaseRef.pyID. is ootb? i cannot find
@RamS17794658 It was more a representation of the syntax you need to use to properly populate the case reference property. I think in your case it was called âParentWorkObjectâ.
I understood that and tried the below approcah in a dt i m not able to get the value:
.RefProperty.pyID = @pxGetCaseIDFromRefObjKey(.pxCoverInsKey)
i tried cropping pxCoverInsKey to get pyID still the same issue
@RamS17794658 Then I would start by validating that pxCoverInsKey actually has a value. If you arenât getting a value into a property you need to walk the mapping backwards and see that the thing you are sourcing from actually has a value.
Bonus: Another approach for when you you create a case that is not in a parent-child relationship is described here: Pegasystems Documentation







