SR-D6721 · Issue 488973
Updated report widget drilldown logic for better non-ASCII character support
Resolved in Pega Version 8.1.6
When a report in the report widget had a drilldown chart with a parameter containing certain non-ASCII characters, no entries for the drilldown filter were shown even when there was data that matched that filter. This was traced to the drilldown JavaScript for dashboard report widgets encoding the drilldown parameter twice, causing characters that were Unicode but not ASCII to be corrupted. This has been resolved by updating the logic for pzpega_chart_legacydrilldown.js and pzpega_control_actions_reportdefinition.js to ensure the parameter is not encoded twice.
SR-D8390 · Issue 488003
Handling added for runtime exception on upgrade due to inaccessible external schema mapping
Resolved in Pega Version 8.1.6
If a system used external schema mapping, attempts to upgrade were failing with the error "Caused by: com.pega.pegarules.pub.database.ConfigurationException: Unable to obtain data source "java:comp/env/jdbc/PegaRULES", as it is undefined". This was traced to configuring external DADNs which were not accessible from the server where the upgrade was being run: an upgrade will fail if it cannot connect to an external datasource even if no changes need to be made to that datasource. However, because a PRRuntimeException was unexpectedly being thrown instead of a Database Exception, the exception was not properly caught and handled. This has been corrected.
SR-D9142 · Issue 482314
Support added for custom JVC arguments for Cassandra
Resolved in Pega Version 8.1.6
An enhancement has been added to support specifying custom JVM arguments for Cassandra. This allows uses such as enabling GC logging for cloud deployments, or to increase the native transport queue size for read-heavy deployments.
INC-194932 · Issue 686277
Handling updated for offlineWorkIDs map
Resolved in Pega Version 8.8
Intermittent failures were seen when deleting attachments on Mobile. These were traced to pega.ui.DCUtils being undefined, and has been resolved by populating the offlineWorkIDs map for attachment-related actions.
INC-188469 · Issue 714843
Updated retainLock for DoClose activity
Resolved in Pega Version 8.8
After sending an external email notification from a case, attempting to use the "close" button resulted in an access denied error. This was traced to a missed use case for recent security improvements which resulted in not setting the required parameter retainLock for the DoClose activity, and has been resolved.
INC-192673 · Issue 689552
Tab highlighting updated
Resolved in Pega Version 8.8
Not all elements were indicated with yellow highlighting when tabbing through the screen. This has been resolved.
INC-194180 · Issue 704636
GetChildcases handling updated for large numbers of cases
Resolved in Pega Version 8.8
When a very high number of child cases being processed contained a wait shape that was dependent on the movement of a parent case, some of the cases were moved to the next step of the flow automatically while others required a manual command to ResumeFlow. In extreme cases where many child cases were waiting, a node crash could occur. This was traced to the pzGetChildcases report having a maximum value of 500 lines, and has been resolved by increasing the maximum number of rows to retrieve to 9999 in the Data Access Tab of the pzGetChildCases report definition. In addition, the pxCheckFlowDependencies activity has been modified to perform with a higher number of cases, and DSS(MaxRecords) logic has been added to split the child cases into multiple queue items for each access group to decrease load on each thread process.
INC-201723 · Issue 719854
Audit message displays correct parameter value
Resolved in Pega Version 8.8
The Audit message showed "{1}" instead of displaying the parameter value dynamically. This was traced to the pyInstructions field value which contained the message "Please approve or reject this {1}", and has been resolved by updating the pzInstructionsForApproval rule so the correct value is displayed.
INC-203595 · Issue 702360
Updated retainLock for DoClose activity
Resolved in Pega Version 8.8
After sending an external email notification from a case, attempting to use the "close" button resulted in an access denied error. This was traced to a missed use case for recent security improvements which resulted in not setting the required parameter retainLock for the DoClose activity, and has been resolved.
INC-207218 · Issue 706367
Check added to prevent duplicate approval by single agent
Resolved in Pega Version 8.8
When using a cascading Approvals process supported both by a web access button or by responding via email, a single agent could use both methods and advance a case an additional step as if they were the next approval level. This was due to the system only checking the pzInsKey when processing the approval while the assignment key will be the same for the cascading approvals assignments. This has been resolved by introducing a datetime check to validate if the email approval assignment creation datetime and the one in the database have same value; if yes the approval process will proceed and if not it will exit.