INC-233462 · Issue 739542
DSS added to control validation of hidden fields
Resolved in Pega Version 8.8
When required fields are in hidden format, a client side validation error may be thrown on submit. To address this, a DSS has been added to control whether or not hidden fields are validated. By default "validateHiddenField" will be true and the fields will be validated; changing this to false will skip the validation of hidden fields.
INC-233513 · Issue 741983
Validation warning flag appearance made more consistent
Resolved in Pega Version 8.8
The warning "Please correct flagged fields before submitting the form!" was appearing inconsistently across the flow actions. Investigation showed that from the Todo Widget > Click on Link > Click on Go button. the assignment opened in an Ajax container so validations were triggered because it called the webwb • pzpega_ui_doc_submit • js file doFormSubmit() method which leads to the alert message. However, using Todo Widget > Go button caused the assignment to open in a Dynamic Container so no validations were triggered. This has been resolved by adding a new flag to skip field validation in certain cases to produce consistent behavior.
INC-233991 · Issue 743397
Temporary page logic updated for GetSectionHtmlForDesignView
Resolved in Pega Version 8.8
Trying to open any embedded section or layout inside the "InitiatePDF" section was not working. This was a missed use case for rendering this section, and support for this has been added by modifying the temporary page logic in GetSectionHtmlForDesignView.
INC-234543 · Issue 743003
Parameter value with carriage return evaluated correctly
Resolved in Pega Version 8.8
If a text area control had multiple lines entered in it and the same text area was passed as a parameter to a Data Transform executed at the launch of a read-only harness, the value in the text area was - " #~pyworkpage.propertyname". If the text area had just a single line without any enters/multiple lines, then it worked as expected. This was traced to the handling in pzpega_ui_events and has been resolved by escaping the newline and carriage return characters. An additional issue found when using multiselect in the form was traced to the correctActionArgs function which was generating the replacedtoken "//string//" for one of the property subjectareadetails, and this has been corrected.
INC-234874 · Issue 739874
Cursor moves via arrow buttons
Resolved in Pega Version 8.8
Using the keyboard arrow buttons to navigate between numbers was not working. Nothing happened when clicking on the left arrow, and clicking on the right arrow moved the cursor to two digits. This has been resolved by updating pzpega_control_textinput.
INC-234958 · Issue 742548
Corrected menu item name display and styling for expand icon
Resolved in Pega Version 8.8
After update, a Menu Item with Sub Menu items present did not display the arrow icon to indicate the presence of Sub Menu Items. In addition, the Menu Label was shown twice on click of the parent Menu Link. These have been corrected.
INC-235161 · Issue 743708
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-236451 · Issue 745819
Backbone.js updated
Resolved in Pega Version 8.8
The backbone.js package has been updated to the most recent version.
INC-237221 · Issue 743444
Security improvement for Currency control
Resolved in Pega Version 8.8
A potential cross-site scripting issue related to readonly formatting for the Currency control has been resolved.