INC-211590 · Issue 711020
Auto-complete and calendar popover alignment corrected
Resolved in Pega Version 8.8
An issue with the container alignment of the auto-complete and calendar dropdown popovers has been resolved by removing styling in the pyReportEditorStyling .css which was causing the issue.
INC-211655 · Issue 712351
Added handling for Malaysian locale date/time
Resolved in Pega Version 8.8
When using the "ms_MY" locale for Malaysia, entering ‘14/02/2022 13:00’ in the displayed DateTime input field generated the error "14/02/2022 13:00 is not a valid date / time value." This was due to differences in the underlying Java version: in Java 8, the API PRDateFormat.getShortDateTimeFormat returns "dd/MM/yyyy h:mm" and the PRDateFormat.getAmPmStrings returns [AM, PM], but in Java 11, the API returns "d/MM/yyyy h:mm a" with PRDateFormat.getAmPmStrings returning [PG, PTG]. For the Malaysian locale ms_MY, the clock format is 12 hour and AM/PM Strings are PG, PTG. This caused environments running JDK11 to fail client side validation for date time when PTG (a 3-char AM/PM string) was selected. This has been resolved by adding handling for this usecase.
INC-211743 · Issue 711670
PD4ML upgraded
Resolved in Pega Version 8.8
Issues with PDF generation have been resolved by upgrading PD4ML to version 4.0.13.
INC-211911 · Issue 713053
Able to expand rows when other rows are expanded
Resolved in Pega Version 8.8
When multiExpand, threadProcessing, and readonly flags were true, attempting to expand multiple rows at the same time collapsed already opened rows and generated an error indicating "target is not defined". This was caused by 'handleEditItem' not calling the collapse functionality for an opened row correctly, and has been resolved by adding a check which allows the expansion of multiple rows for readOnly details.
INC-212623 · Issue 709551
Dropdown label is accessible when combined with placeholder or tooltip
Resolved in Pega Version 8.8
The screenreader was not reading the dropdown label if tooltips or placeholders were added to the dropdown. This was caused by the label of the element being overwritten, and has been resolved by replacing aria-label with aria-describedby on the input element.
INC-213247 · Issue 708868
Title attribute added for disabled icons
Resolved in Pega Version 8.8
The disabled icon control in non-template mode used the tempTitle attribute instead of title, interfering with accessibility because no information was available to screen readers. This has been resolved by adding the aria-disabled attribute to the disabled icon control.
INC-213717 · Issue 724533
Flag added to allow disabling copy/paste style formatting
Resolved in Pega Version 8.8
Copy/pasting text from Outlook or another external application caused formatting issues in the Rich Text Editor. To address this, the flag "window.disablePasteFromWord" has been introduced which allows turning off the feature of retaining formats when copying from Word or Outlook. This flag can be set to 'true' in UserWorkForm to disable this default feature.
INC-213833 · Issue 710187
HarnessActions.handleMenuAction able to invoke Show-Harness
Resolved in Pega Version 8.8
A 403 Forbidden issue occurred when Show-Harness was called from pega.ui.HarnessActions.handleMenuAction. This has been resolved by adding code to register 'Show-Harness' when it is called in this way.
INC-214020 · Issue 710311
Placeholder value display made customizable
Resolved in Pega Version 8.8
The default place holder value (123,456.78) was displayed for the integer controls even when the placeholder was set to None. This has been resolved by modifying the code to allow customization of the place holder value display. If the "Display value using read-only formatting" option present under editable format is selected and the desire is to show default placeholder for numeric fields, "showDefaultPlaceholderForNumber" with owning ruleset as "Pega-UIEngine" must be created and set to true. If "Display value using read-only formatting" is selected and the default placeholder should not be shown in numeric fields, the DSS should be set to false.
INC-214222 · Issue 719320
Confirmation message correctly displays
Resolved in Pega Version 8.8
Two issues were seen with inconsistent display of the confirmation message. In one instance, after an assignment was finished the Review harness was appearing instead of Confirm harness and no confirmation message was displayed. In the second instance, after creating a case and moving to the next stage, coming back to the previous stage did not show the confirmation message. These issues were traced to the Ajax container primary getting closed before refreshing the section pyCaseMainPageNotification, causing the harness context issue as well as the failed conditional parameter strPHarnessPurpose issue which caused the message to not display. These have been resolved.