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.

Hello Ravindra,

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.

Thanks,
Mike