SR-124952 · Issue 189565
Resolved HTMLtoPDF font load error
Resolved in Pega Version 7.1.8
When using a Fonts directory during HTMLToPDF conversion, the StaticContent folder resolved to an incorrect properties file and generated an error that appeared to indicate the fonts had not correctly loaded even when they had indeed loaded. The error was traced to the function used to open the Static Content folder with the direct file handle, and this has been updated to resolve correctly.
SR-125070 · Issue 186577
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-125148 · Issue 178077
Parse XML validation default set to "Never"
Resolved in Pega Version 7.1.8
In some cases, the parse XML rules function was not correctly mapping all of the input types. The root cause for the different failure modes seen was found to be that validation was set to "Always" by default, and the rule data did not reflect this until after a manual Save or Save-As. The default has now been set to "Never", and can be manually adjusted to "Always" or "When" as desired.
SR-125148 · Issue 178317
Parse XML validation default set to "Never"
Resolved in Pega Version 7.1.8
In some cases, the parse XML rules function was not correctly mapping all of the input types. The root cause for the different failure modes seen was found to be that validation was set to "Always" by default, and the rule data did not reflect this until after a manual Save or Save-As. The default has now been set to "Never", and can be manually adjusted to "Always" or "When" as desired.
SR-125148 · Issue 192416
Parse XML validation default set to "Never"
Resolved in Pega Version 7.1.8
In some cases, the parse XML rules function was not correctly mapping all of the input types. The root cause for the different failure modes seen was found to be that validation was set to "Always" by default, and the rule data did not reflect this until after a manual Save or Save-As. The default has now been set to "Never", and can be manually adjusted to "Always" or "When" as desired.
SR-125148 · Issue 193504
Parse XML validation default set to "Never"
Resolved in Pega Version 7.1.8
In some cases, the parse XML rules function was not correctly mapping all of the input types. The root cause for the different failure modes seen was found to be that validation was set to "Always" by default, and the rule data did not reflect this until after a manual Save or Save-As. The default has now been set to "Never", and can be manually adjusted to "Always" or "When" as desired.
SR-125447 · Issue 191881
Email functions enhanced for customized authentication
Resolved in Pega Version 7.1.8
After upgrade, the system was not sending email from an account that did not specify a UserID or password. This was caused by PRPC requiring authentication. To allow for custom installations, the SendEmailMessage and EmailListener functions will check for the password; if it is null or empty, then it will set the authentication to false and will not try to authenticate.
SR-125455 · Issue 189496
Error handling improved for importing data instances
Resolved in Pega Version 7.1.8
When importing data instances from a file, messaging showed success even when importing failed due to a database error (e.g.. column length not sufficient). In addition, the error in the log file was not detailed and no error appeared on screen. This problem was specific to Oracle DB and only with Unicode characters with a column size exceeding maximum length of 256. The error handling in this case has been improved: if there is a data base error, a message will appear on the modal dialog and all the changes in the transaction will be rolled back.
SR-125497 · Issue 188946
Handling added for undesignated authentication
Resolved in Pega Version 7.1.8
If service package was unchecked, it was not possible to call authenticated activities from the service activity and errors were generated stating "You lack access required to execute RULE-OBJ-ACTIVITY @BASECLASS". To resolve this, changes have been made in the service layer to bypass authentication for all services that do not have authentication enabled on their service packages.
SR-125561 · Issue 188136
Modified processing to handle SOAP requests with text mapping
Resolved in Pega Version 7.1.8
Headers like action or MessageID with addressing information were not being added to authentication that used a SOAP service with Enable ws-addressing on. This was traced to headers with only text mapping not working with latest axiom jar, and the code has been modified to process the text node.