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-B65958 · Issue 324162
Code modified to avoid CSS style reset on container expansion
Resolved in Pega Version 7.4
CSS styles were being reset when the container was expanded. This was an issue with the CSS class name being changed when the Expanded class name was added to the span without a space, leading to concatenation with the class name already present. A space between new(CSS class Expanded) and old class(CSS class present on span) has been added to fix this issue.
SR-B68991 · Issue 336840
Fixed Expand when evaluation for nested RDLs
Resolved in Pega Version 7.4
When using a nested repeating dynamic layouts that included section with collapsible headers, using a property pyExpanded and a custom 'when' rule isExpanded to expand and collapse the layouts and refresh the parent section from deep within the nesting was sporadically producing unexpected results. If the pagination was set on the inner RDL, after refresh the layouts were not always in the same "expanded" state as they were before the refresh. This was traced to a unique ID not being generated for the expand-indicator inside progressive loaded RDL, and has been fixed.
SR-B69968 · Issue 347332
Handling added for Google Chrome popping required field alert
Resolved in Pega Version 7.4
After tabbing into one of the required radiobutton fields but not making a selection, switching to a different application like Outlook and then switching back to the Pega user portal caused an alert popup for a required field to be thrown by the browser. This happened only when using Google Chrome and PegaWAI was included as part of the application stack. This was traced to a default Google Chrome behavior that leads to an infinite loop of invoking blur handler, and handling has been added to resolve it.
SR-B70521 · Issue 340527
Accordion stays in view when changing tabs
Resolved in Pega Version 7.4
The content in the accordion group was scrolling down below/above the screen frame when other layouts were selected. This was an issue with the accordion not being in viewport when opened since the content was hidden using display:none, and has been fixed by calling scrollIntoViewIfOutOfView for active accordion. ScrollIntoViewIfOutOfView is defined in pzpega_ui_doc_domUtils.
SR-B71597 · Issue 330030
JAWS reads shortcut labels with custom controls
Resolved in Pega Version 7.4
JAWS was not reading the modal dialog title and some inside content for GDIT. This was due to JAWS only reading the value and not the label for pyShortcutTitle and pyShortcutDescription as they are displayed using a custom control. To fix this, the system will use formatted text for pyShortcutTitle and pyShortcutDescription when pxRequestor.pyPegaDesignMode != 'true'.
SR-B74152 · Issue 331689
Resolved blank offer page for property type Class Key
Resolved in Pega Version 7.4
When data like 'Category' was referenced via a pxDropdown in Proposition Data that was defined with a datapage, the Dropdown was working within a proposition via proposition management --> Decision Data, but the following Offer page was displayed as blank and clicking on any existing Offers or the Create button resulted in a rendering exception. This happened when the primary key only contained one attribute that was also used later for "Table Type" and "Class Key Value", and was traced to an issue with the pageName parameter becoming stale. To fix it, the pageName parameter will be cleared after its use in the pzGetClassKeyValues RUF.
SR-B74426 · Issue 330675
Modal window errors displayed as expected
Resolved in Pega Version 7.4
After configuring a tabbed layout where one of the tabs contained properties with required field validation and a button to launch a modal window, focusing on the required property and then moving to another property showed the required validation message for that property. However, once the post-submit modal window was launched and the validation was configured via a post processing activity, clicking the submit button did not display the expected validation messages in the modal window. This was traced to the client side error indicator on the tab header using the incorrect ErrorFlag ID, and has been corrected.
SR-B74907 · Issue 329422
Fixed stuck modal dialog in Microsoft Internet Explorer grid
Resolved in Pega Version 7.4
When using Microsoft Internet Explorer, it was not possible to cancel or dismiss a dirty pop-up error message that was generated in a grid after adding a line and then closing a work object without submitting a mandatory field. The cause was found to be interference with click actions outside the grid caused by the submitrow method of ui_grid.js that was used when the row cells have editable "required" controls. This has been fixed.
SR-B74916 · Issue 332336
Empty value handling added to json.parse
Resolved in Pega Version 7.4
The json.parse in jsonscript was missing handling for empty values, causing RefreshSection on keyDown to not work as expected if no value was given. This has been fixed.