SR-123342 · Issue 186178
Smoothed use of Row Repeat with a Repeating Grid that shares references
Resolved in Pega Version 7.1.8
Issues were found with the display of Row Repeat. It was not displayed when a section contained a repeating grid and row repeat layout that had the same pagegroup property reference, and in other cases was displayed improperly after taking the wrong class for a 'when' condition. The failure to display was due to the active page being the last page of the page group as set by Repeat Grid. The RepeatGrid layout generation was changed beginning in v6.3 onwards, and now uses a method-based engine. However, the RowRepeat layout has been deprecated and therefore still uses the previous generation method. This difference creates a conflict when the RowRepeat kicks off in the same stream generation. Furthermore, this issue arises only when the two layouts bound to same PageGroup property source, and not with a Pagelist property. To resolve this, the system now resets the activePage to that of the primary page in case of page group data source in the Repeat Grid generation so that the Row Repeat gets the proper active page for its generation. The issue with displaying when it should not has been resolved by retaining the existing business logic wherever the section rule with body visible when condition is used in a repeating layout.
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-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.
SR-123617 · Issue 183668
Corrected label issue for language pack
Resolved in Pega Version 7.1.8
When a language pack was imported, the labels on the expand and collapse pane were appended with translated values instead of being replaced. This was caused by the presence of an extra space at the end of the string "Click to expand " and "Click to collapse " in workformstandard that caused a JS mis-match, and has been corrected.
SR-123642 · Issue 187841
Resolved MultiSelectList control issues for Microsoft Internet Explorer 9+
Resolved in Pega Version 7.1.8
The MultiSelectList control was no longer working for Microsoft Internet Explorer 9+. When a user attempted to select one or multiple items in the MultiSelectList control, the values were not captured when going to the next screen and a JavaScript exception was thrown. This was due to an API change in newer versions of the Internet Explorer (Microsoft Internet Explorer) browser. Microsoft Internet Explorer is following a more strict standard about how the createElement function is used, which caused the JS error to be thrown, and the system has been updated to resolve this issue.