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.
SR-B38262 · Issue 295697
Fixed case error in DayOfMonth property
Resolved in Pega Version 7.3
When trying to add a DateTime Property/Column with function 'Day of the month', an exception was generated. This was due to an error in the wrapper creating the Function Alias name 'DayofMonth' instead of the correct 'DayOfMonth', and has been fixed.
SR-B38290 · Issue 295916
Fixed screen truncation with Mashup
Resolved in Pega Version 7.3
Screen content was truncated on refresh when using Web Mashup with Firefox and Microsoft Internet Explorer 11. The resize harness has been updated to call pega.Mashup in a timeout in order to fix this.
SR-B38297 · Issue 300607
Save button with close fixed for Internet Explorer with Mashup
Resolved in Pega Version 7.3
When using a createNewWork Mashup that has a button for Save with the 'Close After Save' option checked, the call to close the work object was never fired. This was traced to Internet Explorer excluding the port number while considering cross domains, and has been fixed by adding a pega.Mashup check along with crossFrame.