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.
SR-A8237 · Issue 217422
Dropdown field focus corrected
Resolved in Pega Version 7.2
If a Dropdown had on change Refresh configured, the extra select displayed beside the dropdown was causing an issue where the focus was not moving back to the field where error was present after displaying an alert. This was traced to display handling differences within the accessibility focus API, and that has been modified to focus on the dropdown select instead of the hidden input.
SR-A6472 · Issue 216449
Dynamic select config works with repeat grid inline mode
Resolved in Pega Version 7.2
Repeat grid inline mode was not working when dynamic select was configured in if the validation failed using a validate rule (or) post server side validations. The logic has been added to submit callback checks for errors on grid row in the submitted row instead of all the rows.
SR-A5746 · Issue 213321
Ensured DateTime maintains read-only state when used with editable dates
Resolved in Pega Version 7.2
In a DateTime control with a read-only format set differently from an editable date format, the read-only format was being set to an editable date format when other fields were refreshed. This was an issue with calling the API, and has been corrected.
SR-A5815 · Issue 213981
Ensured validation messages display properly with changed inheritance
Resolved in Pega Version 7.2
After upgrade, changing inheritance from Work- to Work-Cover- caused validation messages to be cleared from the screen on press of a button. This was traced to the NewAction parameter in the Work-Cover-.ActionSection HTML rule causing the system to treat the action request as new and not display the error messages, and has been corrected by adding conditions to properly display errors found on the step page/primary page.