SR-A540 · Issue 205835
Guardrail justifications logging corrected
Resolved in Pega Version 7.1.9
The 'Reference properties' Guardrail warning for Rule-Obj-Property was not being saved in the pr_index_warnings table as expected. The issue was caused by the warning not being created while saving the rule, and has been resolved by adding a step to set reference warning in checkForWarnings activity.
SR-A1199 · Issue 206250
Updated Email Listener mProtocol
Resolved in Pega Version 7.1.9
It was noticed that testing mail connectivity was working, but the Email listener was failing to start. This was happened when the "getStore" function on a Mail Session in the connection test passed a protocol argument that included [pop3, pop3s, imap, imaps]. EmailListener did not update the "mProtocol" variable to have the "s" for SSL, so it was only ever one of [pop3, imap]. To resolve this, the protocol name in Email Listener has been abstracted so that the 's' appears when telling java mail the protocol name.
SR-A1482 · Issue 204980
Enhancement added to support custom headers through REST
Resolved in Pega Version 7.1.9
The getObject(?pxHTTPServletRequest?) function was returning null when the authentication activity was run through the REST service. The retrieval of custom headers in the custom authentication activity was not previously supported as the object which stores the request map was null, but an enhancement has been added to make the servlet object available to HTTP/REST Service in the custom auth activity.
SR-A1484 · Issue 205662
Enhancements added to assist in migrating truststore information to new clusters
Resolved in Pega Version 7.1.9
An installation working on development both in the system and with set of trust for Connectors defined inside Pega that were specific to the development server and SOAP endpoint desired to have all of the trust configurations migrated along with the code base when setting up additional environments. Problems occurred during certificate validation that prevented the desired use, but no useful error information was generated. In order to support this function, enhancements have been added to produce an informative exception error in the checkServerTrusted method of CompositeX509TrustManagerwhen a certificate is not trusted, and to ensure that the signer certificates and then each of its intermediate certificates in the certification path are imported to Pega?s IBM WebSphere JVM?s truststore and all WebSphere JVMs participating in SSL communication on the PRPC cluster.
SR-A1538 · Issue 207014
prvisiointerface.cab unblocked
Resolved in Pega Version 7.1.9
Effective with earlier ML versions of Pega7, several OCX functions were intentionally deprecated and replaced with Silverlight functions: Prbatchscanning prDeveloper prpackagecominterface prvisiointerface. However, it was found that there are two Word features around the embed merge function requiring prvisiointerface.cab that will produce some visual problems on the screen referring to the missing cab break if the files are ported from an earlier version of PRPC and prvisiointerface.cab is unavailable. Therefore, prvisiointerface.cab has been unblocked and restored for use.
SR-A1574 · Issue 205921
Reverted WSDL naming convention to previous style
Resolved in Pega Version 7.1.9
In earlier versions of the system, the exposed Pega-generated WSDL had ComplexType named "CreateCaseWSRequestType" with uppercase "T". A recent change to naming the ComplexType "CreateCaseWSRequesttype" with lowercase "t" required a manual override to use previously generated WSDLs after upgrading, so the naming has been reverted to using the uppercase "T" format.
SR-A2424 · Issue 205812
Latency resolved for sites with repeated SAML authentication requests
Resolved in Pega Version 7.1.9
In an installation using SAML SSO for authentication, repeatedly initiating SAML IDP requests were eventually causing poor system performance. To resolve this, support has been added to disable replay cache handling during SSO login via a DSS.
SR-A246 · Issue 205577
Email Listener handling added for duplicate-name image files
Resolved in Pega Version 7.1.9
When an email contained several images with the same name, the Email Listener was processing only one of the attached images and ignoring the others. This was a missed case - the system calls addRequestAttachmentUnique to handle duplicate filenames of other types, but image types were not covered. This has been added.
SR-A2481 · Issue 208239
Added escaping for JSON special characters in REST
Resolved in Pega Version 7.1.9
When a REST Service was called and returned a property value which contained a character having special meaning for JSON (like ", \, /, backspace, formfeed, newline, carriage return, horizontal tab, or hexadecimal digits), the JSON string could not be parsed. In order to resolve this, escaping has been added to the outbound JSON text to arrive at a valid JSON. Since this adds to performance overhead as each and every character must be checked, a DSS has been added to escape the JSON conditionally.
SR-A250 · Issue 204903
Added special character decoding for outgoing email attachments
Resolved in Pega Version 7.1.9
Previously, code was added to the system to fix the cross-OS issue of special characters in file attachment names like [,],(,),{,},\,. As part of the fix, the file names are encoded before being saved to the database. However, when those attachment are retrieved and sent out again as email attachments, the encoded characters were visible instead of the decoded values. To complete the decoding process, the file name will be handled with StringUtils.decodeCrossOSString(strfilename).