Hi Terence,

Thanks for posting your query in the Product support community.

Explanation:

1. Currently many OOTB prpc portals upon closing them invoke "pyOnbeforeWindowClose" to release requestor locks , We are extending the same activity to update the presence state of current requestor to disconnected state.
2. Upon browser window/tab close, AJAX request to run activity "pyOnbeforeWindowClose"  is being fired from “webwb • pzpega_ui_doc_lifecycle • js”  which has listener for window unload event.
3. Currently in PRPC there are 2 types of portals, framed and frame-less. "pyOnbeforeWindowClose" is invoked for all framed portals during window unload. It is NOT invoked or frame-less because for each user action, complete windows gets unloaded.

Check the attachment for the snippet from  “webwb • pzpega_ui_doc_lifecycle • js” from where AJAX request to run activity "pyOnbeforeWindowClose" is fired.

Hope this information might help you to achieve your requirement.

Regards

Mahesh

Add a dynamic container in section in the portal. This activity never gets invoked. Traced in Fiddler and tracer. No ajax call traced.Raised an Pega SR-B65422 for this issue. Product version used is 7.1.7. Slight difference in the if block in code posted by Mahesh.

if (pega.u.d.isPortal()) {

            if (!pega.u.NavigateTopHandler) {

                var F = SafeURL_createFromURL(pega.u.d.url);

                F.put("pyActivity", "pyOnbeforeWindowClose");

                var B = F.toURL();

                var I = pega.desktop.support.getDesktopWindow();

                if (!I) {

                    I = window;

                }

                I.pega.util.Connect.asyncRequest("GET", B);

            }

        }

Reproduced the issue in 7.2.2 as well. Just add a Dynamic container in a section. Launch the portal and then close the browser. The activity was not invoked. No logs in tracer or Fiddler.

Mahesh,

Using Dynamic container in a 'multi document' mode invokes the activity while using it in 'single document' mode do not. This test was done using the same portal. How can you explain this?

Warning!

Doing a logout in pyOnbeforeWindowClose will not always work properly. There is a call to pyDeleteDocumentPg in the same function, harnessOnbeforeUnload, that will end up running last most of the time. Any logoff has to be the last HTTP request to PRPC if the window is closing otherwise a requestor will still be there.

I have tested this an even though the call to pyDeleteDocumentPg is coded first it always runs last. I looked at fiddler and tracer.

We will need to look at this because I believe there are some things we can do here so you could use pyOnbeforeWindowClose to logoff.  If we reverse the logic and call pyOnBeforeWindowClose first we can then not call pyDeleteDocumentPg if the portal is closing.  That will need some internal discussion though as it could have negative effects if logoff is not called in pyOnBeforeWindowClose when dealing with browser tabs and returning the same session.

--Chris