SR-127932 · Issue 194420
Paragraph rules library modified for JSP tags
Resolved in Pega Version 7.1.8
A paragraph Rule created with some 'when' conditions and property references showed random contents updates after saving and check-in using the source button. This was traced to the use of a newer library for Paragraph rules that was not able to handle Pega JSP tags like "pega:when" or "pega:foreach", causing ckeditor to remove the content. This has been addressed.
SR-128008 · Issue 188288
Removed unnecessary server-side call to Mobile
Resolved in Pega Version 7.1.8
A performance issue in the developer environment related to saving and updating rules or doing rule creation or check-in has been corrected by removing the unneeded call to pzIsMobileDevice activity on load of Live UI.
SR-128024 · Issue 194819
Ensured compliance for localization checkbox on RadioButtons control label
Resolved in Pega Version 7.1.8
In RadioButtons control, it was seen that a label was localized without regard to the status of the localization checkbox checked at the section level. This has been fixed.
SR-128081 · Issue 193016
Session Timer / Log Off corrected
Resolved in Pega Version 7.1.8
After upgrade, the Session Timer control was not working correctly when created as a script in the section and then embedded in a portal harness. In ML7, the usage of window.showModalDialog was altered because Google Chrome and Firefox no longer support it. This included modifying the desktop app TimeoutLogoffDialog to use a modal dialog, but a syntax error was introduced in oSafeURL; correcting this resolved the display issue with the timeout dialog. In addition, the LogOffTimer has been modified to use the updated windows.close() function and pxSessionTimer has been marked as available.
SR-128095 · Issue 196390
Resolved modal window resize issue
Resolved in Pega Version 7.1.8
When using a grid which launched a modal dialog, selecting a value from a drop down or entering values in a text fields caused the modal dialog height to be increased with each interaction. This was due to an Improper height calculation in the JavaScript, and has been corrected.
SR-128220 · Issue 195539
Screen layout options now visible before saving a new harness
Resolved in Pega Version 7.1.8
When using a screenlayout in a harness, the options for defining the properties were not displayed. This was due to changes made to replace panel sets with screen layouts in this area, and was only an issue if the harness had not been saved yet. In order to facilitate development, these options will now also be present before saving.
SR-128416 · Issue 193685
Updated ImportTranslations activity to fully display all errors
Resolved in Pega Version 7.1.8
While importing the translated strings into the application wizard displays, errors on the last line were being overwritten with new errors rather than adding new rows. The pzImportTranslations activity has been updated to resolve this unexpected behavior.
SR-128495 · Issue 196402
Repeat grid pagination scroll bar improved
Resolved in Pega Version 7.1.8
A repeat grid with progressive pagination format (with a page size set) that had its container collapsed during load was showing its scrollbar when the number of rows was at the minimum number (i.e., when the page size is set to 5, the expectation is that the scrollbar shows only when there are 6 or more rows. But it was found that the scrollbar shows up even if there is only 5 rows). This has been corrected in the autoAdjustProgressiveGridHeight() API.
SR-128714 · Issue 198058
Checks added to harness unload at logoff
Resolved in Pega Version 7.1.8
pyDeleteDocumentPg and pyOnBeforeWindowClose requests that happen on harness unload were causing 500/401 errors when called after logoff request. These calls are now prevented with logoff checks in harnessOnBeforeUnload.
SR-128720 · Issue 194443
Fixed CSS styling for buttons in repeating layouts with refresh
Resolved in Pega Version 7.1.8
Buttons in repeating layout are meant to have incremental IDs to make each distinct for actions applied per row, but if an onClick > refresh this section was applied the DOM that was given after the refresh was no longer distinct and the triggering of CSS styling was affected. This was a problem in repeating layouts where the field control's ID was not incremental but was only pointing to the property name. This has been resolved with unique generation of input IDs and labels for attributes.