SR-A3384 · Issue 212375
Added negation(!) handling for 'when' functions in icon control
Resolved in Pega Version 7.2
After migration, the 'when' rule was not evaluating negation(!) correctly in the deprecated icon control. This was caused by changes in the assembly logic stream generation treating 'when' expressions differently when negation is present, and has been resolved by passing the compiled 'when' rule to the handleEvaluateWhen function.
SR-A3384 · Issue 211149
Added negation(!) handling for 'when' functions in icon control
Resolved in Pega Version 7.2
After migration, the 'when' rule was not evaluating negation(!) correctly in the deprecated icon control. This was caused by changes in the assembly logic stream generation treating 'when' expressions differently when negation is present, and has been resolved by passing the compiled 'when' rule to the handleEvaluateWhen function.
SR-A2971 · Issue 215035
API updated for Tab Group error handling with Accordion layouts
Resolved in Pega Version 7.2
When there is error field on a section which has many Accordion layouts using Tab Groups configured with deferred load with/without pre-load, attempting to submit/refresh the section was generating an error and not rendering properly. This was an issue with the markSectionTabErrors API, and has been resolved.
SR-A2971 · Issue 213000
API updated for Tab Group error handling with Accordion layouts
Resolved in Pega Version 7.2
When there is error field on a section which has many Accordion layouts using Tab Groups configured with deferred load with/without pre-load, attempting to submit/refresh the section was generating an error and not rendering properly. This was an issue with the markSectionTabErrors API, and has been resolved.
SR-A3803 · Issue 212217
Better handling for menus when using JAWS
Resolved in Pega Version 7.2
When accessibility was invoked, the Navigation menu did not indicate arrow up/down options in links with showmenu role='link' generated on them, and JAWS was not reading out that it was a link with a menu. This was an unintended side-effect of updates to avoid reading out a URL in a label/text, and corrections have been made to support accessibility so that navigational menus are read out more intuitively with JAWS.
SR-A5060 · Issue 215198
Borders displayed for empty cells in PDF
Resolved in Pega Version 7.2
Table borders were not being displayed for columns with no data in the generated PDF file. This was due to the PDF to HTML converter being used not applying table styles if the cell is empty (similar to Microsoft Internet Explorer in quirks mode). To fix this, pzGenerateFormat has been modified to generate " " if the stream is called for PDF generation and the value is empty.
SR-A2746 · Issue 209588
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-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.