SR-C92901 · Issue 436503
Check added to maintain date entry error state rather than default to current date
Resolved in Pega Version 8.1.5
When both Calendar and Text Input was enabled, typing special characters or an invalid date into the Date Time control generated an error on submit while the system silently overwrote the incorrect value with the current date. On refresh/save, no further error was thrown and the current date was submitted without warning. To resolve this, a check has been added that will not reformat if the date has error attribute.
SR-C93726 · Issue 435287
Work status icons work correctly when using localization
Resolved in Pega Version 8.1.5
The pyWorkAssignmentStatus control was not displaying the status flags/icons for localized work status values due to a match failure caused by the system using the localized text for the pyAssignmentStatus to perform a string comparison against the hard-coded English values. To correct this, the control pyWorkAssignmentStatus has been modified to run the comparisons with the new string "assignmentStatus" instead of with the localized text.
SR-C93802 · Issue 436138
Rounding added to avoid exception for ADM number too small to save to Oracle
Resolved in Pega Version 8.1.5
An exception was thrown when trying to save ADMSnapshot agent predictor bin data that was too small (below 1 x 10-130) for the Oracle Number column it was written into. This blocked up-to-date reporting on adaptive models. To resolve this issue, the code has been modified to round the double type numbers to an acceptable scale before writing to the database.
SR-C94042 · Issue 432440
Resolved JSON exception with refreshrow used for navigation
Resolved in Pega Version 8.1.5
After upgrade, a custom implementation of a grid that had a menu configured on right click of the row for the category/description in the uploaded case attachments was not working. This was traced to the RefreshRow(non-list) action generating quotes that made the JSON invalid for a navigation rule, and has been fixed by modifying pzProcessRefreshRowItem to remove quotes from navigation refreshrow action generation.
SR-C94047 · Issue 432969
Updated Static Progress Bar Control to resolve parse error
Resolved in Pega Version 8.1.5
When configured in a section with no parameters, the Static Progress Bar control was refreshing every second. After 5-10 seconds, a parse error appeared. This has been resolved by updating the value of bUseProcess to check for both string and boolean.
SR-C95187 · Issue 433825
IO exception logging enhanced
Resolved in Pega Version 8.1.5
In order to improve diagnosing problems such as DDS nodes not joining a cluster despite Cassandra nodes being run successfully, logging enhancements have been added that include details about IO exceptions.
SR-C95253 · Issue 435788
Custom datetime controls correctly appended to Excel export
Resolved in Pega Version 8.1.5
The timezone was not being appended to datetime when exporting to Excel if a custom control was used. This has been corrected.
SR-C95532 · Issue 435981
Improved handling for deleting dedicated index instances
Resolved in Pega Version 8.1.5
If the dedicated index instance was deleted from the ‘Custom search properties’ tab rather than from the dedicated tab of the search tab, then that instance was unexpectedly deleted from the instances of custom search properties and resulted in a blank row with the re-index button disabled and delete button enabled. This was a missed usecase related to handling the deletion of a dedicated index created from D-CP-S on a class whose immediate parent class is an abstract class or class that doesn't have a dedicated index, and has been resolved by setting the pySaveFromUI Flag when delete is invoked from the Data-CustomProperties-Search instance.
SR-C95667 · Issue 438855
Corrected UI distortion for the errors container format
Resolved in Pega Version 8.1.5
After upgrade, using pydisplay to case stages in a harness resulted in misalignment issues in the UI. Investigation showed that this issue was due to an incorrect margin value for the errors container format following recent redesign work in the UI Kit, and has been resolved by correcting the value.
SR-C95840 · Issue 434791
Independent query logic inserted for non-resolved rules to avoid non-applicable columns
Resolved in Pega Version 8.1.5
Nothing was displayed under "Revalidate and save" for Rule-Ruleset-Name and Rule-Ruleset-Version. In Tracer there was an error message saying that "There was a problem getting a list: code: 207 SQLState: S0001 Message: Invalid column name 'pyRuleAvailable'. " Investigation showed that because the system was using the same logic for resolved and non-resolved rules, Rule-Ruleset-Name and Rule-Ruleset-Version were looking for the column pyRuleAvailable which was not applicable because non-resolved rules don't have this column. To resolve this issue, a separate query executor has been added for non-resolved rules as there are a few columns related to resolved rules that are not applicable for those that are not resolved.