SR-B52773 · Issue 312408
Improved null/blank parameter handling when using Microsoft Internet Explorer.
Resolved in Pega Version 7.3.1
After upgrade, opening an assignment in Microsoft Internet Explorer, clicking the save button, and then hitting Function F5 (PF5) caused a null pointer exception on the screen. When OK was clicked in the exception popup it displayed a blank case content screen. This issue was caused by some null parameters on the stored parameter page, and has been resolved by updating the API to better handle null and undefined parameters.
SR-B52773 · Issue 312968
Improved null/blank parameter handling when using Microsoft Internet Explorer.
Resolved in Pega Version 7.3.1
After upgrade, opening an assignment in Microsoft Internet Explorer, clicking the save button, and then hitting Function F5 (PF5) caused a null pointer exception on the screen. When OK was clicked in the exception popup it displayed a blank case content screen. This issue was caused by some null parameters on the stored parameter page, and has been resolved by updating the API to better handle null and undefined parameters.
SR-B67688 · Issue 320076
Fixed use of FieldValue for templatization
Resolved in Pega Version 7.3.1
When templatization was turned on, a FieldValue containing property references that was set as a Label control value was not getting evaluated properly. This is due to the evaluated FieldValue is being set for pyLabelValue in the metadata of the label when the FieldValue actually needs to be evaluated at client side in templating. To resolve this, the property reference will be used directly instead of FieldValue.
SR-B68837 · Issue 318361
Bad 'when' fixed for ruleset translation
Resolved in Pega Version 7.3.1
Due to an error in a 'when' condition that caused incorrect overwriting, Spanish rulesets were being displayed for saving correspondence/paragraph rules irrespective of the language translations that had been imported. This has been fixed.
SR-B73664 · Issue 322173
Text area - Disable when fixed
Resolved in Pega Version 7.3.1
A Text Area control was not disabling with When conditions or expressions. The control was disabled correctly if set to "Always". This was due to an incorrect condition in pzpega_ui_template_textarea.js, and has been fixed.
INC-178417 · Issue 670114
Flag reset added for grid with 'Expand When'
Resolved in Pega Version 8.7
A grid using an 'Expand When' condition worked as expected when the condition was true, but once expanded the grid did not collapse if the expand condition was changed to false even if a section/harness refresh was performed. This has been resolved by adding an update which will reset the flag when the result of 'Expand When' is false.
SR-B70481 · Issue 322272
Scrollbar works when text area disabled
Resolved in Pega Version 7.3.1
After upgrade, scroll bars were disabled when a text area is disabled. This was traced to code that stopped the scrolling due to the disabled text area CSS style pointer-events being set to "none", and has been fixed by adding the needed CSS in the py-enduser71-workarea-overrides.css file.
SR-B70481 · Issue 322427
Scrollbar works when text area disabled
Resolved in Pega Version 7.3.1
After upgrade, scroll bars were disabled when a text area is disabled. This was traced to code that stopped the scrolling due to the disabled text area CSS style pointer-events being set to "none", and has been fixed by adding the needed CSS in the py-enduser71-workarea-overrides.css file.
SR-B44412 · Issue 303742
Expand When updated for RDL with Categorize By enabled
Resolved in Pega Version 7.3.1
The 'Expand When' condition was not running for all iterations when the collapsible layout was in a Repeat Dynamic Layout with the "Categorize By" option enabled. This has been fixed.
INC-165992 · Issue 657691
Table Filter save uses correct harness
Resolved in Pega Version 8.7
After creating a new view for table and then relaunching the portal or switching between tabs, the created views were not visible. Investigation showed that the views were saved under the incorrect pycaseworker harness on initial load, causing them to not be visible when returning from the switch and using the correct pyCWPortalContent harness. This has been resolved with the addition of the new parameter innerHarnessName to get the harness name when creating a personalization instance.