INC-139627 · Issue 604760
Legacy and new ID generation logging enhanced
Resolved in Pega Version 8.5.2
A DuplicateKeyException was generated when attempting to create a case. The root issue was related to the local modification of the reserved ID field in the database through a custom activity and was able to to be fixed with a local change. In order to improve diagnosing events such as this in the future, enhanced logging has been added to to the legacy and new ID generation.
INC-144601 · Issue 602422
Empty addresses removed from email
Resolved in Pega Version 8.5.2
After upgrade, an issue was seen when sending email to multiple 'To' addresses generated an exception if any 'To' address had an empty value. To resolve this, a check has been added that will remove any empty address from the recipientTo address list.
INC-135195 · Issue 598071
PD4ML library updated
Resolved in Pega Version 8.5.2
When generating a PDF from a report definition with more than 1000 records, the system would hang abruptly and stop responding. There was also a noticeable size difference in the generated file. This was an issue with the included version of PD4ML, and has been resolved by updating the version from 4.0.6 to 4.0.9fx1.
INC-154564 · Issue 617348
JAWS reads the table header and filter options separately
Resolved in Pega Version 8.5.3
When table headers for a non-optimized table with filter options received focus in Google Chrome, JAWS read the header, sort and filter options all run together. This was due to a difference in the way JAWS reads headers in Chrome from the way it reads them in IE, and has been resolved.
SR-C80948 · Issue 421765
ProfileLink control updated to resolve opening issue
Resolved in Pega Version 8.2.1
The profile was not opening when the Operator Profile link was clicked. This was traced to certain functions having been moved to javascript files that were not included by default in the ProfileLink control. To correct this, the control has been modified to include the needed javascript files and the appropriate references have been updated to match.
INC-146564 · Issue 607856
DX API returns application specific validation messages
Resolved in Pega Version 8.5.2
When trying to validate the input swagger details with application specific conditions, the create case DX API did not return the validation messages from application but instead returned a "500 Internal Server Error". Investigation showed that the error parameter was not set on validation fail, and this has been corrected.
INC-152442 · Issue 616666
Check added for Create Access to attachment
Resolved in Pega Version 8.5.3
After restricting access for the attachments category in a CS application, the attachment was added without category and could not be opened. This was due to the Create Attachment access not being automatically created for all categories when privileges were added, and has been resolved by adding a step to check Create Access for attachments of the respective category.
INC-139328 · Issue 588584
Corrected Excel table picture being included with the rich-text editor paste
Resolved in Pega Version 8.5.2
Corrected Excel table picture being included with the rich-text editor pasteAs an unintended consequence of code added to allow pasting or dragging and dropping an image for upload using the rich-text editor and the CK Editor, any copied content from Excel also added a table picture to the last cell as part of the pasted data. This has been resolved by updating the system to recognize content copied from Excel and prevent uploading of the image.
INC-155559 · Issue 617502
GoToStage property marked as non-transient
Resolved in Pega Version 8.5.3
When refreshing or reopening the flow, the pzRuleParamsHolder did not display the gotostage property in in the change to stage shape even though the property was present in the clipboard and the flow switched correctly. This was traced to pyGoToStage being marked as transient, which caused the value to not be saved to the database. To resolve this, the pyGoToStage property is now marked as non-transient.
INC-182803 · Issue 679724
SearchKeyword assed to HandleInput allow list
Resolved in Pega Version 8.7.1
After creating a section and placing a template grid with a button to refresh the section on click, clicking the button generated a SECU0001 alert. This was traced to gridMetadata_(uniqueID).pySearchKeyword not being registered when the property is part of a form data post request, and this has been resolved by adding pySearchKeyword to the allow list in HandleInput.java.