SR-123430 · Issue 185464
Right-click info calls corrected for tabs
Resolved in Pega Version 7.1.8
Calling an activity under "Right Click Smart Info Settings" section in Format tab in list view rule was not working properly. This was an issue with the smartinfo code when mousing out from the row, and has been fixed.
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-123440 · Issue 186550
JSP expressions supported as parameter IDs
Resolved in Pega Version 7.1.8
Support has been added to GridSectionBodyElements for using JSP expressions as a parameter ID for a layout configuration in the ID field of free form layout cell properties.
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-123478 · Issue 186770
Defined order of execution for FinishAssignment and pyDeleteDocumentPg
Resolved in Pega Version 7.1.8
In an application in which a page-level message was to be output if a certain field was left blank, sometimes the page-level message did not display when the condition was met. This problem was due to the random order in which pyDeleteDocumentPg and FinishAssignment were issued by the Browser. Both are issued simultaneously to within the same 1000th of a second (according to Fiddler), but sometimes one is issued first, sometimes the other is issued first. Whether or not the function succeeded depended on whether or not pyDeleteDocumentPg was processed first by the server. In order to ensure the proper behavior, the submit and harnessOnBeforeUnload methods defined in pega.u.d object have been modified to send the finishAssignment request after processing the pzDeleteDocumentPg request.
SR-123486 · Issue 186635
Resolved access denied autocomplete error
Resolved in Pega Version 7.1.8
An 'access is denied' error generated while accessing the autocomplete was traced to a JavaScript error in the popup window handling, and has been fixed.
SR-123492 · Issue 184136
Page properties cannot be configured in remote case types
Resolved in Pega Version 7.1.8
The implementation of the Case Type advanced tab allowing page properties to be referenced under 'publish as a remote case type' was sometimes generating a validation error. As this is a complex issue, the abilty to configure Page properties in remote case types has been removed at this time.
SR-123492 · Issue 183606
Page properties cannot be configured in remote case types
Resolved in Pega Version 7.1.8
The implementation of the Case Type advanced tab allowing page properties to be referenced under 'publish as a remote case type' was sometimes generating a validation error. As this is a complex issue, the abilty to configure Page properties in remote case types has been removed at this time.
SR-123533 · Issue 187272
Corrected calculation of WO SLA Goal,Deadline based on calendar input
Resolved in Pega Version 7.1.8
The calculation of Goal,Deadline for WO SLA was not showing the expected results based on business days in the calendar. This was caused by not passing the appropriate parameter (CalendarName) to Work-.DefineSLATimesFromNewProperties so that BusinessCalendar.addTime function could evaluate the SLA based on the calendars, and has been fixed.