SR-C89619 · Issue 429575
Custom section filters retained during refresh
Resolved in Pega Version 8.1.4
Filtered values were not retained on refresh when filtered using a custom section. This has been resolved.
SR-C90467 · Issue 429609
Validations are correctly run on rescheduled reports
Resolved in Pega Version 8.1.4
When using the OOTB schedule report functionality, UI validations were bypassed if the existing schedule was deleted and the report was rescheduled. This has been corrected by updating the Review harness to display the Perform harness when clicking Update.
SR-C77121 · Issue 423114
Code adjusted to prevent looping with CyberArk
Resolved in Pega Version 8.1.4
In order to avoid looping issues when using CyberArk integration, the reference to PRMiniLoader has been removed from PRBaseLoader.
SR-C93555 · Issue 431600
BulkMover updated to not treat Numerics as strings
Resolved in Pega Version 8.1.4
When attempting to update Pega platform 8.1.1 to 8.1.3 with Oracle on a Windows machine with German locale using the out-of-place upgrade of the rules schema, the migration failed at the migration step with the error message "ORA-01722: Ungültige Zahl". This was traced to BulkMover failing when trying to convert a string to a Numeric due to the locale using commas as the decimal separator, and has been resolved by updating BulkMover to not treat Numerics as strings.
INC-187350 · Issue 703198
UUID added to iOS direct photo upload to differentiate filename
Resolved in Pega Version 8.6.4
When "Content Storage" with the option "Store in repository" was enabled on the "Integration" tab in the Application definition, it was not possible to add more that two attachments to a case with an iPhone when directly capturing a photo through the camera app instead of uploading the photo as an attachment using the gallery. When using the default "Store in Pega database", the additional photos could be uploaded directly from an iOS camera without any errors. Investigation showed that when "Store in repository" was enabled, a file name conflict check was done in the repository. Because the iOS camera app saves/uploads every image as "image.jpg", this caused the error when checking for a filename conflict in the repository. This has been resolved by adding code to append a UUID to the attachname when the device is mobile and browser is Apple Safari.
SR-C74054 · Issue 422026
Handling added for summary columns in Export to Excel
Resolved in Pega Version 8.1.4
When a field has an aggregate function in Report Definition, the column alias changes and is not the same as the property name. The consequence is a mismatch between the result set column name and the property name from the property list created beforehand. This results in blank fields when using the "pxDownloadDataRecordsAsCSV" activity for Export to Excel. In order to support the export of summarized columns in Report Definition, an enhancement has been added that uses the column label as an alias for aggregate fields in the native SQL builder of the exportData API to form a map between the property name and the alias name and use it while iterating over the result set.
INC-208424 · Issue 704598
Custom header character encoding for Subject added
Resolved in Pega Version 8.6.4
Case correspondence that contained a Subject with accent characters such as "Invitation à être" was being rejected by MailJet on the basis of encoding issues on the "Thread-Topic" when using custom headers. The error "BAD HEADER SECTION, Non-encoded non-ASCII data (and not UTF-8)" was generated. This was traced to the Send Email Smart Shape handling when using custom headers, and has been resolved by encoding the Subject before appending it to the Thread-topic header while adding custom headers.
INC-199469 · Issue 707513
PDF margins made available as parameters
Resolved in Pega Version 8.6.4
After update, margins were different in exported PDFs. This was due to upgraded jar files: PD4ML v3 used setPageInsets(new Insets(top, left, bottom, right)) , but the v4 jar uses setPageMargins(new PageMargins(left, top, right, bottom)) . Because the order of values (20, 10, 10, 10) were not changed this produced a different result. To resolve this, PD4ML margins are now available to be set as parameters: Param.pyMarginLeft, default value 20 Param.pyMarginTop, default value 10 Param.pyMarginRight, default value 10 Param.pyMarginBottom, default value 10 When standard activities like HTMLToPDF / pyViewAsPDF / pyAttachAsPDF are used, add a Property-Set step before calling the activity to add the necessary margin parameters. When CreatePDF smart shape is used, set the parameters via the connector of the CreatePDF.
INC-204349 · Issue 704563
Updated check for portal name with search
Resolved in Pega Version 8.6.4
After update, using search from a Cosmos portal landing page launched the results in a new tab, and the logoff menu did not show which portal was being used. This has been resolved by updating the 'when' rule to check if pxThread.pxPortal contains the portal name rather that testing for equality.
INC-184798 · Issue 703268
PRconfig added for JVM user/password
Resolved in Pega Version 8.6.4
The setting Dcom.sun.management.jmxremote.local.only=true has been added for use when JMX authentication is enabled by providing jmxuser/password through prconfig.