Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

unnecessary call to prgatewayping wasting 0.3 seconds

SA-31683

Summary



Pega mobile mashup encounters poor performance. Client-side observations show a contributing .3-second call to prGatewayPing which does not appear to contribute to functionality and which should be removed or justified. The delay is not present server-side, but the call appears superfluous.


Error Messages



Not Applicable 


Steps to Reproduce



Run mobile disputes (ios / android).


Root Cause



This request is currently needed to help setup for URL Encryption in this verion of PRPC. 

Resolution



The _pingGateway function that is part of PegaInternetApplicationComposer.js. (PegaCompositeGadgetMgr.js). You can override the function by defining a local version in the same <script> block containing the pega.web.config variables:


pega.web.mgr._pingGateway = function() {
    pega.web.mgr._bDirectPRPC = true;
    _completePegaObjectsInit();
}

When this code is used URL encryption for the gadget can not be turned on.

Once inside PRPC and if using a full end user portal the _pingGateway calls are from within PRPC. These can not be overwritten. 



Note: Starting in Pega 7.2.1 the _pingGateway is no longer used.
 

Suggest Edit

Published December 26, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us