INC-160102 · Issue 627687
Updated resource file paths for mobile images
Resolved in Pega Version 8.5.3
After upgrade, a resource missing error was shown on the mobile UI when accessing a section in an offline mobile app. This was traced to the CSS file having an incorrect path to the 'requiredstar' gif file and has been resolved by updating pzbase-form-level-elements to use webwb instead of an images path
INC-160497 · Issue 627715
Able to add missing headers from App Studio
Resolved in Pega Version 8.5.3
A missing header in pyActionArea and pyActionAreaheader could not be added from App Studio. This was due to the sections not being built using design templates, and has been resolved by updating the section to be editable in runtime.
INC-160500 · Issue 627268
Cosmos App Studio icons have helper text
Resolved in Pega Version 8.5.3
Enhancements have been made for accessibility by adding Helper text to icons in the Cosmos theme for App Studio.
INC-161430 · Issue 627721
Accessibility Component/Widget role added to pyCaseErrorSection
Resolved in Pega Version 8.5.3
Page level errors were not accessible due to the error section being wrapped inside a dynamic layout whose contents were not readable. This has been resolved by updating dynamic layouts to use the correct accessibility roles.
INC-162692 · Issue 629637
Added primary portal navigation role
Resolved in Pega Version 8.5.3
While in the User portal, Accessibility inspector displayed the warning "Primary Portal navigation may be missing a navigation role." This role has now been added to pzPortalNavigation.
SR-D82148 · Issue 547576
Localization improved for ToolTips
Resolved in Pega Version 8.5.3
Attempting to use the Field value to localize the tooltip for Hour and Minute resulted in the time being displayed as "tooltip: Hour". Support has been added for localizing these fields using pyTooltip. In addition, an issue with the tooltip still being displayed after switching helper text to None and saving (without manually clearing the existing text) has been resolved with an update that will clear the tooltip value when helper text is selected as 'None'.
SR-C68134 · Issue 423618
Support added for configuring key stores using prconfig or system properties
Resolved in Pega Version 8.1.3
Previously, stream service only supported key store and trust store configuration using Data-Admin-Keystore instances. Unlike cluster encryption, it did not allow the configuration of key stores using prconfig or system properties. In order to align Stream service SSL configuration with the rest of the platform, support has now been added for the following system and prconfig properties:-Dpega.cluster.keyStore -Dpega.cluster.keyStorePassword -Dpega.cluster.trustStore -Dpega.cluster.trustStorePassword
SR-69015 · Issue 619995
Unescaping characters implemented for expressions
Resolved in Pega Version 8.3.6, Resolved in Pega Version 8.4.4, Resolved in Pega Version 8.5.3, Resolved in Pega Version 8.6
An issue where expression builder statements were evaluated differently at runtime than at testing has been resolved. Pega Platform expressions with String literals(that is, sequences of characters enclosed in quotation marks) now unescape characters in strategy shapes such as Set Property or Filter.
SR-C60247 · Issue 413680
pzRuleFormToolbarPopulateActions works when @ is present in the operator ID
Resolved in Pega Version 8.1.3
Using pzRuleFormToolbarPopulateActions to get all the versions of the rule was not working as expected if the '@' symbol was present in the user ID. This was caused by the Rule-.pzRuleFormToolbarPopulateActions activity not forming the private rules correctly in this use case, and has been fixed.
SR-C65381 · Issue 415189
Added check for pyType when refreshing the Declare_pyDisplay Page
Resolved in Pega Version 8.1.3
The standard behavior of clicking a link in the left navigation of the Pega Diagnostic Cloud manager portal is to open a new thread which automatically adds/updates the Declare_pyDisplay Page. However, in some circumstances opening the work items and clicking the navigation link followed by a refresh/F5 from the Google Chrome browser caused the Declare_pyDisplayDatapage to become corrupted and either froze the screen or caused a new popup window to open. This was traced to a situation where the parameter "pyType" was not present in one of the cases, causing the system to rely on "harnessName" instead. To resolve this, a check has been added that will retrieve pyType from the docObj parameter page of the pzpega_ui_dynamiccontainer.js file if needed.