SR-D28297 · Issue 498141
Tracer issues resolved for Chrome broswer
Resolved in Pega Version 8.2.3
Tracer was running in the background even after the tracer window was closed. Attempting to run a Tracer in this condition resulted in an error indicating the Tracer was being run by another operator and should be restarted, and in the Dev environment, attempting to start a Tracer once it was closed resulted in the message "Cannot launch multiple Tracer sessions for a requestor." Investigation found that the Tracer session was not being closed when the tracer window was closed because the browser specific method intended to do so was not being called. This was found to be an issue caused by the Chrome browser changing the signature of the method, and has been resolved by updating the method name in the TraceMain HTML rule.
SR-D26342 · Issue 495415
Tracer issues resolved for Chrome broswer
Resolved in Pega Version 8.2.3
Tracer was running in the background even after the tracer window was closed. Attempting to run a Tracer in this condition resulted in an error indicating the Tracer was being run by another operator and should be restarted, and in the Dev environment, attempting to start a Tracer once it was closed resulted in the message "Cannot launch multiple Tracer sessions for a requestor." Investigation found that the Tracer session was not being closed when the tracer window was closed because the browser specific method intended to do so was not being called. This was found to be an issue caused by the Chrome browser changing the signature of the method, and has been resolved by updating the method name in the TraceMain HTML rule.
SR-D8754 · Issue 497377
Tracer issues resolved for Chrome broswer
Resolved in Pega Version 8.2.3
Tracer was running in the background even after the tracer window was closed. Attempting to run a Tracer in this condition resulted in an error indicating the Tracer was being run by another operator and should be restarted, and in the Dev environment, attempting to start a Tracer once it was closed resulted in the message "Cannot launch multiple Tracer sessions for a requestor." Investigation found that the Tracer session was not being closed when the tracer window was closed because the browser specific method intended to do so was not being called. This was found to be an issue caused by the Chrome browser changing the signature of the method, and has been resolved by updating the method name in the TraceMain HTML rule.
SR-D18589 · Issue 495714
Google Map API correctly loads pointer the first time
Resolved in Pega Version 8.2.3
When using Address Map control with enabled markers whose source is a datapage, the location in the map was redirected as expected to the address populated by the datapage, but the marker overlay that appeared by default containing address details and a link to "Open in Google Maps" did not load. Clicking on random places on the map caused it to load correctly. This has been corrected with the creation of a custom activity to get section markup that will use reload section with proper context to fix the issue.
SR-D17568 · Issue 498410
Handling added for interaction portal refresh containing many data parameters
Resolved in Pega Version 8.2.3
Attempting to refresh the browser when there were interactions opened in the Interaction portal and a huge amount of data on the parameter page caused the screen to blank and the interaction content was not displayed. Investigation showed that as part of the refresh, the displayOnPage GET request was sent with all of the parameters in the parameter page (data-model), resulting in a 400 Bad Request due to the browser URL length limitations. This has been resolved by removing the parameters which are not actually required for the displayOnPage GET call during the refresh case.
SR-C95857 · Issue 483549
JSON parsing added for identifier data type
Resolved in Pega Version 8.2.3
After upgrade, Service-REST was no longer mapping data as expected when the property was of type "identifier". Handling has now been added for mapping where property type is identifier and the incoming type is any valid value for identifier.
SR-D11909 · Issue 488670
Secure and httponly attributes added to Pega-Perf cookie
Resolved in Pega Version 8.2.3
A vulnerability test identified the Pega-Perf cookie as not having any attributes for secure and httponly. This has been resolved.
SR-D14201 · Issue 485963
MY system pulse receiver will parse originating tenant name to facilitate data page removal
Resolved in Pega Version 8.2.3
When using a node level data page on a cloud multi-tenant system to get the data from a data table, attempting to flush the data page by explicitly calling pzFlushDataPage was not flushing the page in all nodes of a tenant. This was traced to the system pulse used to communicate between MT nodes: the receiver node was not removing the data even after receiving the system pulse because the cache contained the page with a different key. The key formed contained the tenant name, and the receiver was not parsing the tenant name from the pulse message received. To resolve this, the system has been updated to parse the tenant name from the pulse message and set it on requestor. This allows the correct key to be formed, allowing the receiver node to remove the data page as expected.
SR-D15391 · Issue 484922
Add row works as expected when using Embedded Elsewhere with a modal grid
Resolved in Pega Version 8.2.3
When using Embedded Elsewhere, add row was not working on the first attempt for a grid launched inside a modal dialog. Changing the focus then resulted in the added row appearing. This has been resolved by updating the timing for the performInsertAction in the ui_grid JS.
SR-D20817 · Issue 499920
Async cache checking updated for interaction reload use
Resolved in Pega Version 8.2.3
A thread level data page using connect REST to get data from an external system with the "Reload once per interaction" checkbox ticked was being loaded asynchronously from the activity when by default the data page it was supplying needed to be loaded synchronously. Due to this, changes to the data in the external database were not reflected in the data page. This was caused when an async cache was referred and the freshness check for the data page instance did not consider the 'reload once per interaction' flag because it would cause the data page to load twice. The cache checking has been updated to resolve this.