SR-A23979 · Issue 246353
Revamped help docs to clarify ServiceExport directory config
Resolved in Pega Version 7.2.1
An error in the help documentation did not correctly outline the method for changing the ServiceExport directory by modifying prconfig.xml. The directory location is hard coded to StaticContent/global/ServiceExport in the temporary directory, but the location of the temporary directory is configurable using the Initialization/explicitTempDir setting. Changes have been made to the help files to clarify this.
INC-174567 · Issue 651121
Permissions added to handle Openshift installer image
Resolved in Pega Version 8.7
When running the install process on an Openshift test cluster, the process failed with a permissions error while attempting to download the postgresql-42.2.12.jar. This has been resolved by ensuring the root group can write to the distribution files.
INC-175197 · Issue 651114
Permissions added to handle Openshift installer image
Resolved in Pega Version 8.7
When running the install process on an Openshift test cluster, the process failed with a permissions error while attempting to download the postgresql-42.2.12.jar. This has been resolved by ensuring the root group can write to the distribution files.
SR-A16337 · Issue 232778
OCXinstaller install.bat script for Windows explicitly sets .cab file path
Resolved in Pega Version 7.2.1
The OCXinstaller install.bat script for Windows failed if it was run from the command line in a directory other than the one the script was stored in. The root cause was the batch file not finding the actual .cab files, as the batch file assumes the cab files are in the current path. The install.bat file has been updated to always uses the path of the batch file as the current path.
SR-A21487 · Issue 241066
Corrected GRANT generation for DB2 users
Resolved in Pega Version 7.2.1
When importing a RAP with a view into a DB2 10.1 LUW database, the GRANT statements were failing because of invalid syntax and the view creation was not executed. This was caused by the user name not being properly appended to the grant statement generation for DB2 users, and has been fixed.
INC-173663 · Issue 651302
Resolved Push Node Daily Information exception
Resolved in Pega Version 8.7
The "Push Nodes Info Daily" agent was generating an exception on each of the nodes. This has been resolved by enhancing the PegaAESRemote code to handle the exception and get the node info locally, then push it to the console when it is not able to get it via the cluster management API.
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.
INC-189781 · Issue 677816
Database Transaction Log update overflow resolved
Resolved in Pega Version 8.7
When automatic.resume=false was encountered during an update, cleaning up the existing codeset from previous updates ended up filling up the database transaction logs and caused the update to fail. This has been resolved by updating the process of clearing the codeset so it doesn't overflow the transaction log.
SR-A22147 · Issue 244096
Autogenerated prconfig sets v6 or v7 based on detection
Resolved in Pega Version 7.2.1
The autogenerated prpcUtils prconfig.xml file was setting the database/storageVersion to 6. In order to facilitate other setups, a flag has been provided in prpcUtils.properties as pega.storageVersion which will set the value in generated prconfig.xml to an empty string so the engine handles setting this to 6 or 7 in the same way that is possible when running the system.
INC-178002 · Issue 663770
Restore point handling updated for absent pzpvstream column
Resolved in Pega Version 8.7
While executing the “get restore point” action for rollback, a PZPVSTREAMerror error occurred with the message "(util.HistoryCollectorDataModel) WARN|Rest|SystemManagement|v2|restorepoint - History collection for the table will be slow because it does not have all of the required columns". This was a missed use case for Robotics Automation not having a pzpvstream column for one of the tables; this has been corrected with a check to validate for pzpvstream column so the system will not seek history records if the pzpvstream column is not present.