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-123776 · Issue 187714
Corrected assembler issue with XML header parsing
Resolved in Pega Version 7.1.8
An assembler issue after upgrade was causing SOAP services to have issues parsing the request header. By the time the parsing is completed, header properties in the clipboard page were missed. There was a workaround of dynamically switching to the old assembler, but this has been fixed.
SR-124027 · Issue 190234
BPEL rule types deprecated
Resolved in Pega Version 7.1.8
BPEL is a flow format that makes SOAP calls to other systems. Previously, Rule-Connect-BPEL and Rule-Service-BPEL were supported types not as callable rules, but as summaries of the rules involved with interacting with a particular BPEL flow. This usage originated before the advent of landing pages, and summarized the connector or service rules, respectively, that were in the system for a given BPEL-related service package. It has been found that the BPEL-specific standard in version 1.1 and higher does not carry enough information in its schema to do an import and requires limitations and post-import work to make the flows usable. In addition, BPEL import was supported only with Visio. In Pega 7 there is no Visio view for flows, so these flows cannot be viewed or edited. Therefore the following rule types have been deprecated as of this release: -------------------------------------------------- Form Hierarchy Service COM Service BPEL+D249 Connect BPEL Parse Transform Parse Transform Collection Parse Infer Attempting to use these rule types will present the following messages: -- Service BPEL: "The rule type Service BPEL is deprecated and should no longer be used. Please use Service SOAP instead." -- Connect BPEL: "The rule type Connect BPEL is deprecated and should no longer be used. Please use Connect SOAP instead."
SR-124028 · Issue 189200
BPEL rule types deprecated
Resolved in Pega Version 7.1.8
BPEL is a flow format that makes SOAP calls to other systems. Previously, Rule-Connect-BPEL and Rule-Service-BPEL were supported types not as callable rules, but as summaries of the rules involved with interacting with a particular BPEL flow. This usage originated before the advent of landing pages, and summarized the connector or service rules, respectively, that were in the system for a given BPEL-related service package. It has been found that the BPEL-specific standard in version 1.1 and higher does not carry enough information in its schema to do an import and requires limitations and post-import work to make the flows usable. In addition, BPEL import was supported only with Visio. In Pega 7 there is no Visio view for flows, so these flows cannot be viewed or edited. Therefore the following rule types have been deprecated as of this release: -------------------------------------------------- Form Hierarchy Service COM Service BPEL Connect BPEL Parse Transform Parse Transform Collection Parse Infer Attempting to use these rule types will present the following messages: -- Service BPEL: "The rule type Service BPEL is deprecated and should no longer be used. Please use Service SOAP instead." -- Connect BPEL: "The rule type Connect BPEL is deprecated and should no longer be used. Please use Connect SOAP instead."