Populating pyWorkCover for an archived child case

General
, , ,
1

Dear Team,

Can you please advise on the below?

Case A is a Parent case and Case B is a child case of Case A. Both Case A and Case B are archived.

While opening Case A - the Case A details are populated in pyWorkPage - Expected

While opening Case B - the Case B details are populated in pyWorkPage - Expected

While opening Case B - the Case A details are not populated in pyWorkCover - Is this expected?

The OOTB activity used to open any archived case (Parent or Child) is pzOpenArchivedWorkObject. This doesnt have any logic to populate pyWorkCover.

Since pzOpenArchivedWorkObject is Final rule, we need to do some tweaks which we dont want to do.

Is this a bug in Pega or expected product behaviour?

Thanks for your time!

Regards,

Guhan

2

@GuhanathanV4521 It appears that the behavior you are experiencing is expected. The OOTB activity pzOpenArchivedWorkObject does not include logic to populate pyWorkCover when opening an archived child case. This means that when you open Case B, the details of Case A are not automatically populated in pyWorkCover. Since pzOpenArchivedWorkObject is a final rule, it cannot be modified directly. This behavior is consistent with the product’s design and not considered a bug.

:warning: This is a GenAI-powered tool. All generated answers require validation against the provided references.

How to implement/customize archival cases in application layer built on theme cosmos