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

Static content issue through IAC and CPM

SA-5674

Summary



Customer has observed static content (picture/ javascript) is retrieved too often when request are going via the prgateway servlet, with the CPM framework.
A solution was released for PRPC but it is not taken into account by the CPM layer.

Error Messages



not applicable


Steps to Reproduce



Setup CPM
-Setup FCM with the pyFCMRFederatedWorkList7 gadget.
- At run time, looking at the federated worklist, open a remote work item.
- Check with an HTTP tracer that all the static content gets retrieved.
For instance, we see this type of request:
/prgateway/PRPCGateway/dd/!dd/$PS1__TABTHREAD2/pega_ui_harness_13256097365!!.js

- Don't close the work item and click back to the federated worklist, open another remote work item.
- Check with an HTTP tracer that all the static content gets retrieved.
For instance, we see this type of request:
/prgateway/PRPCGateway/dd/!dd/$PS1__TABTHREAD3/pega_ui_harness_13256097365!!.js

notice how the url has changed based on the thread name.

If we connect straight to PRPC, we don't face this issue.


Root Cause



The root cause of this problem is a defect in Pegasystems’ code/rules. 

Static contents are retrieved for every work object that have different thread name.This causes network congestion for the browser. 

We applied Hfix-20514 but found the PEGACOMPOSITEGADGETMGR javascript file from OOTB PRPC is not used by CPM. 
Instead CPM is using cpmcompositegadgetmgr. 

So we need to solution added to the CPM layer. 

Resolution



HFix-20591 - pega_cpm_tabbedwork.js file has been updated with the url to be genereated for "createNewWork", "openWorkByHandle", "openWorkByURL".
Suggest Edit

Published January 31, 2016 - Updated December 2, 2021

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