INC-170041 · Issue 655251
Check and error message added for filename containing "%00"
Resolved in Pega Version 8.7
At the time of file attachment or upload, if the file name contained % followed by two 0s (%00), the file upload mechanism distorted the UI and the Pega logo screen popped up. The file was saved properly in the ServiceExport directory, but while fetching the attachment info, the file was split in two because the engine considered %00 as a delimiter. This has been resolved by adding a file name check and a pyInvalidFileName field value to be used for an error message.
INC-184352 · Issue 671897
Predictive model snapshot generation updated for Java 11
Resolved in Pega Version 8.7
While the Simulation data export case type was executed as expected, the predictive stages showed zero records processed. This was traced to instances running on Java 11 which caused an issue with the snapshot process. This did not affect learning, but visualization and reporting were not working in Prediction studio. To resolve this, an update has been made to the snapshotID for Java 11 compatibility which will generate a random UUID instead of using a seed.
INC-176542 · Issue 668478
Removed unused function to improve Class rule save performance
Resolved in Pega Version 8.7
Clicking save on the Policy Class rule was not working correctly or was taking an excessive amount of time to respond. Adding property mapping in the External Mapping tab of the Class rule exhibited the same behavior. Investigation showed there was an infinite loop being invoked in the class ruleform, which was traced to the disableKeyEntries() function. As this function is no longer used, this has been resolved by updating the RF_RuleObjClassScript.js to remove disableKeyEntries and any function calls to it.
INC-139627 · Issue 604760
Legacy and new ID generation logging enhanced
Resolved in Pega Version 8.5.2
A DuplicateKeyException was generated when attempting to create a case. The root issue was related to the local modification of the reserved ID field in the database through a custom activity and was able to to be fixed with a local change. In order to improve diagnosing events such as this in the future, enhanced logging has been added to to the legacy and new ID generation.
INC-144601 · Issue 602422
Empty addresses removed from email
Resolved in Pega Version 8.5.2
After upgrade, an issue was seen when sending email to multiple 'To' addresses generated an exception if any 'To' address had an empty value. To resolve this, a check has been added that will remove any empty address from the recipientTo address list.
INC-135195 · Issue 598071
PD4ML library updated
Resolved in Pega Version 8.5.2
When generating a PDF from a report definition with more than 1000 records, the system would hang abruptly and stop responding. There was also a noticeable size difference in the generated file. This was an issue with the included version of PD4ML, and has been resolved by updating the version from 4.0.6 to 4.0.9fx1.
SR-C11319 · Issue 352584
Mobile dropdowns accept data binding from all sources
Resolved in Pega Version 8.1
When entering reports on Mobile, dropdowns were being reset after filling in autocompletes and other dropdowns. This was traced to data binding not being supported for sources other than Associated, and changes have been made to the generateDropdown RUF to support data binding for all sources of dropdown to correct this.
SR-C13426 · Issue 356652
Delta sync enhancement to improve performance
Resolved in Pega Version 8.1
When actions were bundled into a single delta sync request, the resulting package contained a large amount of redundant information that caused performance issues during handling. To improve performance, an enhancement has been made to the process so that only the modified properties of pyWorkPage are sent during delta sync.
INC-180594 · Issue 670957
Filtering added for DisableDormantOperators
Resolved in Pega Version 8.7
When running the Disable Dormant Operators agent, many operators were seen which were dormant but not disabled. Investigation showed the activity was fetching all of the operators without filtering the deactivation state. This has been resolved by adding a filter condition in pzDisableDormantOperators to fetch only deactivate state users.
INC-175205 · Issue 652531
Agent restart made more resilient
Resolved in Pega Version 8.7
During a timeout outage, agents intermittently encountered a NoClassDefFound error and were disabled. After the database connection was restored, the agents were not automatically restarting. This has been resolved by making the code more resilient to errors; agent will be restarted when a temporary issue is detected, and the restart will be immune to most exceptions.