INC-133944 · Issue 586016
Future DateTime Property picks operator timezone
Resolved in Pega Version 8.5.1
When selecting the DateTime in a property field configured to accept future data input, the input failed validation due to the DateTime field being compared with the System time zone (IST instead of the operator time zone. This has been resolved by adding a condition to honor the operator timezone in isFutureDate validation, and to fall back to the browser timezone if necessary.
INC-134634 · Issue 584946
FSM Mobile app correctly starts phone call after closing Google
Resolved in Pega Version 8.5.1
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-125341 · Issue 560436
JAWS reads the remaining character count in text input area
Resolved in Pega Version 8.5.1
When using a JAWS reader with a textarea control, the remaining character count was not being read out as expected as text was added. This has been resolved by updating the textarea tag to add an aria-describedby charcount attribute.
INC-131523 · Issue 573851
Parameters to Property UI Field available in report
Resolved in Pega Version 8.5.1
When using a parameterized control like Decimal for a property in the UI control of the Property rule with inputs given to the parameters, once the property was optimized and referred to in Report Definition, the value was rendered using the Control with parameters defined in its rule form. In the report, the column was not rendered as it is designed on the property rule, but the same worked as expected in a section. This behavior was a change after upgrade. This was traced to "pyPropertyName" being added to the stepPage as part of the pzMergeAutoGenForProp Activity, and has been resolved by adding it to the stepPage only when it is an auto-generated control.
INC-133637 · Issue 581342
Refresh handling added for cancel 'add item' while offline
Resolved in Pega Version 8.5.1
When using iPad and iPhone offline, filling in one required field, hitting submit (click action: 'Add item') without filling in a second required field, and then hitting cancel resulted in a blank record being added. Clicking the cancel button first without clicking submit before did not add the item. This was traced to the underlying repeating dynamic layer being refreshed during the submit and adding the record, and has been resolved by adding a refresh for the cancel button process as well.
INC-129848 · Issue 580459
Refresh handling added for cancel 'add item' while offline
Resolved in Pega Version 8.5.1
When using iPad and iPhone offline, filling in one required field, hitting submit (click action: 'Add item') without filling in a second required field, and then hitting cancel resulted in a blank record being added. Clicking the cancel button first without clicking submit before did not add the item. This was traced to the underlying repeating dynamic layer being refreshed during the submit and adding the record, and has been resolved by adding a refresh for the cancel button process as well.
INC-132670 · Issue 585774
JAWS reads optimized table rows correctly
Resolved in Pega Version 8.5.1
When using JAWS2020 on Google Chrome on a PegaWAI enabled application and traversing an optimized table using Table shortcuts, the first row of the table was never read, and columns were read with the headers, but with unnecessary verbiage. For example, if column "Name" had an entry "Adam", JAWS read out "Name press enter to sort , Adam" instead of just "Name Adam". JAWS reads the data columns based on aria-rowindex: because it treated the header as the first row, it directly went to the row with aria-rowindex 2. In the second issue, the complete header group was read by JAWS because there was no aria-label. These have been resolved by modifying the aria-rowindex attribute for first data row accessibility by JAWS, and aria-label has added to the header group to restrict what is read out while navigating across the data columns.
INC-137691 · Issue 585769
Aria label added to support description of tab groups
Resolved in Pega Version 8.5.1
When using layout group - tab, the screen reader would immediately read the first tab; there was no information about the tab group itself. To support giving a description of the purpose of the upcoming tabs, Layoutgroup and DLG now have a design time descriptor to configure an aria-label which will be used to announce the purpose of the Layoutgroup ahead of reading the first tab.
INC-137324 · Issue 584917
Corrected tabbing focus when modal flow has 'disable when'
Resolved in Pega Version 8.5.1
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.
SR-A92680 · Issue 263151
Removed duplicate repeat grid header
Resolved in Pega Version 7.3
An extra Grid Header Title was created when allow refresh on update was checked in a repeat grid configured for row editing via modal dialog. This was due to a place holder div error, and has been corrected.