SR-A24110 · Issue 246955
Fixed new tab opened on manual refresh (F5) of the Case Manager portal
Resolved in Pega Version 7.2.1
Doing a manual refresh (F5) of the Case Manager portal caused a new tab to be created with the harness displayed in it This was caused by the pyKey being incorrectly updated for static tabs, and has been fixed.
SR-A24968 · Issue 247952
Performance improvements for pyComputeSegmentLogic
Resolved in Pega Version 7.2.1
Caching and updated logic have been added to the pyComputeSegmentLogic activity to improve performance.
SR-A9107 · Issue 218864
Fixed required field entry validation flicker in autocomplete
Resolved in Pega Version 7.2.1
For autocomplete (chosen as required), when the down arrow is used and an option is selected, the error "field cannot be blank" is shown for a fraction of second. This has been fixed by moving the validationtype attribute firing from the time of selecting a value from grid to after the value is selected.
SR-A9481 · Issue 244466
Cleared validation error for fields not present on submit
Resolved in Pega Version 7.2.1
Validation errors were being thrown by fields that were no longer present or no longer relevant when a a modal window was launched and then canceled without filling in the fields, and the the main form was submitted. This was due to the popover/overlay close not clearing the DOM element, and has been fixed.
SR-A9651 · Issue 235540
Added null check for empty section rule properties in Design Time section containers
Resolved in Pega Version 7.2.1
In some cases, attempting to reopen a section container resulted in corrupted files. This was a Design time issue only, and was traced to empty property values. On doing a check-in , the clipboard page is put into the DB, but only properties with values were committed. Any properties whose values are empty were not committed. During retrieval, an exception was thrown because the properties did not exist in the XML. This has been resolved by updating the loadPropertyHtmlCache API of pzpega_ud_dvmanager to add null checks for pyFormat and pyValue properties which are being accessed.
SR-A14914 · Issue 231019
Onclick works with single quotes in button label
Resolved in Pega Version 7.2.1
A single quote in the label of a button was breaking the onclick functionality. This was a particular issue when using the French locale, as the localized value for "End other session to Release Lock" is set to "L'autre extrémité session pour déverrouiller". This has been fixed by removing pega:lookup tag RUF GenerateButton and adding a call to get the localized value and escape that value.
SR-D37421 · Issue 514593
Cross-site scripting security added to Marketing Offers
Resolved in Pega Version 8.1.8
Cross-site scripting protections have been added to Marketing Offers, which had a potential vulnerability when using Firefox.
SR-D45608 · Issue 519902
Correct service instance name passed for data flow in DSMStatus
Resolved in Pega Version 8.1.8
When using the Connect-HTTP service "DSMStatus" to provide the node and status information as seen on the various tabs of the Designer Studio > Decisioning > Infrastructure > Services landing page, using DataFlow as the service parameter for the HTTP service method resulted in an empty response when the expectation was to get the information regarding the cluster details of Dataflow node type. This was traced to the service instance name not being parsed correctly when used for Data Flow services, and has been resolved by ensuring the correct service instance name is passed for this use.
SR-D47618 · Issue 516300
Statistic rounding error in ADMSnapshot Agent with Oracle corrected
Resolved in Pega Version 8.1.8
While running the ADMSnapshot Agent, the exception "internal.mgmt.Executable) ERROR com.pega.decision.adm.client.ADMException: Failed to complete ADM Data Mart snapshot" was seen. This was traced to an issue with the rounding of performance statistics when using Oracle, and has been resolved.
SR-D54218 · Issue 518599
Deadlock in static Initialization of IntList resolved
Resolved in Pega Version 8.1.8
JVM Deadlock was seen related to the static Initialization of a subclass field in class com.pega.decision.strategy.ssa.runtime.collections.api.IntList . Thread dumps showed threads in RUNNABLE State that were parked to wait for class initialization, and this was traced to a missed sonar alert which failed in multi-threading. To resolve this, the system handling has been updated to prevent potential deadlock.