Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-A8117 · Issue 227498

Assign-pzResetAssignmentSLA retains SLA on drag and drop

Resolved in Pega Version 7.2.1

The out-of-the-box Assign-pzResetAssignmentSLA activity passed "Workpage" as parameter instead of "param.WorkPage", causing assignments that were dragged and dropped in the Case Manager portal to lose their SLAs. To resolve this, the Assign-pzResetAssignmentSLA activity has been updated to pass param.WorkPage instead of WorkPage

SR-A8475 · Issue 233560

Fixed Multiselect grid drag and drop

Resolved in Pega Version 7.2.1

When using MultiSelectList Control, if a value was selected and then 'submit' was used to populate the Grid's data, dragging and dropping the Grid's row to some other workbasket did not work. This happened because the clipboard calls the remove property with a symbolic delete when doing a drag and drop. While processing this delete, if the mode of property was unknown the system was unable to look up the property definition in the dictionary, and an exception occurred. To fix this, handling has been added to lookup the definition of the property if it is unknown before removing it.

SR-A9107 · Issue 218864

Fixed required field entry validation flicker in autocomplete

Resolved in Pega Version 7.2.1

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.

SR-A9481 · Issue 244466

Cleared validation error for fields not present on submit

Resolved in Pega Version 7.2.1

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.

SR-A9651 · Issue 235540

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

Resolved in Pega Version 7.2.1

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.

SR-A9921 · Issue 222554

Updated PDF generation to minimize font conversion temp file creation

Resolved in Pega Version 7.2.1

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.

SR-A14914 · Issue 231019

Onclick works with single quotes in button label

Resolved in Pega Version 7.2.1

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.

SR-A55706 · Issue 249425

BIX user guide clarifications on child/parent extracts

Resolved in Pega Version 7.2.1

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."

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us