INC-188405 · Issue 673063
Handling added for SSO servlet name
Resolved in Pega Version 8.7
After update, logging into an external site was not working correctly due to the SSO URL being appended with "/app/default". This has been resolved by updating the code to handle the servlet name properly.
INC-188544 · Issue 674455
More informative error message for PreGetChildKeys
Resolved in Pega Version 8.7
Previously, any failure of the pzPreGetChildKeys activity included a generic error such as “Unable to identify default schema for the connection” and did not indicate the class/table name. In order to support more efficient troubleshooting, this has been updated to present an error that is more descriptive and includes the correct class name and table name.
INC-189259 · Issue 674820
Big Decimal used while converting List to Page
Resolved in Pega Version 8.7
Previous work done to handle precision numbers in the JSON response that were being rounded or truncated when parsed for the DataSource page has been updated to also handle the case of mapping a list to a page.
INC-189477 · Issue 674034
Service Email handling updated for MSGraph "From" address
Resolved in Pega Version 8.7
While creating cases via email listener, the "From" address was not shown when using MSGraph. This was an issue with extracting the display name when MSGraph is used, and has been resolved by adding double quotes to display the name unconditionally.
INC-189580 · Issue 672852
Cleanup added for disabled/deleted operator passivation data
Resolved in Pega Version 8.7
In some scenarios, a passivated session for a non-active operator was able to be resumed after cluster restart. This has been resolved by adding a check for disabled or deleted operators which will then delete any lingering passivated data.
INC-189811 · Issue 679935
Updated XMLDataToPage privilege
Resolved in Pega Version 8.7
Cases were not being created or moved due to a privilege issue on EndUser portal after update. This was traced to the XmlDataToPage activity now including the OpenDeveloperForm privilege, which end user operator profiles do not have. This was a missed use case, and has been resolved by updating XMLDataToPage so it requires authentication but not privilege to run.
INC-190270 · Issue 681087
MSGraph email listener enhancements
Resolved in Pega Version 8.7
Attachments with .eml /.msg extensions were treated as FileAttachments by the MS Graph API and generating a classcastexception. To resolve this, a check has been added to identify the attachment along with content type so .eml will be correctly recognized. In addition, the MSGraph email listener functionality related to converting from Graph to MIME message has been enhanced around the 'TO' and 'CC' recipients in a MIME message and for parsing nested attachments in Item attachment for addition to MsgraphMessage.
INC-190380 · Issue 678643
CreateVersion rule updated for REST Integration Wizard
Resolved in Pega Version 8.7
When using a JSON response in the Create REST Integration wizard to generate the rules, the wizard displayed a null pointer exception during the final generation. The error pop up message "Generation process has been canceled and all created records have been removed" was displayed on the screen. This was traced to the REST Integration Wizard putting data rules in the wrong ruleset version when the context of both the Integration Layer and the Data Layer were configured to use an existing ruleset and to create a new version of that ruleset, and has been resolved by modifying the pzCreateVersion rule to support this.
INC-191033 · Issue 684370
Security updated for viewing data tables
Resolved in Pega Version 8.7
In order to improve security related to viewing data table instances, the privilege pxListClassRecords has been created in @baseclass and added to the "may start" activity ListEditor. Please add the privilege pxListClassRecords to access groups using ListEditor.
INC-191673 · Issue 679945
"Keep file open" updated
Resolved in Pega Version 8.7
When "keep file open" was checked, Connect-File was failing with a java.io.IOException: Stream Closed error if called more than once. When "keep file open" is checked, the very first Connect-File call saves the handle to the OutputFileStreamWrapper of the requestor page. Any subsequent Connect-File calls will access this saved OutputFileStream but the stream is already closed, resulting in the exception. To resolve this, the try-with-resources statement that closed the OutputStream has been removed.