SR-123367 · Issue 183309
Corrected RTE preview error
Resolved in Pega Version 7.1.8
If a rule or property included in a correspondence rule was edited and then "Show preview of included section" was clicked, the rule did not refresh to show the section preview and the Actions menu became non-responsive. This was due to a NPE in the the RTE CKEditor. There was a workaround of clicking on the Rich Text Editor after checking the preview box to trigger a refresh, but the API has been modified to add a null check for the existence of the "get" function which was added to handle various RTE scenarios.
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-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.
SR-123608 · Issue 186749
Local action launch corrected for CPMFS frameworks
Resolved in Pega Version 7.1.8
An issue in CPMFS framework generated the error "Local actions are available only when you are performing the assignment" on selecting any local action from the Perform harness. ActionAreaContent adds a parameter' actionsection' using '; //--> . When the above section is included in pyCaseActionAreaTabbedScreenFlow, that param was being populated, but not in case of CaseActionArea. This was due to local actions being available only when performing the assignment. A check has been added for the presence of actionSection in processActionDefault, and checks whether it's empty or not.
SR-123615 · Issue 183551
DateTime localization enhanced
Resolved in Pega Version 7.1.8
Previously, language packs were literally translating items like datetime format without regard to the proper grammar of that language. For example, the date time format "4 days ago" came up as an "4 Tage vor" in German, which is not correct usage. A localized parameter-based API with 54 different field values has been added to the pxFormatDateTime RUF to allow field values with arguments so the proper localization text can be displayed.
SR-123615 · Issue 183745
DateTime localization enhanced
Resolved in Pega Version 7.1.8
Previously, language packs were literally translating items like datetime format without regard to the proper grammar of that language. For example, the date time format "4 days ago" came up as an "4 Tage vor" in German, which is not correct usage. A localized parameter-based API with 54 different field values has been added to the pxFormatDateTime RUF to allow field values with arguments so the proper localization text can be displayed.