SR-A76192 · Issue 254055
Added support for tabbing on fixed size freeze header in grid
Resolved in Pega Version 7.2.2
When a grid was configured with many columns and the Freeze Header checkbox was selected from the presentation tab, clicking the header and pressing tab caused the header to move and lose alignment with the columns below. This was an unexpected use case, and support for tabbing on a Fixed size Freeze header in a grid has been added.
SR-A102021 · Issue 268416
Cassandra keyspace configuration updated
Resolved in Pega Version 7.2.2
In order to better support external Cassandra instances and using DDS-based Cassandra when the logic is running from a non-DDS node, the datacenter name will be read from Cassandra using the Datastax driver rather than JMX. The Datastax driver will request the information across the network if needed, rather than trying to use the JMX connection to Cassandra on the localhost (which would fail since there is no JMX port open because there is no running Cassandra on the non-DDS Node). In addition, creation of the keyspaces will be performed on the startup of the first DDS instance prior to any other DSM services running. This will prevent the other services from attempting to create the data keyspace since it will already exist.
INC-199192 · Issue 689037
Check added to ensure StepPage generation for Top keyword
Resolved in Pega Version 8.7.2
A ClassCastException was thrown when top page is used, indicating "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl cannot be cast to com.pega.pegarules.pub.clipboard.ClipboardPage". This has been resolved by adding a check which will generate a myStepPage for Keyword "Top" as necessary.
SR-A89181 · Issue 257344
Connect-Wait made more robust for timeouts and multiple calls
Resolved in Pega Version 7.2.2
To check an asynchronous thread running for a long time, a connect-wait was given multiple checks for the same pool id. On first execution of this connect-wait, it was unexpectedly timing out before hitting the timeout settings in the parameter. For all of the subsequent calls to connect-wait, it was waiting for the asynchronous thread to complete, i.e. exceeding the timeout limit. Normally Connect-Wait is called once and the wait time defaults to the point where data page load finishes. In this particular use case, when connect-wait hit the timeout due to a user-specified value, the system considered it an error state and cleaned up the pool ID from the thread. The subsequent waits were failing due to the mapping for the pool ID being removed when first Connect-Wait call ended with timeout. To support this use, better handling has been added for the user-specified timeout, and the system will not clear the mapping for the pool ID if Connect-Wait ended due to timeout. In cases where another Connect-Wait request does not come, the mapping will be cleared when the thread terminates.
SR-A90493 · Issue 258125
Connect-Wait made more robust for timeouts and multiple calls
Resolved in Pega Version 7.2.2
To check an asynchronous thread running for a long time, a connect-wait was given multiple checks for the same pool id. On first execution of this connect-wait, it was unexpectedly timing out before hitting the timeout settings in the parameter. For all of the subsequent calls to connect-wait, it was waiting for the asynchronous thread to complete, i.e. exceeding the timeout limit. Normally Connect-Wait is called once and the wait time defaults to the point where data page load finishes. In this particular use case, when connect-wait hit the timeout due to a user-specified value, the system considered it an error state and cleaned up the pool ID from the thread. The subsequent waits were failing due to the mapping for the pool ID being removed when first Connect-Wait call ended with timeout. To support this use, better handling has been added for the user-specified timeout, and the system will not clear the mapping for the pool ID if Connect-Wait ended due to timeout. In cases where another Connect-Wait request does not come, the mapping will be cleared when the thread terminates.
SR-A97752 · Issue 271947
Test Suite operator ID error fixed
Resolved in Pega Version 7.2.2
After creating and executing a Test Suite, the error "Unable to open an instance using the given inputs: pxObjClass = "Data-Admin-Operator-ID", pyUserIdentifier = "System" appeared on the Dashboard landing page of the Automated Unit Test. This was due to the system not setting the operator identifier when doing the agent login, and has been corrected.
SR-A24855 · Issue 253637
Fixed Export to Excel with Microsoft Internet Explorer 11
Resolved in Pega Version 7.2.2
When using Microsoft Internet Explorer 11, Export to Excel from report definition generated the sporadic error "Unable to read file." After consulting with Microsoft, the cause was traced to the browser attempting to open the file before it was downloaded, and code has been added to check for the browser and handle the download/open appropriately.
SR-A86465 · Issue 257770
Updated partial search from the Case Manager portal to return consistent results
Resolved in Pega Version 7.2.2
After upgrade, the search functionality was not working as expected. Launching the Case manager portal to search and then open a case worked, but then searching for another case and opening it resulted in the contents of the first search being displayed again. This was traced to inconsistent results when partial search was used from case manager portal,, and has been resolved by showing all the results (top 20) every time partial search is used from case manager portal, irrespective of the ranking ES provides to the search results (i.e., even if the work id is present in the top 20 or not).
SR-A24246 · Issue 248666
Event size difference on calendar corrected
Resolved in Pega Version 7.2.2
When using the out-of-the-box calendar gadget to display some events apart from the worklist goals and deadlines, an event shown on the calendar was correct in the monthly view but had the wrong time and duration in the daily view. This was traced to the way the height of the div tag was calculated in different functions, and has been corrected.
SR-A88617 · Issue 259450
Scroll bars made consistent for RTE content
Resolved in Pega Version 7.2.2
When content is entered beyond the boundaries of the Rich Text Editor (RTE) control, scroll bars appear to view the content. When attempting to print the case while in the Review/ Confirm harness with the same field, the complete content of the case was not shown on the print screen (scroll bars were still present). When the item was printed, the RTE contents did not print at all. The scroll bars are added by the browser to handle word wrap, but they are not used for RTE elements which have 'contenteditable' set to false. To resolve this, word wrap has been added for RTE in review and print options so browsers will behave consistently for elements which have the 'contenteditable' attribute as false.