SR-C46720 · Issue 386889
Back button in mobile screen flow retains entered data
Resolved in Pega Version 8.1
When navigating to an earlier step using Back Button on ScreenFlow via Mobile App, data was lost.This was traced to a call mismatch: rather than using getElementsByName, the system was calling a function that used getElementByName. This caused an exception and resulted in the form not being properly merged with the work page, leading to data loss. To correct this, the getFormJSON method has been changed to properly use getElementsByName for this function.
SR-C46751 · Issue 389629
Cleanup added to DDS service shutdown
Resolved in Pega Version 8.1
When prpcUtils is executed it starts DSM services in client mode when a DSM node (DDS) in the cluster is running. However, DSM threads do not shut down when the utility class completes, causing the Import task to hang. To prevent this, cleanup implementation has been added to the DDS service shutdown.
SR-C46793 · Issue 385886
Logoff from all portals in a Mashup fixed
Resolved in Pega Version 8.1
The logoff command was not logging the user off from all of the mashup portals. This was due to homeurl not being stored properly in mashup use cases, and the logoff URL has been updated to correct this.
SR-C47022 · Issue 388398
XSS protection added to TopHarness query string
Resolved in Pega Version 8.1
When the topHarness query string parameter was provided with a request to Pega, its contents were written to the HTML stream without HTML-encoding the content, creating a Cross-Site Scripting vulnerability. To improve security, the “topHarness” value will be encoded using com.pega.pegarules.pub.util.StringUtils.crossScriptingFilter API in pzClientDynamicData.
SR-C47024 · Issue 386882
Support added for specifying single or multiple custom directories for DDS
Resolved in Pega Version 8.1
Previously, Pega always checked free space in a default location. This caused confusion and misleading Pega0085 alerts related to the expectation that free disk space for DDS would instead be checked in a directory specified via prconfig. The system has now been modified to check free space in one or more custom Cassandra data directories configured as comma separated strings in the following prconfig settings: dnode/cassandra_data_directory, dnode/yaml/data_file_directories. The above settings will use Disk health check. In the multiple directories setup, an alarm will be raised when the disk usage threshold is crossed on each disk. Support has also been added for backing up multiple data directories.
SR-C4747 · Issue 353585
JAWS reads table sort order
Resolved in Pega Version 8.1
To improve accessibility, the sort order of a table will be read by JAWS.
SR-C47580 · Issue 386951
Assertion Type results count updated to allow input of filter class for validation
Resolved in Pega Version 8.1
When using the assertion type result count and trying to validate a property in pxResults class, it was not possible to save the test case. This was due to the system trying to validate the class in a rule under test class and not pxResults class. To fix this, the AUT rule form has been updated to show the filter class filter class text box so that when no class is been populated the filter class can be entered to enable selecting the properties from this class inheritance.
SR-C47580 · Issue 386290
Assertion Type results count updated to allow input of filter class for validation
Resolved in Pega Version 8.1
When using the assertion type result count and trying to validate a property in pxResults class, it was not possible to save the test case. This was due to the system trying to validate the class in a rule under test class and not pxResults class. To fix this, the AUT rule form has been updated to show the filter class filter class text box so that when no class is been populated the filter class can be entered to enable selecting the properties from this class inheritance.
SR-C47633 · Issue 386353
Agent management made more resilient against DB connection errors
Resolved in Pega Version 8.1
Intermittently after a database interruption occurred, agents would end up in a state where they did not run. When viewed via SMA they appeared to be running, but the next runtime was blank and the agent did not execute. Attempts to stop/restart an affected agent yielded an error, but restarting the system put the agents back into a operable state. This was a corner case caused by a DB connectivity issue where agents were first being stopped and then attempts to instantiate AgentNotification() also failed due to the DB connectivity issue. To resolve this, AgentNotification will be instantiated during AgentQueue creation itself so it will remain available. All exceptions /errors in AgentNotification will be logged.
SR-C47733 · Issue 389568
Handling added to maintain grid size when resize is run in a hidden DOM
Resolved in Pega Version 8.1
Grid layout height was getting set as 2px after opening a work item. This was traced to Grid height being reduced when the grid is in a hidden DOM and the resize handler was fired after a new tab was opened, making the grid content not visible. To correct this, a check has been added for contentHeight to avoid setting zero height when this code is run in hidden DOM.