SR-123056 · Issue 185070
FCM IAC caching improvements
Resolved in Pega Version 7.1.8
Analysis on the web server access logs found that content such as JS, image, and CSS files are cached correctly when accessing PRPC directly but not cached at all on the client when the same case is opened via the FCM IAC Gateway. This caused network congestion for the browser. To resolve this, the system now removes the appending forward slash from the thread name in the finalizeNavURL method when the request is issued to a gateway, allowing the download of the static content based on the application instead of the thread name.
SR-123127 · Issue 185219
Improve error handling for File Listener
Resolved in Pega Version 7.1.8
The File Listener not processing all files successfully when there was more than one file to be processed. This was caused by missing logic for the clearing of 'hasOnce' at the file level for the record type. Since 'hasonce' was not cleared at file level, once a file with an incorrect configuration is processed, others files were also getting processed as errors. This has been resolved by adding code to reset the 'hasonce' on a per file basis so File Listener is able to process multiple files.
SR-123149 · Issue 184289
SOAPRequestEnvelope parameter added for custom Auth Activity
Resolved in Pega Version 7.1.8
In some cases, the SOAP request envelope content was not available to the authentication activity called by the auth service protocol. Since the operator ID is derived via a decision table from a different value in the SOAP request envelope, there was no way to use that value as an input to the new authentication activity. To correct this, SOAPRequestEnvelope is now made available on the parameter page of customAuth Activity with name "pxReqSOAPEnvelope".
SR-123149 · Issue 186790
SOAPRequestEnvelope parameter added for custom Auth Activity
Resolved in Pega Version 7.1.8
In some cases, the SOAP request envelope content was not available to the authentication activity called by the auth service protocol. Since the operator ID is derived via a decision table from a different value in the SOAP request envelope, there was no way to use that value as an input to the new authentication activity. To correct this, SOAPRequestEnvelope is now made available on the parameter page of customAuth Activity with name "pxReqSOAPEnvelope".
SR-123209 · Issue 183265
Fixed validation Issue with Map eForm rule
Resolved in Pega Version 7.1.8
A validation error occurred when the system was not able to refer to property which was in a nested page group in Map eForm rule even though the property existed. To resolve this, code has been modified in the validation activity to correctly handle data with parentheses.
SR-123209 · Issue 181230
Fixed validation Issue with Map eForm rule
Resolved in Pega Version 7.1.8
A validation error occurred when the system was not able to refer to property which was in a nested page group in Map eForm rule even though the property existed. To resolve this, code has been modified in the validation activity to correctly handle data with parentheses.
SR-123609 · Issue 184384
Added timeout for SendEmailMessage and SendEmail RUFs
Resolved in Pega Version 7.1.8
A problem was noted with case auto-creation from email occasionally stopping. This was due to the out-of-the-box sendemailmessage function not having any mechanism to stop the requestor from waiting after certain period of time, meaning if the email server was down at that point of time the PRPC requestor kept on waiting forever for the connection. To resolve this, a default timeout of 60000 ms (1 minute) has been added to the SendEmailMessage and SendEmail RUFs. The error "The Connection to be outbound email server timed out. The Server may be unavailable, or the connection configuration may be incorrect. Verify Username, Password and SSL options" will appear. This timeout value can be overridden by creating a Dynamic System Setting with name "email/timeout" in "Pega-IntSvcs" ruleset to set the desired value.
SR-123609 · Issue 190249
Added timeout for SendEmailMessage and SendEmail RUFs
Resolved in Pega Version 7.1.8
A problem was noted with case auto-creation from email occasionally stopping. This was due to the out-of-the-box sendemailmessage function not having any mechanism to stop the requestor from waiting after certain period of time, meaning if the email server was down at that point of time the PRPC requestor kept on waiting forever for the connection. To resolve this, a default timeout of 60000 ms (1 minute) has been added to the SendEmailMessage and SendEmail RUFs. The error "The Connection to be outbound email server timed out. The Server may be unavailable, or the connection configuration may be incorrect. Verify Username, Password and SSL options" will appear. This timeout value can be overridden by creating a Dynamic System Setting with name "email/timeout" in "Pega-IntSvcs" ruleset to set the desired value.
SR-123636 · Issue 184161
Trojan horse protection auto-enabled
Resolved in Pega Version 7.1.8
The authentication/trojanhorseprotection previously defaulted to NEVER, creating a security vulnerability. The trojanhorseprotection setting now defaults to external.
SR-123636 · Issue 181701
Trojan horse protection auto-enabled
Resolved in Pega Version 7.1.8
The authentication/trojanhorseprotection previously defaulted to NEVER, creating a security vulnerability. The trojanhorseprotection setting now defaults to external.