INC-150038 · Issue 614826
Data Type local data storage snapshot history updated
Resolved in Pega Version 8.6
When a History Class Data object was created, two snapshots were made - one with value and another with no value. This was traced to a 'when' condition that evaluated whether to add history when deleting a record from records editor, and this issue has been addressed by removing the condition as the history-add step takes care of checking if there is a dedicated table or not.
INC-184669 · Issue 666183
Locking issue resolved for passivating requestor
Resolved in Pega Version 8.4.6
A null pointer error was seen when passivating a requestor related to AbstractPassivationStorage.deleteAssociatedRequestorContents. This was traced to the lock to being called on the app requestor and not properly released. This has been resolved by ensuring the lock will be cleared when the Requestor is destroyed/returned.
INC-171753 · Issue 649441
Checks for Apache Tomcat 6 with MSSQL removed
Resolved in Pega Version 8.7
After implementing a specific local Tomcat configuration that removed the Tomcat version number from displaying on Tomcat standard error screens, the error "Tomcat 6 not supported or unable to detect version for custom Tomcat: Apache Tomcat. Contact Pega Customer Support!" appeared and Tomcat failed to start. Because Tomcat 6 was not supported for use with Microsoft SQL Server Systems, Pega used the ServletContext.getServerInfo() method to determine the Tomcat version; if the system used Tomcat 6 or an undetermined version in combination with MSSQL then the system would purposefully not start. As Tomcat 6 is no longer supported in Pega 8.5.2 and above, this check is unnecessary in those versions and the Tomcat version 6 checks in ClassMapImpl have been removed to allow serverAllowsMerge to return as true.
INC-152435 · Issue 612995
Hardcoded cluster password deprecated
Resolved in Pega Version 8.6
An unneeded hardcoded cluster group password has been removed in 3.8 version of Hazelcast as this use has been deprecated.
INC-136019 · Issue 584809
EmailListener restart correctly reflects Inbox folder change
Resolved in Pega Version 8.6
The Email Listener did not pick up a change in the INBOX folder name when the listener was restarted, but did when the server itself was restarted. This was due to the folder name being cached but not being included in the cache key: a cache change only occurs when the key of the cache changes. This meant that even after changing the folder name, the object was treated as 'not changed' and returned the older connection with older folderName. This has been resolved by adding the foldername to the cache key.
INC-145255 · Issue 600273
EmailListener restart correctly reflects Inbox folder change
Resolved in Pega Version 8.6
The Email Listener did not pick up a change in the INBOX folder name when the listener was restarted, but did when the server itself was restarted. This was due to the folder name being cached but not being included in the cache key: a cache change only occurs when the key of the cache changes. This meant that even after changing the folder name, the object was treated as 'not changed' and returned the older connection with older folderName. This has been resolved by adding the foldername to the cache key.
INC-177470 · Issue 657142
Optimization prconfig check added for TableInformationMap
Resolved in Pega Version 8.7
A prconfig setting check has been added to the TableInformationMap use of OPTIMIZE_SMA_QUERY during its foreign key lookup.
INC-170551 · Issue 656559
Rule Assembly update for pxTextInput and pxDisplayText
Resolved in Pega Version 8.7
After the application restart, multiple rule assembly alerts were seen for pxTextInput and pxDisplayText . During first access, Assembly is done and container is cached in VTable; investigation showed that in this case, the Load class without the package name had a class not found issue, and then subsequent access tried to use the container from cache and assembly was not done. To prevent this, an update has been made to perform the class lookup using the package name and class name.
INC-182986 · Issue 668829
Property Rule Form refreshes after discarding changes
Resolved in Pega Version 8.7
After updating from Pega 8.2 to Pega 8.6 and migrating the properties, modifying any property rule and then discarding the change did not refresh the Property Rule Form. Investigation showed that the LOG-SYSTEM-PROPERTYOPTIMIZATION instance created during property optimization was not getting deleted when a property was deleted. As this was not getting deleted, the property was shown as optimized when adding the property back, causing confusion. This has been resolved by cleaning up the LOG-SYSTEM-PROPERTYOPTIMIZATION instance when the property is deleted and there is an optimization entry.
INC-130176 · Issue 585373
Removing Page List removes all cached pages
Resolved in Pega Version 8.6
A previous change was made such that when removing a Page List property, its size is removed from the size-specific cache as well. A further enhancement has been made so that when a Page List is removed, the system will clear the pageCache of all cached pages in the Page List.