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-143599 · Issue 598771
Non-template RDL time value handling updated
Resolved in Pega Version 8.5.2
The Time value displayed on clipboard and data designer differed from the value shown on user work form when using a categorized repeating dynamic layer rendered in non-template mode with the Datetime control configured inside the RDL. This was traced to the Time string being considered as a date when using this configuration and calling the engine API, and has been resolved by ensuring this configuration will call the correct Time API instead so that the timeofday property value will be formatted correctly.
INC-132176 · Issue 588809
Cache cleared before PDF generation to ensure proper fonts
Resolved in Pega Version 8.5.2
The font File OCRAEXT.ttf added at location "/usr/local/tomcat/fonts" was not being picked when the PDF was generated via an agent execution. When the same activity was run manually, the font issue was sporadic. Investigation showed that when multiple apps use the same props directory but different fonts directories, the handling would sometimes cause one app to use another app's props file with the result of the improper fonts mapping. To resolve this, an update has been made to clear the cache before PDF generation starts to ensure the library reads the proper fonts.
INC-132219 · Issue 580266
Values with accent characters are sorted properly
Resolved in Pega Version 8.5.2
Table Layout column values using a pagelist were not sorted properly when the data contained French accent characters. This has been resolved.
INC-144102 · Issue 605882
Values with accent characters are sorted properly
Resolved in Pega Version 8.5.2
Table Layout column values using a pagelist were not sorted properly when the data contained French accent characters. This has been resolved.
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-136768 · Issue 588450
Question Wizard import will downcase answer types to match system requirements
Resolved in Pega Version 8.5.2
The Question Upload wizard would not create a File type question while using a survey template. The template has a column Answer mode in which accepts an input of the type of answer expected, but in this use case "File" was given instead of "file", resulting in the question being created using the default values. To resolve this, during the import process when the system parses the file and gets the contents from the data using the pzSetdefaultValuesforQuestions DT, mode values will be explicitly set to lowercase.
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.