INC-216404 · Issue 721510
Table alignment corrected for PDF
Resolved in Pega Version 8.8
The align="center" styling was not getting applied whenever the Rich Text Editor was in readonly mode. To resolve this, the CSS style has been updated to correct table center alignment for readonly Rich Text Editor documents and paragraphs in the pzbase-gadgets-ckeditor and pzbase-div-layout CSS files respectively.
INC-216727 · Issue 730957
Inline error message consistent for currency field
Resolved in Pega Version 8.8
After update, an inline validation error triggered on a currency field inside of a text box disappeared when the page was scrolled back to the top. This was traced to the display_removeErrorImage function being called from validation_ValidateFieldOnEvent due to an “onBlur” event, and has been resolved by removing the onblur for a number of decimal type to prevent clearing the validation messages at field level on tab out.
INC-216927 · Issue 714496
Conditional handling added for perceived invalid valuelist reference in design time
Resolved in Pega Version 8.8
After adding a value list property '.pyDateTimeValue(2)' in a section configured in the view editor, the design time error "config issue" was shown. There were no errors at run time and the application's behavior was correct. Changing the subscript of the value list property to (1) ran without an error. In this scenario, the actual usecase configuration will populate .pyDateTimeValue(2), but the view editor believed there was an error in the section because there was no reference to pyDateTimeValue(1) first. This has been resolved by conditionally changing the pyValue to a template property in design time when a perceived invalid valuelist reference is provided as property in the panel.
INC-217304 · Issue 714589
Regex handling updated for non-empty inputs
Resolved in Pega Version 8.8
Expression evaluation for non-empty regex has been updated to include testing for unicode characters to align with recent updates made to CKEditor.
INC-217655 · Issue 723566
Resolved validation check freeze for Dynamic Layout Group
Resolved in Pega Version 8.8
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-217680 · Issue 717605
Tab name displayed correctly in embedded mashup portal
Resolved in Pega Version 8.8
"Work Item" was given as as the tab header instead of the Case ID## when:a case link was clicked/opened in an application embedded in an external site (IAC). This was traced to the pega.desktop.support.doGadgetAction function not calling the regular handleGadgetLoad function in this scenario, and has been resolved by explicitly directing work items opened in a multi-doc mashup portal to use handleGadgetLoad.
INC-217821 · Issue 719168
Ensured data refresh for cascading dropdown controls
Resolved in Pega Version 8.8
When using two cascading dropdowns where the options within the second dropdown depended on the selection in the first dropdown, making both selections and then going back to change the selection in the first dropdown appeared to allow changing the selection in the second dependent dropdown, but autocomplete was still holding the previously selected value in memory even though the source property changed. This caused an unexpected behavior when the selections were submitted. Investigation showed that changing the value of the first dropdown triggered an API call to the Refresh assignment action that updated the value, but changing the first dropdown did not cause a refresh call to set the value back to blank in the second dropdown. This issue was seen when the dropdown values were hard-coded but did not occur if each dropdown used a data page. This has been resolved by ensuring the dependent property in a cascade is reset when the source property changes.
INC-218265 · Issue 720611
DoClose updated to resolve lock and context issues
Resolved in Pega Version 8.8
An interaction case was closing when intent tasks were closed from CSRecents. Investigation showed this was due to the doClose activity not being triggered in the right context, and has been resolved. An additional issue with locks not being correctly released after opening the new case Create stage and clicking Cancel in the modal was traced to a missing pyWorkPage in the safeURL params that was needed by the doClose activity, and this has been resolved by adding the primary page name.
INC-218855 · Issue 718833
DSS added to control section collapse on refresh
Resolved in Pega Version 8.8
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-219004 · Issue 719691
Able to trigger a flow action multiple times
Resolved in Pega Version 8.8
Previously it was only possible to trigger a flow action once in a case. Once a search was triggered via the flow action, it could not be triggered another time in the current case context. It was possible to select the local action, but it did not execute. This has been resolved by modifying the getTargetFromContainerItemID API to get the correct target by iterating over the container and checking the passed containeritemname in it.