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.
SR-A5212 · Issue 215923
Corrected Spellcheck examining style tags
Resolved in Pega Version 7.2
When text was sent for spell check, the Spell Checker was also validating the contents inside style tags and adding the spell checker's suggestions to them. This has been resolved by trimming any style tags off before sending the text for spellcheck.
SR-A7105 · Issue 215067
Corrected When Display format handling for DateTimeControl
Resolved in Pega Version 7.2
If the read-only formatting value was checked in the pxDateTime control for the When Display value, selecting the same value twice from the calendar caused the formatted value to be lost. To correct this, the populateSubmitableField API in pzpega_ui_calendar_dbp js file has been updated to set the data-display-value attribute before setting the value and enabling the data-formatting attribute.
SR-A6766 · Issue 215088
Corrected XSS filter handling of properties with parentheses
Resolved in Pega Version 7.2
While localizing any text using field value to a property that contains parentheses, '(' and ')' were being encoded to ( and ) respectively. This was traced to the cross-site scripting filter being applied twice twice in in the RUF pzGenerateLabelInclude, and has been corrected.