SR-B37957 · Issue 303574
XSS security added for date property error message
Resolved in Pega Version 7.3
A cross site scripting filter has been added for pyErrorMessage in order to improve security.
SR-B37957 · Issue 278510
XSS security added for date property error message
Resolved in Pega Version 7.3
A cross site scripting filter has been added for pyErrorMessage in order to improve security.
SR-B37958 · Issue 296563
Radio button error highlight fixed for grids
Resolved in Pega Version 7.3
When a radio-button was configured as mandatory in a grid column, submitting the page without filling in the mandatory field did not correctly highlight the error. This was caused by the system not being able to find the correct label for the associated elements, and code has been added to find the correct label when the radio button is inside a grid.
SR-B37988 · Issue 298759
Fixed Addressing checkbox error in Connect-SOAP
Resolved in Pega Version 7.3
The addressing checkbox on the SOAP connector rule form was not being honored. This was a defect in the third party library 'praxis2-1.6.2-1.jar', and code has been added to disable the processing of WebSphere addressing headers when WebSphere addressing is false.
SR-B38034 · Issue 297014
Improved error handling for Usage Daemon
Resolved in Pega Version 7.3
The Usage daemon was exiting due to DB error and did not recover, leading to PALSnapshotImpl multiplying and causing an OOM. This was traced to missing error handling, and UsageDaemon has now been updated to handle a DB error without exiting.
SR-B38072 · Issue 297065
null-pointer exception fixed for REST XML samples
Resolved in Pega Version 7.3
The rule generation implementation for XML samples in REST wizard was faulty and throwing a NullPointerException if a resource name was the same as any of the complex node names in the sample XML. This has been fixed.
SR-B38101 · Issue 299647
Corrected DateTime corruption
Resolved in Pega Version 7.3
If "Display value using read-only formatting" was selected for a Date field, entering an invalid value caused the resulting HTML DOM to be displayed incorrectly when the page was refreshed. This was traced to missing handling for the exception resulting from the invalid data, and has been fixed.
SR-B38157 · Issue 301486
Added post-upgrade compatibility for agent tracing
Resolved in Pega Version 7.3
After upgrade, tracing agents was not working due to a change between versions in the method of tracing rules in rulesets of a remote requestor. Previously, rules were traced in the rulesets of the current requestor who initiated the trace; in newer versions, rulesets are fetched for batch requestors so all rules in rulesets accessible to browser requestor are not traced. In order to resolve this, a traceAllRulesets flag has been added for agent tracing so that all rulesets are traced and a note has been added to the settings window stating that in case of agents, all rulesets are traced.
SR-B38248 · Issue 294657
Rule search works after indexer cancel
Resolved in Pega Version 7.3
If the indexer was canceled from within the engine, the rule search function would not work until node restart. This was an error in the method used to call the cancel API, and has been corrected.
SR-B38248 · Issue 293250
Rule search works after indexer cancel
Resolved in Pega Version 7.3
If the indexer was canceled from within the engine, the rule search function would not work until node restart. This was an error in the method used to call the cancel API, and has been corrected.