SR-127923 · Issue 193684
Localization updated in Developer environment to correctly translate labels if dot or @ is enclosed in double quotes
Resolved in Pega Version 7.1.8
In the Developer environment, the translation/localization wizard was not generating the corresponding field values for labels with text ending with '.'. This was an issue where the function "pzGenerateLabelCellContent" that validated the label text would not process the field if it contained text with a dot (.) or an @ symbol. The system has been updated to perform the localization if those special characters are enclosed in double quotes, and this format should be followed to ensure proper handling.
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-127961 · Issue 192637
Corrected reference name for doc attached to work object by CreateMergedWordDoc
Resolved in Pega Version 7.1.8
When using the CreateMergedWordDoc flow action to create a document and attach it to the Work Object, the display showed the label used in "pyNote" as the document name. However, opening the document opens it under the category name. This was caused by a mismatch in the handling and has been corrected.
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-128102 · Issue 193767
Resolved RD filter prompt not showing
Resolved in Pega Version 7.1.8
The Report Definition filter prompt was not displayed even when 'Prompt for filter changes' was checked. This was an issue with PXSHOWREPORT not using the correct step page, and has been fixed.
SR-128171 · Issue 196940
Drill down corrected for leaf node in RD summary report
Resolved in Pega Version 7.1.8
When a summary type report definition as used to source a tree grid, double-clicking a leaf node in the tree did not open the associated detailed view from the report definition. This was traced to a missing null check for the clipboard in the drill down activity, and has been resolved.
SR-128178 · Issue 192632
DataOnly upgrade modified to handle pr_data_products tables
Resolved in Pega Version 7.1.8
Running the upgrade.bat dataOnly true to upgrade the data schema failed while trying to insert values into the pr_data_products table. Promoting upgraded rules schema to higher environments and then upgrading the data schema is a supported upgrade procedure, but the dataOnly upgrade did not take this into account. The system has been updated such that when migrating post upgrade, it will not migrate pr_data_restore and pr_data_products tables and will fail if there are uncommitted hotfixes.