Composite screen display issue - new interaction portal
After upgrading from v5.5 to v7.1.9 and to CSI 7.1.4. We are doing compliance upgrade updates to use CPMInteractionPortal and encountering several issues. One of the Issue is displaying composite screen when CSP processing SR. We have Composite screen getting displayed using standalone pages, they works fine when processing SR. But when we start SR, composite is not showing any data.
From analysis we got to know that, since SR work launches with new thread and in that thread composite view stand alone pages created during Interaction are not available so showing blank screen.
To solve this, we know one option is to create requestor level Declare page and refer that in composite view. But this takes huge effort, we have 8 tabs and all load data with different standalone page and there are 100's of activities to load composite data ... verifying all them and changing testing is not a upgrade effort but a like a rewrite effort.
Is there a way to solve this issue easily ? please suggest with options..
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Hi, We know DataPage is best option to go far.. but we cannot take risk of changing all 360 view pages to datapages, in which case i may need to change so many activities. Our 360 view is complex in nature for each tab, so doing such datapage change becomes major work, which ends up in doing partial rewrite rather than upgrade.
Is there other ways to copy the page to SR's thread as well..? i mean using any OOB functions or activities .. please guide...
We have a similar situation. We used to create top-level pages during the interaction that afterwards were passed to the service case's thread. To avoid refactoring all the service cases, we kept them as-is (so, we keep referencing A.property, B.property) where A and B are top level pages.
But we changed the interaction process so now, after building A and B we also do "Page-Copy A into pyWorkPage.A" and the same for B. This way A and B will exist as well in D_Interaction.
Then, we overrode NewDefaults so it does "Page-Copy D_Interaction[InteractionID].A into A", so it re-copies the pages to top-level on SR creation and all the service cases still find the data where they expect to find it.
However we adopted this solution as temporary, while we migrate all the other things (screens, CPMPortal, etc). Once we have a fully functional Pega 7 system we will start migrating processes to reference directly D_Interaction. The advantage of putting this temporary solution in place is that you won't need to migrate all the processes, but you can do it progressively since having the duplicate structure will allow old and new processes to work.