SR-131266 · Issue 199637
Cleared exception during import of RAP by prpcUtils
Resolved in Pega Version 7.1.8
When attempting to import a RAP file through command line by using prpcUtils.sh, the build was successful and all the rules were imported but an SQL exception was generated related to the execution of Stored Procedure. The RAP file did not contain any code to execute stored procedure, so the execution was found to have been done internally by prpcUtils.sh. To prevent this, prpcUtils has been updated to use the data schema as the default schema for the connection while running against either of the DB2 dbs.
INC-196415 · Issue 686313
Performance improvements for revalidate and save
Resolved in Pega Version 8.7
In order to improve performance when working with very large numbers of class definitions, an update has been made to optimize the revalidate and save process by avoiding looking up all classes on the system instead using ClassDefinition for existence and checking ancestor data to ensure class is a Rule- or Data- descendant.
INC-144555 · Issue 603071
Changelog cleanup added for de-optimized properties
Resolved in Pega Version 8.4.4
Unwanted optimization was automatically added to properties for the Application-Work-Casetype class created using the wizard in the App Studio. Attempts to remove the optimization did not work: the property advance tab was showing the optimized classes details even after deleting and recreating the property. When a property is optimized the system adds entries to pr_changelog for the list of classes it has optimized. When the property was deleted, the pr_changelog was not cleared. This was a missed usecase, and has been resolved by overriding the Cleanup activity at Rule-Obj-Property class to delete the pr_changelog entry associated with that if it is present.
INC-196842 · Issue 683766
APIs updated for sending large attachments with MSGraph
Resolved in Pega Version 8.7
Sending mail using MSGraph was failing with the exception "Error during http request" when attachments were greater than 3MB. This was traced to changes made by Microsoft in the Graph API implementation which caused it to throw a runtime exception instead of the expected 413 status code and relevant message for the attachment size. To resolve this, an update has been made to ensure that any attachment larger than 3MB is sent via the Microsoft Outlook API.
INC-161984 · Issue 638858
Web Tier busy threads released on timeout
Resolved in Pega Version 8.7
Tomcat Web Tier Busy Threads were not being correctly released, causing stability and performance problems that included health check pings not receiving a thread to service the request so the node was marked as bad, users were quiesced, and the node replaced. Investigation showed the 'put' on the blocking queue did not time out when the queue was full and waited indefinitely, keeping the thread blocked. To resolve this, the system will use 'offer' on the blocking queue instead of 'put' to force thread release on timeout. In addition, debug logs have been added to understand when the offer (or Put) does not succeed and the state of the queue that is causing this issue; the debug logs for class com.pega.pegarules.session.internal.serverpush.RoboticAutomationImpl should be enabled only if the thread busy issue is observed and for limited time window while actively debugging.
INC-170599 · Issue 645222
DSS partition count setting made backward compatible
Resolved in Pega Version 8.7
After upgrade, the DSS 'dsm/services/stream/pyTopicPartitionsCount' used to limit the number of partitions was no longer working and instead used the default value of 20. This has been corrected and made backwards compatible.
INC-180479 · Issue 659639
DSS partition count setting made backward compatible
Resolved in Pega Version 8.7
After upgrade, the DSS 'dsm/services/stream/pyTopicPartitionsCount' used to limit the number of partitions was no longer working and instead used the default value of 20. This has been corrected and made backwards compatible.
INC-192078 · Issue 680064
DSS partition count setting made backward compatible
Resolved in Pega Version 8.7
After upgrade, the DSS 'dsm/services/stream/pyTopicPartitionsCount' used to limit the number of partitions was no longer working and instead used the default value of 20. This has been corrected and made backwards compatible.
SR-127319 · Issue 197788
Updated cache searching for Obj-Browse on a class mapped to external table
Resolved in Pega Version 7.1.8
Unnecessary queries were being fired while using Obj-Browse on a class mapped to external table. This was caused by a class mapped to an external table and using Obj-Browse on that class fired queries to the metadata to get the columns instead of searching in the caches. The system has been updated so that the caches are read instead of firing querying the metadata every time to get the list of columns.
SR-126448 · Issue 189959
Special character handling added to 'pzupgraderulemessages'
Resolved in Pega Version 7.1.8
The 'pzupgraderulemessages' activity was introduced to recalculate the pzinskeys of Rule-Message instances. These instances were migrated to a new table and the property, and pyclass name was made part of the key. Running this activity was made mandatory as part of upgrade/update process effective v 7.1.7. This activity selects each rule-message instance using its pzinskey and checks if it needs to be recalculated. To fetch the Rule-Message record, a plain SQL is used which did not escape any special characters in the pzinskey (\t, etc.).However, this lack of character escape was problematic for some customers who had existing rules utilizing special characters, so the activity has been updated to use a prepared statement which takes care of escaping characters in place of the generated plain SQL.