SR-D17249 · Issue 490109
Handling added to resolve Fusion chart tooltips issue in Google Chrome
Resolved in Pega Version 8.3
Tooltips for charts were not showing, and placing the mouse over the white area for the genaral tooltip in the charts made the white background blink. The error " Uncaught ReferenceError: FusionCharts is not defined at pyfusioncharts.theme.default_12208971721.js!!.js:1" was found in the Google Chrome console. Investigation showed that there was a recognition issue with Fusion charts when tooltips were enabled; this has been resolved by adding handling to check for an undefined value of the FusionCharts object within the declaration of the theme.
SR-D19281 · Issue 490124
Added handling for cases where Microsoft Internet Explorer causes a SAXParseException
Resolved in Pega Version 8.3
Numerous SAXParseException messages were seen in the log file, and the queryString showed the pyDeleteDocumentPg being referenced. This was traced to the method used by Internet Explorer to construct an HTTP request: Microsoft Internet Explorer sends the header and body of the request in separate TCP packets, but for an unknown reason in this case the body packet goes missing. To resolve this, a toggle has been introduced which will send the pyDeleteDocumentPg request as GET if pega.u.d.GET_REQUEST_DELETEDOCUMENT is set to true in userworkform. In a normal flow without this variable, the request will pass through the normal flow.
SR-D10775 · Issue 490171
Finalluy block added to Data-COS-.COS-Print streams
Resolved in Pega Version 8.3
A security scan detected a potential issue with the activity Data-COS-.COS-Print not closing the stream in a finally block. Although this activity is not in current use, a finally block has been added that will close all of the conditionally initialized streams if they are still initialized.
SR-D20533 · Issue 490195
Fixed Export to PDF page formatting
Resolved in Pega Version 8.3
A formatting issue was seen when using export to PDF; the first page contained only the title of the report as well as the filter, the generated date, and the number of records, and the exported data was included only from the 2nd page onwards. This has been corrected, and some performance improvements for the generation time were added.
SR-D14064 · Issue 490218
Support added for Tumbling Window size defined by field
Resolved in Pega Version 8.3
When using a Data Flow that called an Event Strategy that contained a Tumbling Window, all records were processed when given a user-defined option. However, trying to use a calculated "Defined by Field" option designed to time the windows out at the same time each hour resulted in only a small percentage of records being successfully written to the destination dataset. This was traced to the logic used by the out of order timers not supporting this use, and handling has now been added to resolve this issue.
SR-D18008 · Issue 490221
Improved processing handling for duplicate email attachments
Resolved in Pega Version 8.3
Errors were seen when saving attachments which were sent back and forth in an email conversation when Content Management is enabled. Handling has been added for a "file already exists" exception by appending the M- id to file name. In the attachment gadget, the system will evaluate if the file is a duplicate or not at the repository by using pxExists API. In Pulse, the system will append the pulse message ID to the filename before storing it to external storage. The unexpected behavior of the process for saving multiple files proceeding to attach a duplicate file even after it was removed from the modal has also been corrected.
SR-D22215 · Issue 490267
Hotfix Manager modified to enable cataloging double-digit patch releases
Resolved in Pega Version 8.3
In order to reflect the updated release process, the regex format used by the Hotfix Manager for the TargetRelease in the catalog has been modified to allow double digit patch versions. This updates the format to use the Catalog Version from the Product Source in place of the previous ML format.
SR-D21808 · Issue 490281
Filter values retained when editing a report with custom filters
Resolved in Pega Version 8.3
After running a report, if some filter values were selected and then the Edit Report button was clicked and simulated data and actual data fields were toggled, the filter values were lost when exiting the report editor. In the Edit Report Page, trying to drag a new filter condition was not working and the Change logic buttons were not visible. These functions worked as expected when a custom Filter section was not used. This was traced to the custom filter page being cleared in the pzCreateCustomFilterPage activity where the step for creating new page should be skipped if it already exists. To resolve this, a parameter will be set to show if the report was rerun in "reRunReport", and a check has been added in pzCreateCustomFilterPage to see if the report was rerun before running the other 'when' conditions.
SR-D21493 · Issue 490305
Corrected revision management with decision data rules
Resolved in Pega Version 8.3
When a new version of a decision data rule was created in dev studio and new propositions were imported or existing ones modified, the typical behavior was for the system to also automatically create a new version of the "pyEditElement" section even if the form was not changed. If this is done from revision management, the revision automatically creates a branch in the overlay application. If the revision contains a decision data rule, the branch contains an instance of the decision data rule and also an instance of the pyeditelement section, but when the revision was submitted, the generated package only contained the decision data rule and skipped the pyeditelement rule. This was traced to the pyEditElement section of the decision data rule not getting packaged because the package flag was not set to the section, and has been resolved by fixing the withdraw and reject scenarios by modifying the package flag in pyRemoveDDRules activity.
SR-D19081 · Issue 490370
Logic updated to handle Report Definition with a join
Resolved in Pega Version 8.3
When using a multi-select element on the UI with a report definition as a data source where the report used a join to another class where it was referenced by a prefix, setting that data source property as prefix.property resulted in the multi-select no longer showing any results when tested on the UI although the report definition returned results when run manually. This was traced to platform differences revealed by an upgrade, and the idGenerator function has been updated to handle a report definition with a join to resolve this.