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.
SR-A6069 · Issue 215077
Expanded debug information generated by pzUpdateElementModel
Resolved in Pega Version 7.2
The error message generated by pzUpdateElementModel has been updated to log more complete debugging information on the exception in the oLog.
SR-A6227 · Issue 217784
Fixed logic for property as dynamic label
Resolved in Pega Version 7.2
Property reference is visible instead of property value. User is When using a property as label to show dynamic labels, the property reference was visible instead of the expected property value. This was traced to a logic flaw during the markup generation for the 'GenerateCellContent' RUF, and has been corrected.
SR-A3064 · Issue 218100
Form submit disabled while Action List is processing
Resolved in Pega Version 7.2
When an Action List was being processed in response to a user action, there was no way, using out-of-the-box tools, to prevent the user from clicking on the Submit button while the process is running. This additional click or enter could cause a change in the transaction ID, which then caused incorrect data to be used in the assignment. In order to ensure the proper calculations are run, logic has been added such that once the action list processing has been fired, the buttons in the section are disabled until everything on the action list has completed.
SR-A8231 · Issue 218303
Form submit disabled while Action List is processing
Resolved in Pega Version 7.2
When an Action List was being processed in response to a user action, there was no way, using out-of-the-box tools, to prevent the user from clicking on the Submit button while the process is running. This additional click or enter could cause a change in the transaction ID, which then caused incorrect data to be used in the assignment. In order to ensure the proper calculations are run, logic has been added such that once the action list processing has been fired, the buttons in the section are disabled until everything on the action list has completed.
SR-A3064 · Issue 215647
Form submit disabled while Action List is processing
Resolved in Pega Version 7.2
When an Action List was being processed in response to a user action, there was no way, using out-of-the-box tools, to prevent the user from clicking on the Submit button while the process is running. This additional click or enter could cause a change in the transaction ID, which then caused incorrect data to be used in the assignment. In order to ensure the proper calculations are run, logic has been added such that once the action list processing has been fired, the buttons in the section are disabled until everything on the action list has completed.