INC-170918 · Issue 653216
DateTime property handling revised for future date with daylight savings time
Resolved in Pega Version 8.7
A DateTime property was changing each time the local action refreshed. Investigation showed this was a missed use case related to recent work to correct an issue with a 1 day discrepancy for non-template DateTime. The previous update to use the default time zone when generating markup in non-template for the date property while the datetime property uses the server time zone has been further refined to handle formatting the date time when the year is greater than 2037 and combined with daylight savings time. This will be resolved by setting the correct date before returning the moment object if the year is greater than 2037 for the date time control using display mode as date.
INC-171121 · Issue 648130
Filter popup persists correctly
Resolved in Pega Version 8.7
When the Apply filter option was selected for a table configured with a page list property as source, the filter popup appeared on the screen but disappeared after 3 to 4 seconds. This has been resolved by enabling the stretch for tabs option in the layout group.
INC-171352 · Issue 653691
Focus set correctly on the modal window in theme-Cosmos
Resolved in Pega Version 8.7
In theme-Cosmos with touch enabled, clicking on a button to open a modal window set the focus on the background instead of in the modal window, forcing tabbing through the full page to reach the modal window. This was traced to the templates not using the pzModalCancel control which has the necessary container_close for the modal dialog close icon, and has been resolved by adding a check to set the focus correctly.
INC-171663 · Issue 655245
MashUp dynamic parameters article updated
Resolved in Pega Version 8.7
The documentation for MashUp best practices has been updated to clarify that dynamic parameters sent from the client side using "pega.web.api.setAuthenticationParameters" API will be sent as part of the query parameters and won't be part of the encrypted hash as this hash is generated on the server end while generating the mashup code in the mashup channel.
INC-172178 · Issue 655021
TransID updated to trim spaces
Resolved in Pega Version 8.7
While preparing newTransID from a response, special characters slipped into "newTransID" param value and generated an error. This has been resolved by updating the system to trim spaces from newTransID.
INC-172314 · Issue 650493
File selection dynamic layout added for Cosmos
Resolved in Pega Version 8.7
The Cosmos Files & Documents widget for managing content displayed the application's configured content sourcing repository, but the screen did not allow actually selecting a file from the repository. No browse option was available, and the submit button generated an error to select a file for upload. This was traced to a missing dynamic layout with file selection for Cosmos, and has been resolved.
INC-172483 · Issue 651710
Filtering updated for UI markup
Resolved in Pega Version 8.7
Filtering has been added to the UI code to preserve the browser display appearance but remove inappropriate or potentially insecure markup.
INC-172521 · Issue 651553
Email template content visible in user application
Resolved in Pega Version 8.7
An issue was seen with email templates functionality where the body content given during the email template creation was not visible when the template was used in the application by an end user. This was a missed use case for recent security updates, and has been resolved.
INC-173238 · Issue 656504
Restored missing API call for icon navigation
Resolved in Pega Version 8.7
After logging in and searching for a bond, navigating to the home page without clearing the search string from the bond screen resulted in a pop-up warning to remove unsaved changes. Clicking on OK and then attempting to click on the list index number available below the table resulted in an error. Investigation showed pzCTkn was missing for the API calls triggered by clicking on the icon; this has been resolved by updating the pega_yui_connection.js file.
INC-173345 · Issue 655038
Check added for empty geolocation values
Resolved in Pega Version 8.7
Latency issues were traced to Geolocation-related errors in the log files. To improve performance, changes have been added to check for empty pyLatitude and pyLongitude before adding in the postdata of an async request.