I would not recommend using an activity to do this because your pyWorkCover is locked along with your pyWorkPage in most cases, unless you have configured otherwise. In addition, there are many opportunities to do this using a data transform on a connector in the flow. This pattern will not throw a guardrail warning as an activity based implementation would.
I did this on a previous project in the flow on the final connector using a data transform with a single Set at the page level, for example, I had a single page that encapsulated all the data collected at the case level in a child, and then copied it to the parent on the connector. This, of course, assumes that the same page property exists on both case types.
Based on your use case this may suffice, but without that information, I can not state that this would be the best pattern.
@MMIchalski I want applicant specific details( can be more than 1 applicant also) to get copied to the child case (pyWorkPage) as and when the child case is created so that I can use those while processing the child case.
Correctly said, the copy method will not work here.
Posted: 2 months ago
Posted: 2 Aug 2021 13:04 EDT
Michael Michalski (MMIchalski)
Consulting Manager - Public Sector
@nitinb6996 If you are copying to the child case from the parent, then data propagation is your friend. That is the opposite of the title, which indicates copying from the child (pyWorkPage) back to the parent (pyWorkCover). In your use case, configure data propagation appropriately based on the version of the platform and portal (App Studio versus Dev Studio) you are using.