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-125313 · Issue 188224
Documentation updated regarding Update Wizard avoiding deadlocks
Resolved in Pega Version 7.1.8
Following migration, running the Update Wizard tool (Designer Studio -> System -> Upgrade -> Update Existing Applications) caused deadlock errors. This was actually an error/omission in product documentation: the connection property 'webSphereDefaultIsolationLevel' must be set in the datasource prior to running the wizard, and this has been noted.
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-125539 · Issue 188736
Property Optimization Wizard working for Page level properties
Resolved in Pega Version 7.1.8
The Property Optimization Wizard was not working on Page level properties in a PageList due to due to the 'PropertyPath' Param in the displayResults activity having "()" characters that did not exist in previous versions. To resolve this, the "()" are stripped off in the Rule-Declare-Index name.
SR-125539 · Issue 188739
Property Optimization Wizard working for Page level properties
Resolved in Pega Version 7.1.8
The Property Optimization Wizard was not working on Page level properties in a PageList due to due to the 'PropertyPath' Param in the displayResults activity having "()" characters that did not exist in previous versions. To resolve this, the "()" are stripped off in the Rule-Declare-Index name.
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.
SR-125810 · Issue 188388
invokeHttpConnector updated to support TLS
Resolved in Pega Version 7.1.8
In order to support connections to TLS-enabled endpoints with Connect-HTTP, the invokeHttpConnector Activity has been updated.
SR-125913 · Issue 192447
Fixed file attachments in Mobile
Resolved in Pega Version 7.1.8
When using the AttachContent Control functionality in mobile, attaching a file popped up a window with the message 'File attached successfully', but no Action Sets associated with file attachments were actually run. Using the same functionality on desktop did not have any issues. This problem was traced to an error in the JavaScript code for the mobile control relating to the access group, and has been corrected.