SR-A93522 · Issue 262361
Validation highlights correct field with duplicated sections
Resolved in Pega Version 7.2.2
For business purposes, the same section was included twice in the UI to allow the left part to be used as read-only to see the old data while the right part was editable to modify existing data. When validation triggered an error to be displayed (required attribute set to Always) the message correctly appeared under the impacted control, but the RO label was shown in RED because the same labels were used for the read-only and editable components. This has been corrected to ensure that the correct labels get highlighted after the validation.
INC-154826 · Issue 614818
Enhanced handling for screen/non-screen/screen flow movement
Resolved in Pega Version 8.4.4
When using a screen flow where the last screen had a link to launch a section, a cancel button in the section that was configured with a data transform and a 'Finish Assignment' intended to move back to the screen flow did not work as expected. If a browser refresh was performed and then the cancel button was clicked, the Finish Assignment / return was triggered as expected. Because this configuration navigated to a non-screen flow, the attachOnLoad function did not load the parameter needed for maintaining error messages. This has been resolved by updating the navigation to handle this use.
SR-A87606 · Issue 257332
VDB start waits for Cassandra node with keyspace data
Resolved in Pega Version 7.2.2
An issue was found with restarting a DNode if there were no copies of the VBD keyspace data on the available nodes in the Cassandra cluster when VBD started up. VBD uses replica factor 3 on its keyspace, meaning there will be at most 3 nodes in the cluster with full copies of the VBD data. If when restarting the cluster only Cassandra nodes that happen to not have VBD's data were brought up, starting up VBD would hang trying to read partition summary data. As a solution, If VBD is started and its Cassandra data is not yet available, the process to load partition summary data will wait until the next time there is VBD activity. Once the Cassandra node comes up with VBD's data, it will be loaded and VBD functionality will be enabled. Additionally, an intermittent deadlock was discovered when starting 2 VBD nodes in parallel. The deadlock appeared when VBD was initializing its persistence at the same time another thread checked to see if persistence was initialized (triggered by remote request from second node). The first thread owned a Hazelcast distributed lock and attempted to use a Supplier to get an instance of an object. The second thread was already calling the Supplier and was waiting for the Hazelcast distributed lock. This deadlock has been fixed.
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.
INC-142589 · Issue 595491
Corrected tooltip evaluation for multiselect
Resolved in Pega Version 8.5.2
After adding help text for a multiselect help icon with overlay on hover field, the value was not being sourced. Changing to a different type of help text or control type worked as expected. This was due to an error in case sensitivity, using pyToolTip when it should have been pyTooltip, and has been corrected.
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-128279 · Issue 591378
Layout Group tab alignment correctly shown in Microsoft Internet Explorer
Resolved in Pega Version 8.5.2
Even though the responsive breakpoint for a layout group was disabled, the tabs were getting changed to Menus in Microsoft Internet Explorer. This was traced to Tab-overflow being triggered in very small viewports when using Internet Explorer 11, and has been resolved by adding dom manipulations for all layout groups.
INC-144709 · Issue 608797
Removed unnecessary decoding from GetDropdownOptions
Resolved in Pega Version 8.4.4
When using a dropdown sourced by a data page with parameters in the section, passing multiple values as the parameters of the data page resulted in the error "pzGetDropdownOptions:Invalid JSON Stream for data page params" and the parameter values were not resolving at runtime. This was traced to unnecessary decoding in the process, and has been resolved.
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.