Discussion
Coforge
US
Last activity: 6 Apr 2018 19:26 EDT
Copying Pages from One Tread to Another
Hi,
We have a application which is built using CS FW which is upgrading from v5 to V7. We have a scenario where Clipboard Pages(transient 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 without using requester data page concept.
Please suggest me some feasible option to achieve this.
**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.
Elastic
DE
Hi MGR00001
I agree with you, that usually the requestor scope would be the way to go, but as you have some issues, I will forward your question to the relevant SME. They will get back to you.
Regards
DIMIS
Pegasystems Inc.
IN
Few important things from Applicaton perspective:
Are you looking for Tolerence upgrade? Which means, you want to continue to use old CSR Portals? If so - You don't have to do any stuff as you will have only one thread.
Looking at your explaination in the above post, you are planning to upgrade to New Interaction Portal where Interaction and Service case are running in different threads(PR). If this is the case, I would recommened you to upgrade to CS 721 version and use data pages to share the data between threads.
I would strongly recommned you not to copy pages from Interaction to Service Cases threads. This will cause multiple issues when you launch multple service processes (Interaction Portal gives this capability).
However, to share data between Interaction and Service Case threads we do provide a facility called Thread Family (if you are using tabbed navigation - you must have know used it) which will help you to share named pages between Interaction and Service process threads (you don't have to duplicate the data and not a a good way also). We recommend you to use to data pages to share the data by parameteriing propertly, you can use thread family as interim approach to use existing pages. With this approach, updates to thread family level pages ( you need to promoate your existing named pages to thread family scope using an API) will reflect in all the threads as it is just single copy in the memory.
Refer to CS 721 documentation for more info.
Few important things from Applicaton perspective:
Are you looking for Tolerence upgrade? Which means, you want to continue to use old CSR Portals? If so - You don't have to do any stuff as you will have only one thread.
Looking at your explaination in the above post, you are planning to upgrade to New Interaction Portal where Interaction and Service case are running in different threads(PR). If this is the case, I would recommened you to upgrade to CS 721 version and use data pages to share the data between threads.
I would strongly recommned you not to copy pages from Interaction to Service Cases threads. This will cause multiple issues when you launch multple service processes (Interaction Portal gives this capability).
However, to share data between Interaction and Service Case threads we do provide a facility called Thread Family (if you are using tabbed navigation - you must have know used it) which will help you to share named pages between Interaction and Service process threads (you don't have to duplicate the data and not a a good way also). We recommend you to use to data pages to share the data by parameteriing propertly, you can use thread family as interim approach to use existing pages. With this approach, updates to thread family level pages ( you need to promoate your existing named pages to thread family scope using an API) will reflect in all the threads as it is just single copy in the memory.
Refer to CS 721 documentation for more info.