INC-131384 · Issue 584856
Documentation updated for troubleshooting inline images for email
Resolved in Pega Version 8.5.2
Inline images were not showing by default when sending emails. To assist in this, the troubleshooting information for email has been updated with the following information: Correct configuration for display of inline images via Email bot is one that is shipped standard. To support Rich text in email display via Email bots, Email body must be stored 'As HTML attachment' (the setting on auto generated Service Email rule). In addition, no other setting on listener must be changed especially 'Embed inline images'(should remain unchecked) on Email listener rule. Combination of these 2 settings causes Email bot to save - 1. Email body as attachment 2. All inline images as attachment At runtime UI display, these 2 are recombined to display proper email. This is done in order to increase performance because images are lazily loaded.
SR-D92590 · Issue 553059
PostgreSQL information updated in Platform Support Guide
Resolved in Pega Version 8.5.2
The Platform Support Guide has been updated to reflect the following:Postgresql-42.2.14.jar supports PostgreSQL 8.2 or newer, and requires Java 6 or newer (Pega only supports Java 8 and 11); this driver also contains support for SSL and the javax.sql package. Prior versions of this .jar file have known problems. Do not use these versions: • 42.2.11 – creates an exception which stops Pega Platform startup • 42.2.12 and 42.2.13 – known vulnerability issues (CVEs) reported
INC-126942 · Issue 583398
Report Shortcuts resolve datapage parameter references
Resolved in Pega Version 8.5.2
After upgrade, no results were displayed in case manager portal report browser. This was traced to a data page value that was not resolved at runtime when a data page was used in the report definition shortcut to pass a parameter value. Investigation showed this was due to a change made for v8.4 to correct an issue with data page variables that were not persisting if a report was made with pre-exisiting filters. To resolve this, the logic related to pzResolveCopyFilters has been updated.
INC-133482 · Issue 605002
Corrected isExternal flag not resetting
Resolved in Pega Version 8.5.2
If an extraction referred to external tables, an isExternal flag that was set to true during the Extraction process did not get reset to false for the tables which were not referring to external. This has been corrected.
INC-139295 · Issue 588138
Report Shortcuts resolve datapage parameter references
Resolved in Pega Version 8.5.2
After upgrade, no results were displayed in case manager portal report browser. This was traced to a data page value that was not resolved at runtime when a data page was used in the report definition shortcut to pass a parameter value. Investigation showed this was due to a change made for v8.4 to correct an issue with data page variables that were not persisting if a report was made with pre-exisiting filters. To resolve this, the logic related to pzResolveCopyFilters has been updated.
INC-140110 · Issue 600398
Large filter values accepted in Report Definition edit
Resolved in Pega Version 8.5.2
Report definition edit filter values were not accepting large comma separated values properly. This has been resolved by modifying the logic in RRFilters_Logic to use ReportFilter.getReportFilters.
INC-141322 · Issue 594510
Resolved drill up doubling the filter box
Resolved in Pega Version 8.5.2
When opening a report with a visual graph, clicking on one of the filtered options, leaving this box open (not submitting it) and then clicking on a bar in the visual graph of the report showed the contents of the graph, but then clicking on the report link to go back to the report overview caused a doubled filter box to be displayed. The report would then have to be reopened before being able to continue. The problem was that the value of .pyUI.pyConfigSecToShow was still set to "filter" after the drill down. When the drill back up happened, the report was trying to show the filter configuration section from before but the context was no longer available and it failed. This has been resolved by adding a call to pzCancelFilterLogicChanges in pzDrillUpReport to set the filters to the previous values and reset the value of pyConfigSecToShow.
INC-143191 · Issue 596469
Scheduled tasks landing page shows all tasks
Resolved in Pega Version 8.5.2
Due to pzGetScheduledTasks listview having a hardcoded limitation of 500 records to be fetched, not all scheduled tasks were being shown in the scheduled tasks landing page. This has been resolved by modifying the pyCreateSummary activity to use a newly created Report Definition to fetch data instead of list view.
INC-144103 · Issue 599681
Updated filter logic for filtering on a DateTime column
Resolved in Pega Version 8.5.2
When a class join was used in a report definition, the error "The Filter Logic used in the report is invalid" appeared while filtering rows of a report definition results on a DateTime column. This was a missed use case, and has been resolved by modifying pzGridSortPaginate to convert the data type value into the proper casing.
INC-145810 · Issue 599465
BIX log shows correct corrupted BLOB pzInskey
Resolved in Pega Version 8.5.2
An update has ben made to ensure the correct inskey is shown in the BIX logs for a corrupted BLOB.