SR-D41130 · Issue 510078
Handling added for precision decimals in cascading dropdown on mobile
Resolved in Pega Version 8.3.2
A cascading dropdown with a parameterized datapage configuration containing decimal values with precision (such as 22.3,20.000) showed the values as expected on desktop, but the values were empty on mobile. The values did show on mobile as well if precision was not used. This has been resolved by updating templateengine_context so that decimal values will not be treated as a property reference.
SR-D42583 · Issue 514485
Label of a field is correctly rendered when a section is re-used with a visiblity condition
Resolved in Pega Version 8.3.2
The label of a field was not being rendered/visible when a section with a 'visible when' condition was re-used in different Page Contexts. The label was displayed correctly if 'Run visibility condition on client' was checked. As part of performance improvements made in a previous version, label generation was moved under the dlcellvisibility flag. Because of this, if a section was re-used at multiple places with different contexts and one place had visibility false and another had visibility true, the labels were not getting generated for the visible section. To resolve this, Label Generation has been moved out of dlcellVisibility to ensure label metadata will always be generated. Updated performance improvements have been made instead by way of a DSS setting (generateCellMetadata) so that when generateCellMetadata is true, the label generation will honor dlcellvisibility to generate the label metadata.
SR-D43740 · Issue 512181
Added support for Helper Text Question Mark with visibility condition
Resolved in Pega Version 8.3.2
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-D44769 · Issue 531439
Resolved non-template harness stale reference for navigation menu
Resolved in Pega Version 8.3.2
Post upgrade, the navigation menu was initially present but disappeared on click of a menu item. This issue was seen only when the harness was non-template and SPA was enabled on the dynamic container: when launch harness was done on the same harness, change tracker created a new thread object but the client cache was holding the stale reference. When using template harness, mergeBigData adds all the new details into the stale object, preventing this issue. To resolve this issue for non-template harnesses, initChangeTracker in pzpega_ui_doc_lifecycle file has been updated.
SR-D44943 · Issue 527919
Handling added for mousdown triggers in Firefox dropdown and sutocomplete controls
Resolved in Pega Version 8.3.2
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 512527
Added support for Helper Text Question Mark with visibility condition
Resolved in Pega Version 8.3.2
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-D45736 · Issue 512895
Parameter field value correctly resolved for radio button rendering
Resolved in Pega Version 8.3.2
After creating a section that held a Radio button field that used the field label as a parameter from another section, at run time the radio button displayed the parameter name on the screen rather than its value and the radio buttons did not appear. Investigation showed that when rendering the section, the param.property was not resolved and the control was not rendering. To resolve this, the DLCellTemplate.js has been updated to display the localized value in the Label, and DLCellTemplateMetadata and RunTimeUtil have been modified to include the parameter reference in the current context.
SR-D45828 · Issue 519351
Added variable null check to resolve refresh condition on dynamic layout not working
Resolved in Pega Version 8.3.2
Given a setup where a parent section had several section includes, one of which had a property that was set to refresh and disable another section when the property changed, on changethe refresh action was not working and hence the disabling did not work. Refreshing the browser corrected the behavior. Javascript errors were noted on the console. This has been resolved by adding a null check on the variable to avoid exceptions.
SR-D45848 · Issue 515523
Added toggle to hold radio button value during multiple service case creation
Resolved in Pega Version 8.3.2
When a field was implemented with a radio button control in the service case screen, starting two cases of the same or different case type (with the same property and control) resulted in the selected value not sticking in the first case when selections were made for the second case. This was traced to multiple radio buttons with the same name in the dom for different AJAX containers: as per radio buttons behavior, only one could be selected if they have the same name. To correct this issue, updates have been made to change the name on radio buttons which are inside the hidden AJAX container and toggle the changes when the buttons should be shown.
SR-D46543 · Issue 516181
Error messages made more accessible
Resolved in Pega Version 8.3.2
In order to improve the accessibility of error messages, an aria-describedby attribute will be placed on the input that will link to the error message. To further support screen reader users, the focus will be moved to the first input field with an error after the user clicks submit.