INC-183712 · Issue 674132
IndexOf updated to remove extra bracket
Resolved in Pega Version 8.7
When trying to open a section rule, content was not loading if values were derived using a report with column containing a function. This occurred when the section rule included a table referencing the report where one of the section table cells had its Property value set to the function. To resolve this, indexof has been updated to not include closing > as the HTML returned from the server now includes an attribute on that tag.
INC-183995 · Issue 673789
Corrected accessibility for action menu button
Resolved in Pega Version 8.7
When using JAWS with Google Chrome or NVDA with Microsoft Edge, the action menu button label was announced twice, as 'Case Action Menu button' and 'Action Menu button', and it required two tab key presses to set focus on the Action menu button from the Follow button. This has been resolved by removing the role type as component/widget and keeping the label as "case wide actions" so that after the focus from the icons, the focus is correctly set on the action buttons.
INC-184104 · Issue 682356
Cosmos Report Browser list updates during current session
Resolved in Pega Version 8.7
The Cosmos Report Browser list section was using a cached list of reports that did not update to reflect created or deleted reports until after logout and new login. This has been resolved by adding the pzInvalidateRBDataPages activity for harness initialization to update the reports list during the current session.
INC-184109 · Issue 671195
Handling updated for customDateTime formatting
Resolved in Pega Version 8.7
When a feature date was entered, for example as 2021/07/29 12:00:00 AM, changing any other property caused the time to be off by 4 hours and display as 2021/07/28 08:00:00 PM. Investigation showed this was caused by the parameters being passed in an incorrect order while calling pega.ui.Formatter.formatDateTime() in combination with customTimeZone, and has been resolved.
INC-184311 · Issue 667270
Time value handling updated for IW locale
Resolved in Pega Version 8.7
The error -"0undefined/0undefinedundefinedundefinedundefinedundefined is not valid time of day value" appeared when using the 'IW' operator locale and the time field was changed. This was traced to a missed condition check for the IW locale while preparing the selected time value from the dateTimeFormatString, and has been resolved.
INC-184419 · Issue 669619
Checks added to prevent EditingMode null value
Resolved in Pega Version 8.7
When trying to open a section rule in developer portal in Pega Cloud, "Error" was displayed instead of the section details. Investigation showed the pyEditingMode property was present but did not have a value, and this has been resolved by adding checks to the UpgradeSequoiaGrid activity to ensure the pyEditingMode of "" does not invoke a data transform of that name.
INC-184443 · Issue 668437
Time value handling updated for IW locale
Resolved in Pega Version 8.7
The error -"0undefined/0undefinedundefinedundefinedundefinedundefined is not valid time of day value" appeared when using the 'IW' operator locale and the time field was changed. This was traced to a missed condition check for the IW locale while preparing the selected time value from the dateTimeFormatString, and has been resolved.
INC-185122 · Issue 670401
Able to create View in Cosmos React
Resolved in Pega Version 8.7
After creating a Cosmos react application and adding casetype, it was not possible to configure the view from the step in App Studio or Dev Studio or to create a section from Dev Studio. This was traced to the componentslist not finding some necessary components, and has been corrected.
INC-185563 · Issue 670848
"Manage content" dialog box tab index is consistent
Resolved in Pega Version 8.7
The tab ordering for the "Manage content" (document upload) dialog box was not consistent. This has been resolved by updating pzModalTemplate to list the submit, cancel, etc, buttons in a consistent order.
INC-185782 · Issue 674523
Tab Names correctly displayed in Ajax Container
Resolved in Pega Version 8.7
After configuring Action Set with an Ajax container to open a harness and then configuring the same harness name for multiple action items, the first open happened as expected but the following action items were not opening properly and were still pointing to the old tab instead of showing the new tab names. This was traced to actionMetadata.Name not having the correct value, and has been resolved by explicitly updating the tabName value in the "Display" action with the needed actionMetadata.Name.