INC-168203 · Issue 641337
Improved performance for data flow runs
Resolved in Pega Version 8.6.1
Nodes were intermittently going into safe mode after a service registry heartbeat failure. Investigation found that some of the activities were performing an Obj-Browse that invoked report definition logic to call the database classmap. This has been resolved by modifying the implementation for the initialization and caching of list of classes in a table.
INC-169055 · Issue 646674
Performance improvements for database queries and archiving
Resolved in Pega Version 8.6.1
In order to improve the performance of database queries, repetitive unnecessary database calls have been removed, archival queries have been simplified, and diagnostic metrics were added. Optional batch requestors have been added to all archival services with their own DSS settings to allow processing more cases in parallel. It is recommended to create 2 additional indexes to help with the archival process. The indexes will be on:pegadata.pr_metadata (pyisparent, pyobjclass, pyarchivestatus) INCLUDE (pyinskey); pegadata.pr_metadata (pyisparent, pyarchivestatus) INCLUDE (pyinskey);
INC-169856 · Issue 649460
Personalized table sort order limited
Resolved in Pega Version 8.6.1
After implementing a personalized table, the query started adding more 'order by' sorts, causing system impact. This was traced to the pzPopulateSortOrder activity Implementation having different constants assumed for the same purpose (999 in one place and 99999 in another), and has been resolved by updating the logic in step 1 and step 2 to disregard sort orders higher than 999.
INC-170389 · Issue 645001
Updated authentication for report filter screen
Resolved in Pega Version 8.6.1
If the report filter screen was shown first after clicking on the report link in the report browser, an error is generated for users but not for administrators. This has been resolved by registering the activity and adding a BAC registration section to the prompt filter section.
INC-175622 · Issue 652279
Screen reader announces report names
Resolved in Pega Version 8.6.1
An update has been made to pyReportBrowserItem to ensure names of the reports on the report browser are read correctly.
INC-176205 · Issue 655939
Secure shared link generation added to scheduled reports
Resolved in Pega Version 8.6.1
When a scheduled report with a link was sent in email, clicking the link displayed an access denied message. To support this use, logic has been added to pytaskoutputprocessor in the pega-scheduledtask-reporting and pega-scheduledtask classes that will create a secure encrypted URL using the PublicLinkURL function.
INC-176385 · Issue 657671
Corrected blank lines for hidden report filter criteria
Resolved in Pega Version 8.6.1
When the report browser had five filter criteria for a report and only the last two were made visible due to conditions, three blank lines were shown above the visible filters. This was traced to the Report Definition column filter showing the grid row as empty space when "Filter Not Visible in Viewer" was selected, and has been resolved by adding an inline style to PzPromptGrid.
SR-D28060 · Issue 498749
Cross-site scripting filtering added to App Studio
Resolved in Pega Version 8.3.1
The pzDisplaySpaceFeedTitle control which is used to display the audit feed in Pega App Studio has been updated with cross-site scripting filtering.
SR-D28293 · Issue 498233
Pega Survey answer values support special characters
Resolved in Pega Version 8.3.1
When using a Complex radio control (RadioButtonComplexQuestionSurvey), a selected option that used answer values containing special characters was cleared on refresh. This was traced to a mismatch between strAnswer and strValue in the control logic, and has been corrected.
SR-D30428 · Issue 503424
Added handling for deprecated UI Kit in Pulse OpenURLInWindow
Resolved in Pega Version 8.3.1
After upgrade, clicking on a link in a Pulse comment opened a new window with an error message indicating no content was returned. Investigation showed that if an older deprecated version of the UI kit was used, 'Open URL in window' was configured as Run Script function. The more recent versions use an OpenURLInWindow action. To resolve this, the script has been updated to use an action and pass the correct parameters.