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.
SR-127385 · Issue 235813
Fixed user authorization filtering error in extracts
Resolved in Pega Version 7.2.1
Extraction was failing sporadically due to the filter condition not being picked up by all the extract rules when running BIX. This was due to an error in authorizing the requestor with username/password causing differences in datetime formats, and has been fixed.
SR-A17976 · Issue 239119
Updated SendEmailMessage to handle images with spaces in the filename
Resolved in Pega Version 7.2.1
When an image was inserted into a draft email and sent, the image was visible in PRPC but not at the receiving end. This was a problem with the regex available in the SendEmailMessage activity not being able to handle file names containing spaces: handling for this has now been added.
INC-172692 · Issue 650615
InsID will be derived from handle if null for upgrade
Resolved in Pega Version 8.7
Upgrade from Pega 7 to Pega 8 failed with a null pointer exception in the “Upgrade Context” target. This was traced to a rule where the pxInsID was null. To resolve this, an update has been made to derive the InsID from handle when needed.
SR-A17288 · Issue 237095
Email listener leaves empty text body untouched
Resolved in Pega Version 7.2.1
When Email Listener received a new email of Content-Type: text/plain with a subject line but an empty message body, it copied the email's subject to the email's body. This was traced to code explicitly performing this copying, which has been removed.
SR-A23862 · Issue 246708
VPD Data Page passes custom properties
Resolved in Pega Version 7.2.1
When trying to set up Oracle VPD custom properties as instructed in a PDN article, an exception was generated due to missing handling for custom class/property definitions. The new pyCustomProperties if PageList has been added to Code-Pega-DBApplicationContext .
INC-163043 · Issue 645390
PEGA SOAP Service MTOM attachment handling updated
Resolved in Pega Version 8.7
After configuring a PEGA SOAP service with the Enable MTOM checked, sending a SOAP request with attachment to the service returned an invalid request error stating "Value of content length header is greater than zero - [762], but this request has empty POST". Investigation showed that when the input request reached the getPostBytes method and inputstream tried to read it, there were no available bytes and end of file was detected. This was due to the inputstream having already been read in getMultiPartSOAPHandler() method in FileUploadHandler class. To resolve this, the system will update an 'if' condition in getPostBytes method to skip reading the request attachment when contentType is "multipart/related".
INC-193442 · Issue 679178
ServicePackage thread handling improvements
Resolved in Pega Version 8.7
Work recently done to improve the release of requestor pool threads for the ServicePackage has been further enhanced by adding an explicit status notification to the thread waiting for Data Pages to be loaded in background and added support for the use case of a missing object handler. This also resolves a 504 Gateway Time-out error intermittently seen while trying to open the URL of the Pega application.
SR-A18404 · Issue 235467
New parameter to disable logging of Tidy PDF processing warnings
Resolved in Pega Version 7.2.1
When purge/archive was enabled, the system logs were filling with Tidy warning errors during PDF conversion. To resolve this, the new parameter 'pyShowWarning' has been added to the HTMLTOPDF Activity: set it to 'false' to avoid Tidy processing warnings in logs.
SR-A21098 · Issue 246780
Updated row delete authorization failure error message
Resolved in Pega Version 7.2.1
The delete button at the top of the ListViewEditor was correctly configured to delete or not based on permissions, but the proper error message did not appear when the edit attempt failed. The function will now show the message "You are not authorized to delete row." in cases where there was no permission to delete the instance.