SR-B73599 · Issue 324612
Filtering fixed for properties defined by @@CaseWhen()
Resolved in Pega Version 7.3.1
Filtering was not applied for properties defined by @@CaseWhen() . This was due to some function alias calls needing double quotes for literal parameters. The double quotes are removed after section XML is submitted and hence the param available to the grid (via html attribute sortField) did not have the double quotes. To correct this, a function alias call in RD bound grid will set the pyColumnName to pyFieldName since the pyColumnName does not have the double quotes that are needed by some functions.
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.
SR-B76216 · Issue 325540
Localization support added for Indonesian
Resolved in Pega Version 7.3.1
pyLanguage has been modified to add the new value in_ID in the prompt list that will provide localization support for Indonesian (Indonesia).
SR-B77544 · Issue 326629
Scroll bar issues fixed for freeze column pane
Resolved in Pega Version 7.3.1
A vertical scroll bar was displayed on the screen and the horizontal scroll was not working as expected when the freeze column pane option was selected in the repeating grid. This was traced to styles missing from the base-grids.css that were needed for fixed column configuration, and these have been added.
SR-B57565 · Issue 316702
Fixed encoded special characters in 'Field values'
Resolved in Pega Version 7.3.1
Special characters in 'Field values' were being displayed as encoded in the grid. This was due to missing handling, and has been fixed in the generateCellContent RUF.
INC-217655 · Issue 723565
Resolved validation check freeze for Dynamic Layout Group
Resolved in Pega Version 8.7.3
After creating a multi-step form where step 1 had a Dynamic Layout Group(tabbed) that used form fields configured with validations, clicking next with empty/invalid values in the form intermittently caused the screen to freeze and a javascript exception was logged. This was traced to a missed use case related to templates in the childNode, and has been resolved by adding the necessary safe checks in lgtemplate and lgcelltemplate.
INC-218855 · Issue 718834
DSS added to control section collapse on refresh
Resolved in Pega Version 8.7.3
After update from 8.5, using dynamic layouts that included certain controls (autocomplete/text/dropdown) configured with Refresh-Other Section -> Parent / Top Level Section such as a pyCaseActionArea with Event 'On Change' showed a different behavior: entering a value in the configured text/auto-complete field that leads to the refresh of the top level section will collapse all expanded sections if there is a refresh trigger within the embedded section or dynamic layout of the collapsible layouts. In order to control this behavior, a new DSS has been introduced. By default HonourExpandWhenOnRefresh (owning ruleset Pega-UIEngine) will be set to false to maintain the current behavior of collapse on refresh, while setting it to true will use the older behavior of maintaining expanded sections.
INC-223222 · Issue 723634
Corrected apiContext when using bulkActions
Resolved in Pega Version 8.7.3
Row selections in the multi-selection table were intermittently not working after opening a table with bulk actions enabled. Investigation showed that opening a table with bulkActions enabled and then navigating to a table where bulk actions are not available but multi-select is enabled led to functions like setSelectedRows and getSelectedRows still being available in apiContext. This has been resolved by correcting apiContext when bulkActions is enabled.
INC-225236 · Issue 725703
Corrected LiveDesignViewDisplay error handling
Resolved in Pega Version 8.7.3
When all rulesets were locked and a section was opened from Live UI in a portal, a "rule deleted" message appeared and it was confirmed the rule was deleted even though the rule was in locked ruleset. Investigation traced this to a pzLiveDesignViewDisplay call to pxChooseBestRuleSet which jumped to failure logic when "allow check out" was disabled, and this has been resolved by correcting the error handling in pzLiveDesignViewDisplay.