How to launch multiple PRPC browser windows to view cases and keep each session unique?
We have an internal application which provides a link to PRPC cases as part of a call center solution, It appears that if we click on one link to view an initial case, everything works. If we click on a second link to open a second case; even though we open a new window, data from the original case is presented (ie data on requestor-level data pages etc.). If we start a fresh browser session this does not occur. Is there a way we can build this capability into the link which launches the new ie window?
Why popup windows? The other application not PRPC?
Do you need the ability to view more than one case at a time, multiple popup windows? This has to be done by using separate thread pages. You could call the activity RedirectAndRun each time you launch a window providing a unique thread page name, ThreadName parameter, then what to run in the Location parameter. This way every case is separate, just like it would be if displayed in a tabbed work area etc.
The big problem with this is that you have to worry about the cleanup thread pages when done with the window. Meaning the calling application has to do things to keep track of the windows and thread pages and make sure cleanup is done. When using window.open the result is the window handle so you can keep track and even close child windows from parent window. This could get a little crazy.
Hi Chris - yes the other application is NOT PRPC. It is an application developed by the customer. I believe they want to see multiple windows so they can compare data within each of the individual work objects. I will provide them with your guidance. I may return and update this thread if they have additional questions. Thanks!
You can ignore the -nomerge option. This was available in pre-release versions of Internet Explorer 8. This option has been superseded by the -noframemerging option.
This has the net effect of preventing session merging, but it looks like -nosessionmerging is likely even better.
"Internet Explorer 8 and later versions. Internet Explorer 8 and later versions. Prevents Internet Explorer from merging tab processes and thus sharing session cookies across tabs. Even if you have the –framemerging feature turned on (which it is by default; see above), specifying this option will isolate your tabs into separate processes and prevent session sharing, even if those tabs are associated with the same frame process."
This is exactly what we have gone with. The calling application is rebuilding their URL and placing the RedirectAndRun activity in the URL rather than just the "Open"activity. We are passing that activity name in as a paramter to the RedirectAndRun.