SR-A2746 · Issue 209586
Brought forward Dynamic Select enhancements from earlier versions
Resolved in Pega Version 7.2
Some enhancements made to Dynamic Select for earlier versions were not present in the most recent release. Although this is a deprecated feature, these enhancements have been made available.
SR-A7574 · Issue 217301
Changed auto-refresh default for Dynamic Layout radio buttons
Resolved in Pega Version 7.2
Validation was not working as expected when using a Dynamic Layout (Stacked) in a section with two radio buttons given different properties and required validation; only the first button was evaluated on submit, and the second button was evaluated if submit was clicked again. This was due to the wrapper handling the change in parameter values, and has been resolved by changing the auto-refresh property default to disabled.
SR-A4956 · Issue 212712
Check added to ensure modal edit cancel clears value
Resolved in Pega Version 7.2
If an incorrect value was entered into a field by way of a modal edit window on a repeating grid row provisioned with server side validation, clicking 'Cancel' instead of correcting the value caused the system to retain and move forward with the invalid value. This was due to the incorrect value being written to the clipboard by an older portal modal dialogue, and a check has been added to ensure proper clipboard clearance.
SR-A4005 · Issue 212070
Check added to pass value instead of parameter name from icon control
Resolved in Pega Version 7.2
After upgrade, an issue was found with passing a property to an activity from the deprecated icon control: instead of the value of the property, the property name itself was passed to the parameter of the DoAction activity. A check has been added to the generateButton RUF to catch property references and populate the property value at run time instead of the property name as a literal value.
SR-A3683 · Issue 215536
Container workarea header styles corrected
Resolved in Pega Version 7.2
The "Use the same formatting for expanded and collapsed headers" checkbox in the Workarea header style format was not working as expected in the default pyEndUser71 skin. This was due to the class being generated as layout-outline-formatstyle that was later intended to be replaced with the appropriate value, but the replacement activity was additionally replacing the 'a_' inside the workarea_header and causing the unintended result. The system has been updated to ensure only the intended content is replaced with the value.
SR-A4125 · Issue 211004
Corrected class issue with DS section rendering
Resolved in Pega Version 7.2
In Designer Studio, a section rule referencing another section of different class using a PageGroup was not rendering properly. This has been corrected by updating the handling for the GetDesignViewXML check on whether the page being used as the context is found on the pages and classes tab.
SR-A6169 · Issue 214467
Corrected compilation error when using param.value in Repeat Layout label
Resolved in Pega Version 7.2
A compilation issue was encountered when a parameter was used in a repeat section cell due to the paramStrValue being double encoded. This has been resolved by adding a check that will skip the extraneous encoding.
SR-A1235 · Issue 211107
Corrected display of page error messages set by activity
Resolved in Pega Version 7.2
Some error messages set via activity were not being displayed due to an additional call to getTrackerChanges. This was due to the async request altering the table, and has been fixed.
SR-A7682 · Issue 218041
Corrected modal flow submitted by ActionAutoSubmit
Resolved in Pega Version 7.2
ActionAutoSubmit was not working correctly with modal windows, incorrectly submitting the flow action from which the modal was invoked. This has been fixed.
SR-A5745 · Issue 213842
Corrected page group attribution handling for duplicate names
Resolved in Pega Version 7.2
If two mandatory properties existed with the same name in different contexts, the validation error "Value cannot be blank" was appearing in the second field after the first was completed. This was caused by the 'for' attribute in the label field having the value corresponding to its input field, leading to the the input fields having the same ID attached to that 'for' attribute. To correct this, the logic has been modified to pick up the nearest label from the error element.