Question
Legato Health Technologies
IN
Last activity: 16 Oct 2018 12:03 EDT
Launch of popup should create a new thread
Got a functionality to open a popup on click of a link with a new thread. Configuration includes an action of "Open URL in window" on click of link wherein "RedirectAndRun" activity is called with a thread name, accessgroup name and purge thread set to true. Though this creates a popup (child window) with a new thread, the activities performed in either of windows, i.e., parent(main screen) or child(popup) reflect in each other such as on click of logoff in popup, main portal/screen log offs as well which is not desired. So, any suggestion on creation of new thread for poup on click of link which is independent of old thread...
***Edited by Moderator Marissa to add SR Details***
**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.
Accepted Solution
Pegasystems Inc.
IN
The issue has been handled as part of SR-B74136, please find below the details:
Explanation:
The configuration designed at user end is not a recommended approach. In Pega 7 it is suggested to use dynamic container where multiple work objects can be run at the same time.
Also When mutliple windows with same portal are launched at the same, the log off action performed on one window will be reflected in all.
Pegasystems Inc.
US
Hi Siva
I didn't confirm the behavior on an OOTB sample, But, technically, when you launch a child window from the parent and log off from the parent, I feel you should close the child too and not let it linger. What is your use case for which you want the child to persist even when you attempt to log off from the main application?
Thanks,
Bhuvana.
Legato Health Technologies
IN
Hi Bhuvana,
The use case is that of smart dispute app wherein the csr should be able to perform actions in child window even when the parent window is logged off. The said functionality was part of pega 5.5 and this has to be retained as part of upgrade to pega 7.2.1. Also, the child window closes off once any action is performed in the parent window which is again not an ideal work case since actions performed in parent should not affect the child window.
Thanks,
Siva
Legato Health Technologies
IN
Got a clarification/solution through SR stating the mentioned outcomes through present configuration is somewhat an expected behavior.
Pegasystems Inc.
IN
Hi Siva,
Glad to hear that you have found the answers to the questions. Request you to share the SR number here so that we can tag it to the thread for tracking purposes.
Thanks!
Pegasystems Inc.
US
Hi Siva,
I found your SR ID and I have notated it within your original post. I also added a note to the SR referencing this post here in the PSC.
Thanks!
Accepted Solution
Pegasystems Inc.
IN
The issue has been handled as part of SR-B74136, please find below the details:
Explanation:
The configuration designed at user end is not a recommended approach. In Pega 7 it is suggested to use dynamic container where multiple work objects can be run at the same time.
Also When mutliple windows with same portal are launched at the same, the log off action performed on one window will be reflected in all.
Pegasystems Inc.
IN
Customer could not achieve his requirement with the above suggested approach. Kindly make this post open for more suggestions to help customer meet his requirement.
Legato Health Technologies
IN
The core issue arises when we perform any action in the parent window and the child window closes off. Even a click on submit triggers a closure of child window. Any means to avoid this behavior or an alternative to run 2 different windows at the same time would be highly helpful. As per the present configuration, RedirectAndRun activity does create a new thread for the child window but any action in the parent window closes the child window though both are on different threads.