INC-230368 · Issue 735187
Handling added to prevent empty interaction identifier
Resolved in Pega Version 8.8
The pxInteractionAggregator queue processor was trying to aggregate data periodically but failed with the error "Unable to open an instance using the given inputs: pxObjClass = "Data-Conversation-Summary", pyInteractionId = "". Investigation showed the interaction aggregator could not find the interaction or could not get an ID from the interaction, causing the number of broken records to grow because Obj-Open failed each time it could not find a record in the database. To address this, the pxInteractionAggregator has been updated to better handle the Obj-Open step and empty interaction IDs.
INC-211101 · Issue 709880
ClipboardPageImpl handling updated for virtual list variable mRepresentativeRow
Resolved in Pega Version 8.8
A Concurrent Modification exception was seen after update. This was traced to the ClipboardPageImpl use of a virtual list variable "mRepresentativeRow" in the "InMemoryStringTable" class's method where it was iterating the "InMemoryStringTable" while the same list("InMemoryStringTable") was being modified by another thread at the same time. This has been resolved by modifying the Java file InMemoryStringTable to create a copy of the variable mRepresentativeRow to make sure that while iterating over it, the application will iterate only on a copied variable and not the original variable to prevent the concurrent modification exception.
INC-207307 · Issue 709716
Corrected OAuth jar version for custom Keystore rule
Resolved in Pega Version 8.8
Attempting to create a custom JKS and Keystore rule so it could be pointed to the Pega cipher and use the encrypt and decrypt functionalities failed with an error indicating it was not a valid KMS keystore. This was traced to an issue with a jar version mismatch: upon checking the dependencies for the nimbus-oauth-sdk jar, even though version 6.18.1 was specified the system picked the 8.27 version through transitive dependencies, and the 8.27 version doesn't have the needed CommonContentTypes class. This has been resolved by reducing the version to 6.18.1 in conflicting build.gradle.
INC-232079 · Issue 741121
Clipboard page instance resolution simplified
Resolved in Pega Version 8.8
Previous work related to removing duplicate clipboard page creation from the pyInstanceInfoForUpdate list in order to resolve out of memory issues has been further updated to address a missed use case. While finding a matching instance with same className during instance list resolution, fault logic was leading to the same java object instance being updated N times and added N times to a linked list. This caused unnecessary complexity and has been resolved by removing the matching instance logic and instead creating items for each entry individually.
SR-D28996 · Issue 520717
External Mappings set for History Rule tab of class display
Resolved in Pega Version 8.4
After creating a class rule with external mapping columns and saving the rule, attempting to restore the previous saved snapshot from the full history of the class rule resulted in the external mapping tab being displayed with empty rows. This was traced to "External mappings" not being set when displaying the History Rule, and has been resolved by adding a call to RULE-OBJ-CLASS!OPENDEFAULTS to set the mapping properties.
SR-D31344 · Issue 503070
Stale div classes are removed on refresh of section
Resolved in Pega Version 8.4
When a section had a navigation rule and a button configured in the same section with 'Refresh - Section' in its action set, each click of the button (i.e on each refresh of the section) added an additional row of <div class="menu-panel-wrapper">. This was traced to the sub-menus div not getting removed on every refresh, and has been resolved by explicitly removing the stale div.
SR-D47401 · Issue 512618
Corrected multiplying errors on dirty flag
Resolved in Pega Version 8.4
The error message "Value cannot be blank" was appended on the screen every time the browser gave a dirty flag and OK was clicked. This was due to the context for the error message not being set correctly after toggleErrorMessage, and has been corrected. In addition, due to Context being incorrect when there was a check on the errors on the element, further work has been added to set the correct context before checking if errors exist.
SR-D57278 · Issue 519461
Padding added to keep sort icon always visible in Google Chrome
Resolved in Pega Version 8.4
When sorting a grid column on Google Chrome, the sort icon was missing if the header label was large. This was traced to the Sort icon being handled as a background image of 12px in width inside 'display:table-cell' which was forced to shrink by the resize. To resolve this, 'padding: 0 6px;' has been added to each side to keep the space intact for the sort icon to always be visible.
SR-D11655 · Issue 511426
JMS Listener modified to ensure connections are closed after encountering an exception
Resolved in Pega Version 8.4
JMS listener logs were detailing exceptConnection leaks with the message " J000100: Closing a connection for you. Please close them yourself". Investigation showed that when the JMSListener is configured for JBOSS, it goes via EngineImpl. However, connections opened during engineimpl.ivokeEngine were prevented from closing if they encountered an exception. To resolve this, the execution of the connection close command has been moved to the finally block.
INC-183947 · Issue 673733
Query split added to handle Oracle expressions limit
Resolved in Pega Version 8.7
The PXCHECKFLOWDEPENDENCIES activity was throwing the Oracle error message "ORA-01795: maximum number of expressions in a list is 1000" when a case had a very large number of sub-cases, causing a failure in trying to submit additional child cases which sent them into the broken process. This has been resolved by updating the pxCheckFlowDependencies rule to break down the query parameter into batches of 999 so they can be handled by Oracle.