SR-B83070 · Issue 338342
Tree grid alignment fixed
Resolved in Pega Version 7.4
An alignment problem was seen with a Tree grid layout when the Freeze grid header check box from the presentation tab of Tree grid layout was checked. This was due to the system not updating the width of the header in sync with the body cells, and has been fixed.
SR-B83419 · Issue 334589
Tree grid alignment fixed
Resolved in Pega Version 7.4
An alignment problem was seen with a Tree grid layout when the Freeze grid header check box from the presentation tab of Tree grid layout was checked. This was due to the system not updating the width of the header in sync with the body cells, and has been fixed.
INC-145939 · Issue 606896
Updated handling for ID value change during REST connection creation
Resolved in Pega Version 8.5.3
When using the REST Connector Wizard to create a connector, if the ID was changed on the 4th (last) step of the Wizard and then the Create button was pressed, the screen would freeze and a display a javascript error. Investigation showed that when the ID was changed on the screen, the new value was not updated properly and subsequent function calls threw errors. This has been resolved.
INC-156802 · Issue 620674
Handling added for special characters for track changes
Resolved in Pega Version 8.5.3
After entering inverted commas ["] inside a text box configured with post value and 'refresh this section' actions, focusing out of it caused the UI to freeze. A JSON parse issue was seen in the browser console, which was traced to the domelement API not having handling for special characters in the HTML code. This has been resolved.
SR-B88342 · Issue 352097
Memory leaks fixed for CPM portal with Microsoft Internet Explorer
Resolved in Pega Version 7.4
Memory leaks were found in the CPM interaction portal that caused degraded performance, intermittent screen distortion, and browser screen freeze when using Microsoft Internet Explorer. To correct this, event listeners are now cleared at the end of every interaction so the memory allocated to them is released. In addition, a quickwrapup JS error has been resolved.
SR-B56628 · Issue 244337
Memory leaks fixed for CPM portal with Microsoft Internet Explorer
Resolved in Pega Version 7.4
Memory leaks were found in the CPM interaction portal that caused degraded performance, intermittent screen distortion, and browser screen freeze when using Microsoft Internet Explorer. To correct this, event listeners are now cleared at the end of every interaction so the memory allocated to them is released. In addition, a quickwrapup JS error has been resolved.
SR-B56628 · Issue 322412
Memory leaks fixed for CPM portal with Microsoft Internet Explorer
Resolved in Pega Version 7.4
Memory leaks were found in the CPM interaction portal that caused degraded performance, intermittent screen distortion, and browser screen freeze when using Microsoft Internet Explorer. To correct this, event listeners are now cleared at the end of every interaction so the memory allocated to them is released. In addition, a quickwrapup JS error has been resolved.
SR-B64560 · Issue 334877
Memory leaks fixed for CPM portal with Microsoft Internet Explorer
Resolved in Pega Version 7.4
Memory leaks were found in the CPM interaction portal that caused degraded performance, intermittent screen distortion, and browser screen freeze when using Microsoft Internet Explorer. To correct this, event listeners are now cleared at the end of every interaction so the memory allocated to them is released. In addition, a quickwrapup JS error has been resolved.
SR-D52144 · Issue 515672
When no active document is available on login, first document will be marked active
Resolved in Pega Version 8.2.5
After logging into the user portal, attempting to perform operations like (opening a case/work object, opening reports etc.) caused the browser request to spin or freeze. The only way to recover was to close and re-launch the browser window/session and re-login. This issue occurred when there was an active reportdefinition document before the browser/node crash in the tabless dynamic container(DC) portal. After recovery, the dynamic container did not recreate the report definition document but instead tried to activate the first document in the portal, which in this case was the default harness configured in the Dynamic Container. As it was not yet loaded, exceptions were thrown. To resolve this, when no active document is available, the first document will be marked as the active document.