SR-129291 · Issue 201471
Added ability to configure node cluster timeouts
Resolved in Pega Version 7.1.8
If a cluster has many nodes, all nodes starting at the same time ended up contending for lock and throwing an exception if they timed out. When the cluster starts, none of the nodes have yet registered their cluster address in pr_sys_statusnodes. There is code that guards against a race condition and includes locking with a timeout controlled by the waitTime (set to 2000ms) and the number of attempts (set to 30) for a total of 1 minute. However, a large number of nodes contending for this lock could exceed these limits. In order to avoid this, the timeout for the lock during check cluster consistency is now configurable using "cluster/consistency/lockattemptdelayms" and "cluster/consistency/maxlockattempts". Additional tuning on this locking is anticipated to be included in ML9.
SR-129291 · Issue 201670
Added ability to configure node cluster timeouts
Resolved in Pega Version 7.1.8
If a cluster has many nodes, all nodes starting at the same time ended up contending for lock and throwing an exception if they timed out. When the cluster starts, none of the nodes have yet registered their cluster address in pr_sys_statusnodes. There is code that guards against a race condition and includes locking with a timeout controlled by the waitTime (set to 2000ms) and the number of attempts (set to 30) for a total of 1 minute. However, a large number of nodes contending for this lock could exceed these limits. In order to avoid this, the timeout for the lock during check cluster consistency is now configurable using "cluster/consistency/lockattemptdelayms" and "cluster/consistency/maxlockattempts". Additional tuning on this locking is anticipated to be included in ML9.
SR-126787 · Issue 194580
MultiSelectList details propagated correctly
Resolved in Pega Version 7.1.8
MultiSelectList details were getting saved for the second row with the same values given for the first row. This was an error with the "MultiSelectList" control, and the code has been updated in the MultiSelectList.java file.
SR-126799 · Issue 192968
Grid action events carried over after upgrade
Resolved in Pega Version 7.1.8
After upgrade, the actions configured for a grid that had been multiple click actions became split across multiple action sets - click, enter, up key, and down key. This was an issue with already configured actions not being copied correctly from "pyEditBehavior" to "pyActionSets", and has been corrected.
SR-126852 · Issue 196797
Handling added for click parameters containing HTML to open rule with magnifying icon
Resolved in Pega Version 7.1.8
If a parameter contained HTML characters, it was not possible to open any rule using the magnifying glass icon from next to a field. This behavior was related to XSS security catching the HTML, and has been resolved by sending the requested parameter in post body.
SR-126855 · Issue 193150
Smoothed double click handling for custom buttons with reload harness
Resolved in Pega Version 7.1.8
An application with several custom controls was generating errors after upgrade if the buttons were double-clicked. This was traced to the first click calling the designated ReloadHarness activity and completing it correctly, with the second click then causing the system to try to process the same request once again with the result of a stale transaction. In order to prevent this problem, the code has been changed to check for a "submitting" attribute on the same form element to avoid multiple submissions of the form.
SR-126901 · Issue 190595
Handling added for temp install directory names with spaces
Resolved in Pega Version 7.1.8
If the install directory name contained spaces, the install failed at the point where the directory was used as a script parameter due to the parsing handling the name up to the space as one parameter and after the space as another parameter. In order to resolve this, handling has been added to allow temp directory names with spaces.
SR-126901 · Issue 190603
Handling added for temp install directory names with spaces
Resolved in Pega Version 7.1.8
If the install directory name contained spaces, the install failed at the point where the directory was used as a script parameter due to the parsing handling the name up to the space as one parameter and after the space as another parameter. In order to resolve this, handling has been added to allow temp directory names with spaces.
SR-126980 · Issue 192477
Chart control validation updated to handle aggregate functions
Resolved in Pega Version 7.1.8
When a chart control contained a Report definition with COUNTDISTINCT in the summarize field, the chart was not displayed at runtime. Manually executing the Report Definition displayed the data and the pie chart as expected. This was found to be an issue with chart control not rendering the chart at run time if the underlying RD source contained an aggregate function. To correct this, the pzIsChartReportColumnValid validate rule has been updated.
SR-126980 · Issue 190876
Chart control validation updated to handle aggregate functions
Resolved in Pega Version 7.1.8
When a chart control contained a Report definition with COUNTDISTINCT in the summarize field, the chart was not displayed at runtime. Manually executing the Report Definition displayed the data and the pie chart as expected. This was found to be an issue with chart control not rendering the chart at run time if the underlying RD source contained an aggregate function. To correct this, the pzIsChartReportColumnValid validate rule has been updated.