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

Contents are becoming blank when window is re-sized



Contents of the WO opened in workarea tab are going/becoming blank once the window is re-sized.

Error Messages


Steps to Reproduce


Root Cause

The root cause of this problem is a defect in customer application code/rules. 

User was trying to have CPM screen inside composite portal. Because of this the DOM structure has been changed.
In the normal composite tab, the structure of the DOM of the tab is as follows:
I.e. inside the iframe called (PWGadget1Ifr), we have   following DOM elements:
HTML  >>  Body  >>  div id="PEGA_HARNESS"     >>   div id="HEADER_BUTTON_HTML"

But when you embed a CPM screen inside the composite portal, the structure changes to below:
I.e. inside the iframe called (PWGadget1Ifr), we have   following DOM elements:
frameset name="CAFrameSet"   >>   frame name="DIACTION"    >>   HTML  >>  Body  >>  div id="PEGA_HARNESS"     >>   div id="HEADER_BUTTON_HTML"

The code for composite portal was not written in compatible for CPM frames.
When window is resized _resizeCallback() function of PegaCompositeGadgetMgr.js is called which in turns call the pega.ui.d.getDocumentHeight() of pega_ui_doc.js.
getDocumentHeigh() function tries to find the DOM for HARNESS_CONTENT  & HARNESS_BUTTONS , which it does not find as the DOM structure is changed.
Hence it returns undefined causing the height and the width not set properly. This is the reason why we were not able to see the height calculated properly.
The calling function of _resizeCallback, _ windowResizeCallback() sets the visibility to hidden temporarily while the window is re-sized. This will be made visible in _resizeCallback() upon successful execution.
Since it doesn’t execute the complete _resizeCallback () function and goes to catch block, it is also not able to make the iframe visible.
Hence we are not able to see the content.


The explanation for this behavior is as follows: 

Based on the above analysis, requested User to
  1. Use the OOTB design of CPM portal launch instead of using with composite portal tab.
  2. Customize the pega defined functions in such a way that they work for this configuration.

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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