INC-145902 · Issue 604196
Corrected tab alignment with when expression
Resolved in Pega Version 8.3.5
The tab layout group was not aligned properly in the Case Worker portal when using the Tab Layout Group with Enable stretch for the tabs checked and a when expression on one of the tabs. This was traced to the updateStretchTabWidths API not being triggered in the correct context due to a condition resolving as false. This has been corrected by adding an additional condition to enable the correct resolution and context.
INC-137324 · Issue 584919
Corrected tabbing focus when modal flow has 'disable when'
Resolved in Pega Version 8.3.5
While tabbing through the modal dialog, focus moved to the background screen if there were custom flow action buttons that had a 'disable when' condition. This was caused by the last focusable element being a disabled element, and has been resolved by adding a disabled check in the getLastFocusableElement method that will determine whether element is disabled, and if so it will look for other elements as disabled elements can't be focused.
INC-146223 · Issue 604466
Date column filter shows correct date/time for optimized code
Resolved in Pega Version 8.3.5
Two issues were seen when filtering a table that had the "Optimize Code" checkbox checked: 1) While filtering the date values in the table, the table showed one day less than the actual date based on timezone differences. When both the operator and server timezones are the same, the issue did not occur. 2) The filter always showed the time value as 00.00 irrespective of the property timestamp value. These were traced to the pyModes being incorrect for embedded properties, which has been resolved.
INC-144851 · Issue 604481
Date Time picker works with locale es_US
Resolved in Pega Version 8.3.5
When an Operator had the locale es_US (Spanish) set on the Profile, the Date Picker on the application was throwing validation errors when a date or time was chosen from the out-of-the-box Date Time Control. Investigation showed the date-time format for locale es_US was not supported, and the getDateTimeFormat API has been updated to support this format (11:00 a.m.).
INC-134634 · Issue 584948
FSM Mobile app correctly starts phone call after closing Google
Resolved in Pega Version 8.3.5
When two controls were configured in the FSM Mobile app, one for Get Directions and one to handle a phone call, clicking on the phone call control worked correctly when it was used first, but clicking on the Get Directions control and opening and closing Google Maps before clicking on the Phone call control caused the phone call control to not work. Investigation showed that after the Get Directions control was used, the # in the href attribute was automatically prepended with window.location. To resolve this, a check has been added that will compare the attribute with the completely formed {URL}# so that entire window.location will not be prepended.
INC-140482 · Issue 594166
Handling added for last focused element in custom modal
Resolved in Pega Version 8.3.5
Using Shift-Tab can take the focus out of the modal window when using a custom modal template without the "X" icon in the header. The issue did not happen when using "tab" key press to traverse the modal. This was a missed use case for the last focused element being div and tabindex as 0 combined with using a custom template which doesn't have close button. This has been resolved.
INC-138803 · Issue 591926
Mouse event Cross-site scripting updates
Resolved in Pega Version 8.3.5
Cross-site scripting protections have been added to mouse event attributes.
INC-138701 · Issue 596612
Multi Select populates values for Page group
Resolved in Pega Version 8.3.5
The Multi Select control was not populating values when Page group was chosen as a source. This has been resolved by updating control_multiselect and pzgetACdata to support page group source.
INC-139156 · Issue 592150
Pasting image lands in correct location
Resolved in Pega Version 8.3.5
When pasting an image in a user story or issue, the image did not land where the cursor was placed in the contents of the issue or story. This was traced to the insert element handling for rich text editor, and has been resolved.
INC-132771 · Issue 584963
Refresh section of MultiSelect properly handles refresh section
Resolved in Pega Version 8.3.5
On hitting tab or enter on a Multiselect control with "Post value" and "Refresh Section" enabled, focus moved to the header of the page when it refreshed. This has been resolved by updating the 'disable when' expression for "run on client" to better handle the input element used for enabling the controls.