SR-C1026 · Issue 344634
Able to add When condition for DisplayYesNo
Resolved in Pega Version 7.4
An exception was generated when attempting to add 'when' conditions for DisplayYesNo control in Section. The pzActionConditionSource activity was fetching the pyUIElement value from the Primary Page and setting it to UIELement as intended, but when the pyUIElement value is empty, a null-pointer exception occurs. Handling has now been added to avoid this scenario.
SR-B68991 · Issue 336840
Fixed Expand when evaluation for nested RDLs
Resolved in Pega Version 7.4
When using a nested repeating dynamic layouts that included section with collapsible headers, using a property pyExpanded and a custom 'when' rule isExpanded to expand and collapse the layouts and refresh the parent section from deep within the nesting was sporadically producing unexpected results. If the pagination was set on the inner RDL, after refresh the layouts were not always in the same "expanded" state as they were before the refresh. This was traced to a unique ID not being generated for the expand-indicator inside progressive loaded RDL, and has been fixed.
SR-B70521 · Issue 340527
Accordion stays in view when changing tabs
Resolved in Pega Version 7.4
The content in the accordion group was scrolling down below/above the screen frame when other layouts were selected. This was an issue with the accordion not being in viewport when opened since the content was hidden using display:none, and has been fixed by calling scrollIntoViewIfOutOfView for active accordion. ScrollIntoViewIfOutOfView is defined in pzpega_ui_doc_domUtils.
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-B94720 · Issue 342356
Fixed disable when on button with two expressions
Resolved in Pega Version 7.4
When selecting Visibility condition (when Rule) and Disable Condition (expression) and adding two expressions, the second one failed with an "Invalid property reference" error and the Save button was disabled. Attempting to remove the 2nd expression still resulted in the Save button still being disabled due to the clipboard continuing to hold the incorrect entered value. Closing the expression outside the modal window and reopening it enabled the Save Changes button. This behavior was due to incorrect validation resulting from the lack of a 'when' check in pzValidateExpressionDialog for the secondLeftOperand, and this check has been added.
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.
INC-173760 · Issue 658069
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.
SR-B94216 · Issue 345203
Support added for buttons using simple image
Resolved in Pega Version 7.4
When using a customized Perform Harness set to use images instead of the icons class for Action buttons, performing the flow and closing the dirty Step Section generated a confirmation popup with the work area behind grayed out as expected. However, after pressing Cancel the image on the button was still greyed out even though the work area was not. This was due to the system not enabling the buttons using simple image as a source, and has been fixed by adding code to enabledisable.js to re-set the opacity for the buttons with simple image.
SR-B95191 · Issue 342664
Conditional Required fields fixed when working with accessibility
Resolved in Pega Version 7.4
When Accessibility is in place, the Conditional Required for fields was not working as expected, instead making the fields always required. To correct this, the tag will be generated conditionally after evaluation of required configuration.
SR-B95191 · Issue 341933
Conditional Required fields fixed when working with accessibility
Resolved in Pega Version 7.4
When Accessibility is in place, the Conditional Required for fields was not working as expected, instead making the fields always required. To correct this, the tag will be generated conditionally after evaluation of required configuration.