SR-D87605 · Issue 547296
Indexes and tables updated to improve purge query performance
Resolved in Pega Version 8.2.7
Due to work done previously, purge queries to clean up the application ruleset index and application hierarchy_flat tables were running slowly or not returning the expected results. This has been resolved.
SR-D87673 · Issue 552484
IACservice security updated
Resolved in Pega Version 8.2.7
Security updates have been made which now require authentication to consume the services from IACservice packages.
SR-D87870 · Issue 548772
Resolved putting JMS Message through JMS Listener interface
Resolved in Pega Version 8.2.7
When using MS Listener integrated into Pega running on WebSphere Liberty, the listener was running correctly and able to consume JMS Messages. The JMS Listener ruleform provided options to browse and put JMS messages. However, when attempting to put a message into the destination queue, an error occurred. Investigation showed that if the resource lookup was using 'Resource references' on JMS Listener, the naming context was initialized with a null hashtable. This has been corrected by modifying AddJMSMessage and GenericViewJMSMessage to initialize the naming context with the default constructor RefreshJMSMessages to set JNDIServerName and pass the current parameter page when calling GenericViewJMSMessage.
SR-D91894 · Issue 557220
Class Loader cache values wrapped with WeakReference for improved cleanup
Resolved in Pega Version 8.2.7
Out Of Memory exceptions due to Metaspace were observed on Web tier instances running with a max Metaspace size of 2GB. Investigation showed that in PRClassLoaderDB, mLoaderCache values were wrapped with a SoftReference. To resolve this, the Class Loader cache values will be wrapped with a WeakReference, allowing the cache to free memory when it is no longer needed. JVM options has also been added to switch types of References being used if there is a preference.
SR-D92707 · Issue 551694
QP exception handling improved
Resolved in Pega Version 8.2.7
There is currently a configurable maximum size limit for QP items of 5MB. If the message size exceeded 5 MB, the message failed to be enqueued to Kafka, but still ended up in the delayed message table where it remained. This caused issues with pzDelayedQueueProcessorSchedule JS as a result. To resolve this, the system has been updated to better detect Kafka errors related with message size and move any corrupted item to the broken message queue with the appropriate message attached.
SR-D94019 · Issue 553783
Alerting features added for Listeners
Resolved in Pega Version 8.2.7
An enhancement has been added for Email Listener alerts. At the end of each listener's processing cycle, the system will determine the average processing time per message, the total processing time of the listener, the total unread messages count, and total number of messages processed. In each AESRemote agent run, this data will be published to the PDC, where it will be analyzed and any necessary alerts raised.
INC-173068 · Issue 654066
HTML tags escaped in Audit History field values
Resolved in Pega Version 8.5.6
The case narrative section was showing case statuses with encoded special characters such as % or ( ), resulting in entries such as "Status changed to Complete &# 40;approved& #41; !@##$: %^& amp;*&# 40;&# 41;_&# 43;.</div>". This has been resolved by updating the PyMemo field from type Text Input to DisplayAsLiteral for case narrative, which matches the setting for case history.
INC-178650 · Issue 673547
Cross-site scripting protections updated
Resolved in Pega Version 8.5.6
Cross-site scripting protections have been updated around the DisplayAttachment function.
INC-180275 · Issue 666454
Collaboration control hidden if data type is delegated
Resolved in Pega Version 8.5.6
When collaborating using a customized CaseManager portal with some delegated data types, the admin user refreshing the Data Type view changed the collaborator's view from the portal to show the Data Type tabs, allowing the second person to open rules (properties, Data Pages, etc) and see the configuration even though they could not make any changes. This has been resolved by updating pzDataTypeDelegated to display the collaboration control only if pzDelegation is false.
INC-183650 · Issue 678310
Corrected doubled tag removal
Resolved in Pega Version 8.5.6
After adding two tags for a Service case, attempting to delete the first tag resulted in the second tag also being removed. When three tags were present in the case, deleting the first tag caused the first and second to be deleted. Investigation showed this was caused by the run activity pyRemoveTagLink being called twice in run time, and has been resolved by updating the run activity.