SR-D90331 · Issue 553606
Context-specific APIs used for RefreshHarness with AJAX container
Resolved in Pega Version 8.3.3
After creating an interaction case and letting it go idle, attempting to continue and process the service cases in that case was intermittently resulting in a transaction ID mismatch error. This was traced to handling in the AJAX container, and has been resolved by updating the system to use context-specific APIs for refreshHarness case in doc_submit.
SR-D78258 · Issue 545359
Corrected element pick for CaseAssetsParticipants in UI-Kit
Resolved in Pega Version 8.3.3
The pyCaseAssetsParticipants function from UI-Kit in 8.3.1 was configured with 'launch local action' instead of 'list open local action'. Because of this, the hover event was failing. While there was a workaround of using the action ‘List Open Local Action’ instead of selecting ‘Launch Local Action’ , this has been resolved by adding a check to pick the correct element.
SR-D81726 · Issue 544009
Corrected refresh section for grid dropdown using Google Chrome
Resolved in Pega Version 8.3.3
When using the Google Chrome browser on a Windows machine, an incorrect click event fired when dropdown options were changed inside a grid was causing refresh section to not work properly. This has been resolved by suppressing the 'click' action on dropdown in the 'ui_events.js' file.
SR-D89672 · Issue 550524
Custom error label styles work for 'required'
Resolved in Pega Version 8.3.3
When using the default 'required' error message, the class "labelError" is added when the required field is empty. However, when the default 'required' is replaced by a custom error message, a UI error was seen because the class "labelError" was not added when the field was empty. This was traced to an error in the non-template to template code transform, and has been resolved by updating webwb_pzpega_ui_dlcelltemplate_js to add the labelError class based on the presence of an error message.
SR-D85228 · Issue 548199
Focus retained after cascading dropdown selection in Microsoft Internet Explorer 11
Resolved in Pega Version 8.3.3
Given two DropDown fields sourced with data pages where the first dropdown value was passed as a parameter to the second dropdown source data page, at run time using Microsoft Internet Explorer 11, If the first dropdown field value was selected using the tab key, the focus shifted to the second drop down field and was immediately lost. Pressing the tab key again set focus to the top of the window. This has been resolved by updating the system to retain focus upon cascading dropdown refresh when using Microsoft Internet Explorer 11.
SR-D86360 · Issue 548570
Handling added for declare expression targets when harnessid is null
Resolved in Pega Version 8.3.3
Client expression calculation was not happening in Perform harness. Research showed that whenever text input calculations happened, the expression_calculation js setTargetValuesSuccess function was called but the elementList parameter was passed as null due to the inputHarnessId parameter being undefined. This has been resolved.
SR-D83931 · Issue 545871
Header style inheritance corrected
Resolved in Pega Version 8.3.3
When a header style for a container was explicitly set, any layout underneath inherited that style when using container formats set to 'Use Skin Base Settings'. This has been resolved by increasing specificity for the header title.
SR-D85848 · Issue 551846
Improved accessibility for tab key navigation in tables
Resolved in Pega Version 8.3.3
When using the tab key to navigate to the first cell in a table, the cell itself was taking focus instead of the link and the link did not open when 'enter' was hit. Instead, hitting tab a second time opened the link. By default, the standard was to have tabIndex set on the first cell of every row for accessibility so the link inside the cell gets the next level of focus. To resolve the navigation issue and avoid user confusion, while adding `tabIndex` to first cell of every row, the system will check for focusable content and avoid adding `tabIndex` to `td`.
SR-D74992 · Issue 546875
Improved CPMHC performance
Resolved in Pega Version 8.3.3
After upgrade, slowness was seen when using the CPMHC application. This has been improved by adding Microsoft Internet Explorer 11 optimization with the most recent javascript API.
SR-D67012 · Issue 537306
Invalid dropdown time will retain entered time
Resolved in Pega Version 8.3.3
If a datetime control using dropdown mode and a timeofday property had a validation error, on refresh the current time was being set in the dropdown. This occurred when selecting only one part of the time property (only minutes or only hours), and included an error indicating that the provided time was not a valid time of day value. To resolve this, an update has been made so that if this combination has a validation error, on refresh setting the user-entered time will be given in the dropdown instead of the current time.