SR-D47975 · Issue 514014
OpenRuleAdvanced updated
Resolved in Pega Version 8.4
After upgrade, the Update Page and Append and Map to step in Data transform was generating the error "No Server connection while giving page name to Target and Source". This was traced to the OpenRuleAdvanced_OverLabel control, and investigation showed that a variable was not being resolved when invoking pzEncryptURLActionString. This has been resolved by updating OpenRuleAdvanced and reimplementing two parameters as well as moving the call of these variables to the beginning of the script. Security has also been improved by moving some of the encryption to SafeUrls.
SR-D48248 · Issue 517239
XSS filtering added to URLs
Resolved in Pega Version 8.4
XSS filtering has been added to prevent the injection of a script into a URL using ViewXML.
SR-D48751 · Issue 515538
Pega unit for case type records user inputs
Resolved in Pega Version 8.4
When creating a Pega unit for the case type by selecting Actions -> Record test case for Case, the user inputs were not recorded for embedded page properties. This has been corrected.
SR-D52138 · Issue 537507
Property setting corrected for On Join and Exclusion shapes in Expression Builder
Resolved in Pega Version 8.4
The properties for the defined page did not appear when using the type-ahead feature to select properties for the On Data Join and Exclusion shapes in Expression Builder. This was an issue related to the property being referenced for setting the context in the expression builder, and has been corrected.
SR-D65401 · Issue 528958
Parameter page retained after strategy test case checkout
Resolved in Pega Version 8.4
After a test case for a Strategy was created, it passed in the initial run but then failed after checkout of the test case. This was traced to an issue with the activity pzCheckAndUpdateParameters for strategy, and has been corrected.
SR-D67614 · Issue 527487
Tracer issues resolved for Google Chrome broswer
Resolved in Pega Version 8.4
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 Google Chrome browser changing the signature of the method, and has been resolved by updating the method name in the TraceMain HTML rule.
INC-173986 · Issue 668934
Updated survey refresh API for switching radio buttons
Resolved in Pega Version 8.6.3
After configuring a picklist with multiple options in a survey framework, it was not possible to select a radio button when toggling between radio buttons on the UI. Investigation showed the values of the radio buttons were not published to Clipboard, causing pyAnswer to be blank. After detaching the webwb_pzsurvey_ui_userscript.js the value was posted correctly and the visible WHEN was working as expected. This has been resolved by updating pzsurvey_ui_userscript to add a timeout on the refresh API call when switching between radio button options.
INC-175533 · Issue 678910
Improved Page compare for page groups
Resolved in Pega Version 8.6.3
Field level auditing on embedded properties sporadically did not report the "old" value when a property was modified even though the page was listed as "Modified". This has been resolved by adding logic to the pxComparePages algorithm to treat Lists and Groups differently. Now Page and Value Groups will use pxSubscript as the primary way to detect add and deletes.
INC-179769 · Issue 671022
Document generation new line formatting made consistent
Resolved in Pega Version 8.6.3
The GenerateWordDocument API and Generate Document shape were not adding new line to a Word document even when Text Area format was used. This was traced to a difference in document generation which varied between adding \n and adding \r\n for new line, causing inconsistent behavior, and has been resolved.
INC-182152 · Issue 667395
Special character handling updated for export MapValue to Excel
Resolved in Pega Version 8.6.3
The Excel download was failing when the Row/Column definition or column configuration of a map value contained an equals sign (=) or < > brackets inside quotation marks. This has been resolved by adding an update that will evaluate the comparator value at the start of the row condition value, and row condition value and row condition operator will be set separately.