SR-A67007 · Issue 255075
Catch improved to close Message Explorer connections
Resolved in Pega Version 7.2.2
When using the Message Explorer functionality provided on the JMS Connect rule form, it only allows a number invocations equal to the size of the connection pool. Due to an issue with releasing the connections when using Resource Reference mode or IIOP protocol, the pool was being exceeded and the error "Couldn't create connection object" appeared. This has been fixed by changing the conditional catch for closing the connection with a more effective try catch.
SR-A89677 · Issue 257766
Removed erroneous warning from auto-created DataType reports
Resolved in Pega Version 7.2.2
When creating a data type and local source, a report definition is automatically generated for the data type. That report definition contains the warning "Using a custom HTML control to format a column may result in poor performance displaying query results. Consider using auto-generated HTML controls." This was confusing, creating the unintended assumption that something was wrong with the automatically generated report. To clarify this, the warning will not be displayed when the rule is created automatically.
SR-D87870 · Issue 548774
Resolved putting JMS Message through JMS Listener interface
Resolved in Pega Version 8.4.1
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-D76178 · Issue 538602
Corrected Cosmos dropdown positioning in right-to-left locales
Resolved in Pega Version 8.4.1
When using the Arabic locale with the Cosmos UI, the dropdown was located on the right side of the field instead of the left side. This has been corrected.
SR-D89012 · Issue 550801
DelegatedRules refresh icon made accessible
Resolved in Pega Version 8.4.1
When using Accessibility, the refresh icon in pzDelegatedRules was being read as "Link". This has been corrected by adding text for the refresh icon.
SR-A92126 · Issue 261816
Bulk Action transfers all selected records
Resolved in Pega Version 7.2.2
Not all of the selected cases were being transferred when using the Bulk Actions functionality to transfer. This was due to the pySelected values to not being updated in the clipboard. To resolve this, a Refresh other section has been added to Select Action in pzBulkProcessingActionSection to update the value when clicked.
SR-A88035 · Issue 257024
Localization added for 'Close All' functions for multiple tab views
Resolved in Pega Version 7.2.2
Localization has been added to the 'Close All' menu item and tooltip that appear when multiple tabs are present, using the new field value pyMessageLabel.
SR-D80589 · Issue 544842
Check added before clearing Report definition custom filter section page
Resolved in Pega Version 8.4.1
When using a Custom Section in the Report Viewer, the Page referred to at the Prefix was getting reset while running the report. Investigation showed the page was being reinitialized in pzCreateCustomFilterPage step 2, and this has been resolved by adding a 'when' rule for clearing the custom filter page.
SR-D89002 · Issue 549104
SameSite cookie setting updated for pre-authentication
Resolved in Pega Version 8.4.1
In work done in previous versions to modify the SameSite cookie handling to support Mashups in Google Chrome v80+, SameSite was set to None only in case of an authenticated Pega-RULES cookie and not for a Pre-authenticated cookie. That caused the Samesite value to not be set when using a pre-authenticated cookie, and the blank value was treated as 'Lax', causing a login challenge. To resolve this, Samesite will be set to 'None' when using pre-authenticated cookie, which will match the way it is being set in authenticated cookie.
SR-D78659 · Issue 545761
Resolved CSV validation overflow in Google Chrome
Resolved in Pega Version 8.4.1
When using Google Chrome, validation of records was getting stuck in the UI at 32000+ while importing a CSV file with many invalid records when using the import option in Data type’s local data storage. Investigation showed the Call Stack size limit was exceeded in the Google Chrome dev tools due to the ":first" selector being passed to the Jquery find() method to find the element from the first element child of the XML doc. This selector causes maximum callstack exception when the document is large, and this is a deprecated selector in later versions of Jquery. To resolve this issue, the XML function in pzpega_tools_asyncprocess has been updated to replace the ":first" selector.