SR-C45809 · Issue 386541
Age calculation declare expression fires correctly the first time the input changes
Resolved in Pega Version 8.1
When using a Date control field with display mode as drop-down lists with a declare expression for calculating the age whenever input changes, the age was not being calculated the first time the field was changed. Subsequent changes worked as expected. If the display mode was textinput + calendar in that scenario, the declare expression fired every time. This was traced to the hidden input missing the onchange handler to trigger calculateExpressions, and has been corrected by attaching the validation function using validation_validateFromUIEvent in 2 methods: handleDPDropdowns and populateSubmitableField.
SR-C45846 · Issue 391842
Improved handling for parsing multiple formats of DateTime
Resolved in Pega Version 8.1
In order to further correct an issue with DateTime formats, the system will now use the parseAsDateTime and parseAsDate functions to properly handle the parsing of the date and date time values. The Pega format will be tried first, and if that doesn't work then the UTF formats will be used. If there is still an issue, the system will call back on the original parseAsXSDDateTime/Date which should catch all cases. An exception will no longer be thrown until after all parsing methods are tried.
SR-C46216 · Issue 390637
how Subcase checkbox behavior corrected
Resolved in Pega Version 8.1
When the Show Subcase checkbox in Audit tab was unchecked, the child case history was displayed when it should not have been. This was caused by the List view not being filtered out to remove sub case data when the checkbox was invoked; to correct it the system will call LV pyWorkAttachmentList to get attachments for the parent only in the initial load, then will call another LV pyCoverAllAttachmentList to get parent and child attachments if Show Subcase is checked.
SR-C46283 · Issue 385488
Documentation update to clarify schema names should be all lower case
Resolved in Pega Version 8.1
When installing onto a system with a PostgreSQL database, the install script failed if the schema names had capitals in them, showing "ERROR: schema "pegadata" does not exist". This was due to the mixed case schema name being altered to all lowercase, so calls to the database fail due to the mismatch. In order to clarify the input needed, the PostgreSQL topic in the documentation has been updated to say : “Enter the schema name in all lowercase letters. PostgreSQL requires that schema names are all lowercase. Enter the schema name only in lowercase letters without quotation marks, or the deployment might not be successful.”
SR-C46503 · Issue 386009
Added null value handling for Date/Time
Resolved in Pega Version 8.1
A null pointer exception when trying to Save an empty record into a Date/Time Field. To resolve this, empty string value handling has been added for the date/datetime/time property in both CSV and JSON files, and a more informative exception message has been added for situations when the date can not be parsed.
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.