INC-137352 · Issue 583664
Mobile app improvements for poor connectivity conditions
Resolved in Pega Version 8.5.1
When the mobile app was used in areas with poor data network connectivity, the screen was freezing or a number of sync errors were seen. Improvements have been made in the processing and wait conditions to smooth the functions when connectivity is intermittent.
INC-136643 · Issue 583367
Orphaned CSS reference removed from DisplayReport harness
Resolved in Pega Version 8.5.1
An intermittent invalid CSS error was appearing in the DisplayReport harness when an operation resulted in the regeneration of the harness content. This was traced to a reference to the workform_pyReportingSkin CSS, which was used in old reporting features and is not in use anymore. The reference has been removed to resolve this issue.
INC-131942 · Issue 574321
Orphaned CSS reference removed from DisplayReport harness
Resolved in Pega Version 8.5.1
An intermittent invalid CSS error was appearing in the DisplayReport harness when an operation resulted in the regeneration of the harness content. This was traced to a reference to the workform_pyReportingSkin CSS, which was used in old reporting features and is not in use anymore. The reference has been removed to resolve this issue.
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-135906 · Issue 582901
Harness open handling added for tabs with apostrophes
Resolved in Pega Version 8.5.1
A javascript fail resulted when attempting to open any harness with an apostrophe (') in the name. This was a missed use case, and has been resolved by updating the PegaCompositeGadgetMgr file with a check and appropriate handling.
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-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-132771 · Issue 584961
Refresh section of MultiSelect properly handles refresh section
Resolved in Pega Version 8.5.1
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.
INC-127658 · Issue 568625
Corrected 1 day discrepancy for non-template DateTime
Resolved in Pega Version 8.5.1
Date values in DateTime controls in a custom filter section of a report definition were reduced by one day after drilling down into drilldown report and navigating back to the main report. Investigation showed that when the non-template version of datepicker was configured with a date property, it displayed the value using read-only formatting with allow text entry set to 'No'. This caused the operator time zone to be used to format the value while data-value used the default timezone(GMT). To resolve this, and update has been made so that while generating markup in non-template for the date property the default timezone will be used whereas the datetime property will use the server timezone.
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.