SR-D43468 · Issue 511644
Includes() function changed for Microsoft Internet Explorer compatiblity
Resolved in Pega Version 8.4
The complete screen was not loading due to "includes()" not being supported in Microsoft Internet Explorer, resulting in a console error and the flow breaking. To resolve this, ".includes()" has been changed to indeOf.
SR-D43551 · Issue 511241
Added handling for iPad special characters in any key event
Resolved in Pega Version 8.4
When using an iPAD, there were 5 characters that were not caught when typed by the anykey event on a text control that was supposed to take only numeric data. The control worked as expected on iPhone. Investigation showed that the Keycode is 0 in the event object for some special characters with the iPad, and this has been resolved by using key instead of depending on keycode for those special characters.
SR-D43740 · Issue 512183
Added support for Helper Text Question Mark with visibility condition
Resolved in Pega Version 8.4
The Helper Text Question Mark was not displaying if the control was configured with "Help icon with overlay on hover" combined with a visibility condition. This was a missed use case, and the expression visibility support for controls.changes have now been added in the pzpega_ui_DLCellTemplate.js file.
SR-D44546 · Issue 512600
Corrected opening collapsible rows with modal action inside a nested pane grid
Resolved in Pega Version 8.4
After expanding the second level of a collapsible row in a table and then collapsing the row back down again, trying to expand other rows in the table did not work and the error "Unable to get property 'target' of undefined or null reference" appeared on the console. This was an issue with a modal action configured inside a nested pane grid that was attempting to call a target key on an undefined object, and has been resolved by explicitly checking for the existence of the 'event' object before calling the 'target' key on it.
SR-D44943 · Issue 527921
Handling added for mousdown triggers in Firefox dropdown and sutocomplete controls
Resolved in Pega Version 8.4
After recording a test case that includes entering data into an autocomplete, the data was not actually entered into the autocomplete when the test was executed but the test step was marked as successfully executed. Other tests for other similar autocompletes appeared to execute as expected. This was due to a mismatch between the sequences of events that are fired in the Google Chrome and Firefox browsers: the system is listening for a mousedown event to record a new step, but the browser-specific behavior is different. Google Chrome: mousedown focus click change Firefox: mousedown focus mousedown change As this difference in events order is browser behavior, code has been added that will handle the specific Firefox case where mousedown triggers on invalid target elements related to dropdown and autocomplete controls.
SR-D45101 · Issue 512529
Added support for Helper Text Question Mark with visibility condition
Resolved in Pega Version 8.4
The Helper Text Question Mark was not displaying if the control was configured with "Help icon with overlay on hover" combined with a visibility condition. This was a missed use case, and the expression visibility support for controls.changes have now been added in the pzpega_ui_DLCellTemplate.js file.
SR-D45251 · Issue 523817
Harness context will be stored to handle on click executed outside of the Ajax Container
Resolved in Pega Version 8.4
An exception was generated in the interaction portal on execution of a post-value action for the on-change event on a text-box in the service case: "Failed to find instance Work-Interaction-Research.EmailBodyRTE of type Rule-HTML-Section". This was traced to a condition where clicking outside of the Ajax Container context to trigger the change caused the Events code to execute the event in the active context when the active context had already been changed by clicking outside of the AC. To avoid this, the system will store the harness context in the event object using pega.ctxmgr.getContextByTarget(target) API. Additional changes were also made to handle the context switching in case of post value when the blur triggers a change in context.
SR-D45360 · Issue 510100
Support added for non-decimal currency notation
Resolved in Pega Version 8.4
Previously in the pxCurrency control, the options allowed either specifying Decimal places (2 by default) or using the locale to decide decimal places when "Use currency standard" was selected (creating the default for 2 for en_US, 0 for jp_JP and 3 for ar_JO.) However, this did not account for currencies like JPY, TWD, and HUF, which do not use decimal precision. In order to support these currencies, handling has been added to formatNumaber js and pxFormatNumber for locales which do not have decimal precision in their currency.
SR-D45395 · Issue 524170
Check added to improve progressive scroll in dynamic layout
Resolved in Pega Version 8.4
If a repeating dynamic layout was given a data page as source, selecting a pagination format that used progressive load on scroll caused the same page list value to be shown more than once. This has been resolved by adding a check based on the page size and results loaded.
SR-D45415 · Issue 510912
RemoveThreadLEvelPages modified to preserve primary page for current action
Resolved in Pega Version 8.4
The Job Scheduler Executions drill down showing success/fail results was inconsistently showing results for the wrong jobs when sorting by column (job name). Unsorted, it opened the correct results. This was traced to the pyRemovethreadLevelPages activity removing all pages including datapages on doUIAction, causing any action performed on the UI after sorting the grid to open a wrong page. This was an issue for both the Job scheduler page and the Queue processor page. To resolve this, the pyRemovethreadLevelPages activity has been modified to not remove the data page if it is the primary page for the current action.