We have a application which is built using CS FW which is upgrading from v5 to V7. We have a scenario where Clipboard Pages used to Display composite view screen may gets updated based on some specific action in composite view screen. But that updates need to be available for both interaction and Service Request.
We know one option is to create DataPage and declare it as requester level with parameter as interactionId and PolicyID .. so that using parameters you can refer the page in any thread.
But problem is since this application is designed in v5, now moving this pages to DataPage and changing all Activity, UI rules references with new data page name is a tedious risky Job for upgrade. Is there a way i can copy page from Interaction thread to SR thread when SR is initiated and after SR is closed copy page back to interaction thread which using requester data page concept.
Please suggest me some feasible option to achieve this.
If I understand your use case correctly, could you create a page using your prior naming structure that is sources by the datapage (with said parameters) in poth your interaction and SR areas (acting as wrappers). That way the prior naming references can remain in place assuming they were pointing to a page.
I would caution you to reconsider your approach. The underlying architecture of CPM/Pega CS has changed significantly between PRPC v5 and Pega 7. With a jump that large, you are likely to encounter hard to debug issues like this over the entire lifecycle of your upgrade (and into production) if you try and force the code built on the older architecture to work on the new. You are far better off by starting off with the latest Pega CS application and determining the delta between that and your business requirements. From there, you can focus on the look and feel and any unique requirements of your organization. In my experience, that ends up being quicker and with fewer issues than what it sounds like you are trying to do.