The existing limitation between Pega versions has caused one of the applications from Core Pega Platform (CMS) to be embedded between Pega Customer Care portal (Task area) which makes screens complex.

Until the broader vision of making duplicate search a reusable module at foundation layer, I feel the first version of application will go live with this nested portal (2 left panel, 2 top panel etc.). 

Apparently, enterprise architects and designated Pega designers have approved of it for now, but I am looking for some standard best practices end user document which clearly states this design may cause issues and is not optimal.