Resolved Issues

Fixed required field entry validation flicker in autocomplete

For autocomplete (chosen as required), when the down arrow is used and an option is selected, the error "field cannot be blank" is shown for a fraction of second. This has been fixed by moving the validationtype attribute firing from the time of selecting a value from grid to after the value is selected.

Cleared validation error for fields not present on submit

Validation errors were being thrown by fields that were no longer present or no longer relevant when a a modal window was launched and then canceled without filling in the fields, and the the main form was submitted. This was due to the popover/overlay close not clearing the DOM element, and has been fixed.

Added null check for empty section rule properties in Design Time section containers

In some cases, attempting to reopen a section container resulted in corrupted files. This was a Design time issue only, and was traced to empty property values. On doing a check-in , the clipboard page is put into the DB, but only properties with values were committed. Any properties whose values are empty were not committed. During retrieval, an exception was thrown because the properties did not exist in the XML. This has been resolved by updating the loadPropertyHtmlCache API of pzpega_ud_dvmanager to add null checks for pyFormat and pyValue properties which are being accessed.

Updated PDF generation to minimize font conversion temp file creation

When HTML containing Chinese characters is converted to PDF using HTMLtoPDF, files like "+~JF690731093475584931.tmp" were created in the temp folder for each conversion and were not cleared after PDF is generated. This has been fixed by modifying the PDF utility to create only one fonts.properties file.

Onclick works with single quotes in button label

A single quote in the label of a button was breaking the onclick functionality. This was a particular issue when using the French locale, as the localized value for "End other session to Release Lock" is set to "L'autre extrémité session pour déverrouiller".  This has been fixed by removing pega:lookup tag RUF GenerateButton and adding a call to get the localized value and escape that value.

BIX user guide clarifications on child/parent extracts

The below changes have been made in the BIX user guide for 7.2.1 in order to clarify the process for creating a BIX extract:

* The description of –c in “Setting optional command-line BIX parameters” in page-30 has been updated to  "Include children classes.
Use this parameter to extract the data for each sibling class of the class (classgroup/non class group) on which the extract is defined."

* “About Extract rules  / More about Extract rules / Rule operation” in page-16 has been updated to "If the class of the extract rule is a class group then the query on the source database will get all WorkObject instances of all classes within the class group. If the class of the extract rule is not a class group the query on the source database will only get instances of the particular class."

Grid Header checkbox behavior modified for consistency

Unexpected behavior was seen when clicking on the Checkbox present in Header: all other checkboxes changed their state (which was expected), but if the the Readonly checkbox was checked it was also changing the state the first time (which was not expected). After this first state change, the read-only checkboxes were not changing state (which is correct behavior). Previously, the behavior of Select All / CheckAll checkboxes was as follows: If the SelectAll / CheckAll checkbox is checked - Individual checkboxes are checked only when they are NOT disabled If the SelectAll / CheckAll checkbox is unchecked - Individual checkboxes are unchecked irrespective of their DISABLED state The behavior has now been changed as below: If the SelectAll / CheckAll checkbox is checked - Individual checkboxes are checked only when they are NOT disabled If the SelectAll / CheckAll checkbox is unchecked - Individual checkboxes are unchecked only when they are NOT disabled

Commas removed from filter values to resolve validation errors

When using a Grid layout configured in a section rule, clicking the Filter option and entering a comma separated value in the "To" field in a decimal-type column resulted in an "Invalid numeric range" option message. No error was seen if comma separated values were entered in both the "To" and "From" fields. Because the checkRangeFilter() function in ui_grid.js uses parseFloat() API to extract the decimal content entered in the search boxes, decimals after commas are ignored and validation failed due to the fields not matching. This issue has been fixed by implicitly removing any commas entered by the user.