SR-116597 · Issue 169929
Correct report name displaying on chart reports
Resolved in Pega Version 7.1.7
In Case Manager reports, maximizing a report containing a chart showed the URL as the report name if the report title parameter did not have a value. This field has been updated to default to the report's title if the name has not been explicitly set.
SR-116679 · Issue 169078
"Save preferences" button visibility corrected
Resolved in Pega Version 7.1.7
The ability to save report filtering preferences for Summary View was only appearing if the report included an interactive chart. The system has been updated to present the 'Save Preferences' button in all report types.
SR-116903 · Issue 167940
Recent Explorer item handling corrected
Resolved in Pega Version 7.1.7
When opening a Scheduled item from Recent Explorer, an incorrect flow was being called and the Review Harness buttons (which are based on flow parameters) were incorrect. This was traced to a missing TaskWrapper activity, and has been corrected. In addition, a process was added to check property as well as parameter in the Review Harness.
SR-116941 · Issue 168143
Improved performance for sending queued messages
Resolved in Pega Version 7.1.7
LogToSpecifiedAppender was experiencing poor performance in some situations caused by duplicating locking attempts while processing an appender to send queued messages. To improve this, code changes have been made to smooth locking and avoid searching appenders when dynamic appenders are configured.
SR-117131 · Issue 167711
Corrected Rule cleanup utility
Resolved in Pega Version 7.1.7
The Rule Cleanup utility deletes instances from pr4_rule_ruleset that contain old ruleset versions. Some Rule-RuleSet-Name instances have rulesets and were deleted incorrectly. To correct this, the utility has been modified with an additional 'where' clause to restrict deleting Rule-RuleSet-Name instances.
SR-117252 · Issue 174014
Modified SaveAs function for reports to avoid duplication
Resolved in Pega Version 7.1.7
After using "SaveAs" on an existing report, subsequently using "Save" caused two instances of the report to be saved into the database with the same key. The SaveAs function has been modified to correct this.
SR-117847 · Issue 172996
Handling enhanced for custom system names
Resolved in Pega Version 7.1.7
If the system.name property in setupDatabase.properties was updated to reflect a custom System Name during ruleset migration, the value was not being used by the software update process and the resulting error caused a batch failure. There was a workaround of explicitly setting the system name in the field env name="Identification/SystemName" value=, but this has been updated to fetch the name from the db. In addition, the query that fetches the system name has been modified with a check to make sure that there is at least one requestor for the name it fetches.
SR-118144 · Issue 171689
Corrected date display in graphs
Resolved in Pega Version 7.1.7
The incorrect date was being displayed in graphs after using the Month function alias to get the first day of the month. The grid displayed when running the show data option in the graph contained the correct date. This was caused by a problematic time conversion in graphs for a specific time zone, and has been fixed.
SR-118174 · Issue 173341
Sorted Report Definition drill downs corrected
Resolved in Pega Version 7.1.7
For some configurations, the Report Definition drill down did not work when it has been sorted. This manifested as either no results returned by the drill down report or an error message related to invalid filter values. This was caused by an error in calling the page sort in cases where 'do not display group headers' was checked, and has been corrected.
SR-118528 · Issue 175205
Fixed server error alert generated by portal logout
Resolved in Pega Version 7.1.7
A "Server Error " error was being generated when logging off from "List views/Summary Views" in the Portal Dashboard. This occurred when the request to unload the page reached PRPC after the endsession completed and the request to unload was unable to find the associated session on the server as it has been already invalidated. The Wizard_MainWindow HTML rule has been modified to smooth the timing and clear the clipboard properly.