INC-141579 · Issue 591852
Enhancement added for node heartbeat recovery process
Resolved in Pega Version 8.3.5
Nodes were not showing up in the admin portal even though they were up and running and could be seen in the pr_sys_statusnodes table. The exception "An exception was encountered while invoking the cluster membership listener callback" was seen. All nodes became visible again after multiple restarts. The root cause was traced back to a temporary database connectivity problem. The database itself was fine according to database monitoring reports, but a network problem, a slow database query, or another issue prevented Pega from establishing a connection for more than a minute. An enhancement has been made to resolve this: if a node becomes unhealthy due to the service registry missing due to a failed heartbeat, the heartbeat will try to recover after 60 seconds and keep trying every 30 seconds until it succeeds.
INC-142674 · Issue 594496
Enhancement added for node heartbeat recovery process
Resolved in Pega Version 8.3.5
Nodes were not showing up in the admin portal even though they were up and running and could be seen in the pr_sys_statusnodes table. The exception "An exception was encountered while invoking the cluster membership listener callback" was seen. All nodes became visible again after multiple restarts. The root cause was traced back to a temporary database connectivity problem. The database itself was fine according to database monitoring reports, but a network problem, a slow database query, or another issue prevented Pega from establishing a connection for more than a minute. An enhancement has been made to resolve this: if a node becomes unhealthy due to the service registry missing due to a failed heartbeat, the heartbeat will try to recover after 60 seconds and keep trying every 30 seconds until it succeeds.
INC-137255 · Issue 584910
Resolved Cassandra query read/write latency
Resolved in Pega Version 8.3.5
Read/write latency was seen when certain Cassandra queries were triggered by the system. This was traced to an unusual case where a flush was not done for an exceptionally long time period, and has been resolved.
INC-144399 · Issue 599715
Custom dropdown controls updated for classnames
Resolved in Pega Version 8.3.5
After upgrade, a customized format for Dropdowns was not picked up. This was due to recent changes made to Class name attributes to ensure they are populated for all controls, and was caused by the CSS selector not picking the necessary DOM element. This has been resolved.
INC-136793 · Issue 585605
Updates made to display busy indicator correctly in Google Chrome 84
Resolved in Pega Version 8.3.5
The Pega busy indicator was not displaying correctly in Google Chrome 84 due to changes in that browser. The needed updates have been made to adjust for these changes.
INC-143795 · Issue 599474
Acdatasource_driver call updated
Resolved in Pega Version 8.3.5
When Acdatasource_driver was invoked directly, an exception was generating indicating "This activity may not be called directly from input". This was related to recent refactoring work done, and has been resolved by modifying the code to call the acdatasource_driver activity through pzRunActionWrapper.
INC-138309 · Issue 591150
Added busy state reset to reenable buttons after custom frame cancel
Resolved in Pega Version 8.3.5
When using a custom iFrame in a section that called a third-party URL, clicking on cancel for the popup "Do you want to stay on this page or leave it?" caused the screen to freeze. This was traced to the cancellation of the dirty page setting a busy state which disabled all the buttons and did not have a path to recovery. This has been resolved by updating the busy state so it will reset when the user chooses to cancel the changes and reenable all the buttons.
INC-137100 · Issue 605837
Added predictive text handler for Japanese on iOS
Resolved in Pega Version 8.3.5
The autocomplete function was not working well in MobileView when using Japanese IME on iOS. This has been resolved by adding a new input handler for IOS mobile, which will be triggered when predictive text is selected in mobile.
INC-142248 · Issue 601766
Added safe check for ActivateTabs
Resolved in Pega Version 8.3.5
After configuring a data transform action for a close icon to set a requestor level data page value and a parent-level dynamic layout was configured with a refresh when condition to track this Data page property, pzMicrodynamicContainer was throwing a null pointer exception after this refresh occurred indicating the tag name passed to isRegularTarget function was invalid. This has been resolved by adding a safe check to ensure that activateTabs is called only for tab based Ajax containers.
INC-138968 · Issue 594170
ARIA landmarks added to put dynamic layout in tab order
Resolved in Pega Version 8.3.5
As part of W3 accessibility specifications, ARIA landmarks have been added to dynamic layouts to direct tabbing focus. If the role type is "landmark" or "document", tabindex=-1 will be added, and for component widgets tabindex=0 will be added unless it is a non-focusable element like Alert, log etc.