SR-C91927 · Issue 431510
ValidateSurveyStream updated to ensure validation runs on a named page
Resolved in Pega Version 8.1.4
After creating new survey rules, trying to re-validate and save in survey-specific rules was failing to re-validate in standard/personal edition. This was an issue with the ValidateSurveyStream activity running on an unnamed page: in this activity, the stepPage name is set to a parameter and passed to datatransform for the processing of the rule. Since the steppage was unnamed, an exception was thrown. To resolve this, steps have been added in the ValidateSurveyStream activities for question, question group, and survey that will copy the primary page into the named page and pass it as a parameter.
SR-C91979 · Issue 431156
Null check added for Grid content in a read-only RTE
Resolved in Pega Version 8.1.4
ui_grid.js was trying to initialize a grid from the markup of mail content. Since there were some missing attributes, script errors were thrown that resulted in an endless busy indicator. This is now fixed by adding the necessary null checks in Grid code.
SR-C92060 · Issue 432777
Null check added to resolve issue with manipulating operator access group list
Resolved in Pega Version 8.1.4
When using an operator access group list where there were multiple access groups already listed, picking any one of them except the last and clicking '+' (Add item) to create new line item or clicking on the delete icon to delete the row was generating a Pega busy indicator which never resolved. This was traced to the value label.prop("tagName") being returned as undefined, and has been resolved by adding a null check.
SR-C92202 · Issue 430396
Improved error handling and logging added for null partitions encountered in VBD aggregation
Resolved in Pega Version 8.1.4
A NPE was thrown during VBD aggregation when a partition was found with no data, a condition likely created by a failed insert or failed replication. To better handle this scenario, code has been added for better error handling and more informative logging.
SR-C93079 · Issue 430562
Action queue explicitly cleared in closeAllDocuments method
Resolved in Pega Version 8.1.4
After logging in to the app studio and performing some changes in the case designer, attempting to switch to data explorer or other tabs generated an alert indicating "Remaining tabs have unsaved work". After the alert was generated and closed, a "Maximum limit of opens tabs is reached" popup was then displayed even when there were no open tabs. This was traced to a change in the event handler for "DesktopAction" which caused the system to immediately move from the alert to triggering createNewWork, which then used the same dynamic document as the original alert. To resolve this, the system will clear the action queue pega.c.actionSequencer.clearQueue() in the closeAllDocuments method.
SR-C93234 · Issue 432368
FCM support added
Resolved in Pega Version 8.1.4
Support has been added for the use of FCM for Android push notifications.
SR-C93341 · Issue 433631
Hash handling security updates
Resolved in Pega Version 8.1.4
Several updates have been made to improve hash handling security.
SR-C93344 · Issue 431349
Bcrypt password hash increased to 2^12
Resolved in Pega Version 8.1.4
Bcrypt password hashes have been increased to 2^12 iterations for new passwords.
SR-C93555 · Issue 431600
BulkMover updated to not treat Numerics as strings
Resolved in Pega Version 8.1.4
When attempting to update Pega platform 8.1.1 to 8.1.3 with Oracle on a Windows machine with German locale using the out-of-place upgrade of the rules schema, the migration failed at the migration step with the error message "ORA-01722: Ungültige Zahl". This was traced to BulkMover failing when trying to convert a string to a Numeric due to the locale using commas as the decimal separator, and has been resolved by updating BulkMover to not treat Numerics as strings.
SR-C94950 · Issue 433176
Rule lock is released after alternate approved operator rejects it
Resolved in Pega Version 8.1.4
When using the rule check-in approval process, if a rule check-in candidate was rejected by an approved operator other than the one who checked it in, the lock on the original rule was not released. This has been corrected so the lock is released after the rule is rejected in the case worker portal.