SR-A11321 · Issue 223010
Check added to allow inheritance control overrides
Resolved in Pega Version 7.2
If a property used "inheritfromproperty" as the control, the choice of "select on blur" was not being retained when the action was submitted. This was traced to settings in the inheritance overriding the action, and a check has been added to ensure the format will not persist if the control is changed or is empty.
SR-A6245 · Issue 220858
Restored visibility to activity parameters in the navigation rule
Resolved in Pega Version 7.2
When an activity with parameter name "flowName" was added in the navigation rule as an action, this parameter was not present in the navigation rule. This was an issue where changes had been made to not show the parameter with the name "flowName" in the configuration of the runactivity action of the Service Level Agreement rule, but that change was affecting the complete runActivity action. To correct this, the pzGetRuleParameters activity has been updated to get the form type from the toplevel page and set it using the fromClassType parameter, allowing it to be used along with existing conditions.
SR-A7687 · Issue 218670
Red highlighting reinstated for required fields in repeat grids
Resolved in Pega Version 7.2
Required Field Names in a repeat grid were not turning red as expected when validation failed. This was a change from previous behavior and the highlighting has been reinstated for clarity of use.
SR-A11172 · Issue 222988
RuleSet Pagination fixed in DS
Resolved in Pega Version 7.2
When first launching the ruleset stack landing page in Designer Studio, the second page of the paginated list was not accessible. If either the "next" link or the "2" link were clicked, the page did not respond (and no network activity was shown in the browser's network tab). Clicking on any other page link worked as expected, and refreshing the browser (or not expanding a ruleset item in the list) caused the second page to be accessible. The problem was due to the handling of password fields in the call to getQueryString, and has been updated to correct this.
SR-A8647 · Issue 218523
Handling added for grids sourced with data pages
Resolved in Pega Version 7.2
If a grid layout was used to show a user worklist and the source of the grid layout was a Data page populated from a Report Definition, the result had a join that resulted in a page list having embedded pages of the joined class. This was due to the Page and Classes not being defined properly, and better handling has been added.
SR-A12741 · Issue 224081
Fixed Live UI right panel display in developer tool
Resolved in Pega Version 7.2
When using F12 (Developer tool) in Microsoft Internet Explorer and changing the browser mode, the browser would refresh and load in the desired mode but the Live UI right panel was then displayed at the bottom of the screen. This has been corrected.
SR-A6582 · Issue 215893
Fixed drag and drop pagination shrink
Resolved in Pega Version 7.2
When a case was dragged and dropped to "Manual assessment", the space between pagination buttons (1 2 3?) displayed in the Dashboard would shrink. This was traced to whitespace in pzGridActivePage that was responsible for shifting the display after user action, and has been fixed.
SR-A10450 · Issue 220293
Handling added for referring to a section via property reference in dynamic repeating layout
Resolved in Pega Version 7.2
It was not possible to open a section in dynamic repeating layout if a section used a property reference as a property value. This was an issue with missing configuration handling, and has been fixed.
SR-A9324 · Issue 222377
Check added for post value check boxes and radio buttons
Resolved in Pega Version 7.2
When post value was configured on text field, adding check box and radio buttons caused the text field to disappear. A context page parameter check has been added to correct this issue.
SR-A7616 · Issue 217425
Option added to change CKEditor default fonts to pts vs pxs
Resolved in Pega Version 7.2
The RTE Font control was hard-coded to a font-size value given in pixels instead of points. This caused confusion when mail composed in CKEditor (which uses pixels) was displayed in Outlook (which uses points). To better handle these differences, an extension point has been provided to allow overriding CKEDITOR.config.fontSize_sizes in UserWorkForm.CKEditor to set font sizes from px to pt as desired.