SR-123434 · Issue 183436
Smoothed post-upgrade ApplicationSetup that uses previously generated LDAP configs
Resolved in Pega Version 7.1.8
An LDAP configuration created under a previous version of the software was generating an NPE after upgrading. This was traced to step2 of the ApplicationSetup activity where the system was expecting a page which was missing at that point due to the user not yet being fully identified. To avoid this, a step has been added to check if the page is available and avoid the NPE.
SR-123444 · Issue 185535
DateTime conversion corrected for Excel
Resolved in Pega Version 7.1.8
When parsing an Excel file and extracting the values, the DateTime fields were being returned as a double value. This was an issue with the date to decimal conversion in the toLocal and toGMT functions, and has been corrected.
SR-123455 · Issue 184832
Java thread names corrected for Designer Studio developer activities
Resolved in Pega Version 7.1.8
When trying to run an activity from the Designer Studio developer window, the error "Section 'pxRunRecord' execution error on page 'RunRecordWindow' of class 'Pega-RunRecord" was appearing. This was caused by an error in the Java code relating to the thread name changes after upgrade, and has been modified.
SR-123595 · Issue 184394
Resolved issue with extraneous leading "." in attached properties
Resolved in Pega Version 7.1.8
When attaching a file, there were two extra (duplicate) properties created in the Link-Attachment page: .pxCreateDateTime and .pyCategory, each with a dot in front of the name. This caused an error when attempting to modify or copy the page: "The reference .pxCreateDateTime is not valid. Reason: invalid property name: '.pxCreateDateTime'". This was found to be an issue where 'pxCreateDateTime' and 'pyCategory' were being corrupted when set using the put() API. To correct this, the code has been changed to use the PutString() API instead of Put() in the java for the pyCategory property.
SR-123595 · Issue 184318
Resolved issue with extraneous leading "." in attached properties
Resolved in Pega Version 7.1.8
When attaching a file, there were two extra (duplicate) properties created in the Link-Attachment page: .pxCreateDateTime and .pyCategory, each with a dot in front of the name. This caused an error when attempting to modify or copy the page: "The reference .pxCreateDateTime is not valid. Reason: invalid property name: '.pxCreateDateTime'". This was found to be an issue where 'pxCreateDateTime' and 'pyCategory' were being corrupted when set using the put() API. To correct this, the code has been changed to use the PutString() API instead of Put() in the java for the pyCategory property.
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-123663 · Issue 184330
Multi-cell paste supported for Excel Map Value edits
Resolved in Pega Version 7.1.8
When trying to paste multiple rows into a Map Value using the 'Edit in Excel' feature, a runtime error was generated. The root cause was a refactoring code snippet that assumed only one cell for a change / paste, and the logic failed for multi-cell paste. The property used in the original logic becomes nonexistent (Target.Value) when multiple cells are being pasted. To resolve this, a different property (an array called Target.Value2 ) has been incorporated to populate and adjust the target cells.
SR-123681 · Issue 187957
AddTime calendar function corrected for calculating expiry times
Resolved in Pega Version 7.1.8
Using the out-of-the-box @addTime function to calculate expiry time was not calculating the correct time or was reporting a missing calendar when passed a calendar instance. The root cause of this problem was due to the calendar instance not using the time zone field while acquiring Gregorian Calendar in the class CalendarUtility. java. This datetime problem has been fixed.
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.