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.

SR-A4171 · Issue 213701

Added keyword support for <current>

Resolved in Pega Version 7.2

Variations between system versions were causing a decision table containing some regexp functions to pass or fail validation depending on the version. To remedy this, support has been added for using the regular expression function as a keyword to ensure valid tables are properly handled.

SR-A5565 · Issue 217722

Added missing filename encoding for drag and drop

Resolved in Pega Version 7.2

An error was being generated when opening an attached file with "$" in the filename. This was due to missing encoding for cases attached with drag and drop, and has been corrected.

SR-130442 · Issue 212468

Added support for localization of the 'Advanced' value of the When rule

Resolved in Pega Version 7.2

If the "Advanced" value was localized in the When rule form, it failed as it was trying to compare with localized text. To resolve this, WhenTabListener has been modified to use the ID attribute instead of text for comparison.

SR-A6520 · Issue 216004

Case Worker Portal harness error resolved

Resolved in Pega Version 7.2

When using the Case Worker Portal with the UI-Kit:03-01-01 ruleset, the first search for work returned the expected results, but opening a work object and then searching again caused the same (now incorrect) results to be returned. This was traced to a harness call and storage issue, and has been resolved.

SR-A7369 · Issue 217460

Clarified evaluation order for conditional Local Actions in GetNextWork

Resolved in Pega Version 7.2

If Local Actions were configured with 'when' rules on the stages tab of a case type rule, the 'when' rules were being evaluated before assignment via GetNextWork and the wrong local actions were presented. In order to ensure flow actions are evaluated in the proper order, GetNextWork will populate a flow action before moving it to the worklist.

SR-A8396 · Issue 210609

Corrected duplicate work object IDs

Resolved in Pega Version 7.2

The out-of-the-box section pyAssignmentListGadget was generating duplicate work object ids when pyAssignmentsLabel was used to display the case/Assignments label & ID in Case contents. This was caused by changes made in a previous version intending to enhance the displaying of labels, and has been modified to avoid duplicate work object IDs.

SR-A7590 · Issue 216110

Corrected parameter page used when Flowproblems restarts

Resolved in Pega Version 7.2

Restarting the problem flow was not taking the mandatory parameters defined in the flow, instead generating the error "Required parameter Parameter_name." To correct this, the flow method body has been modified to populate the parameter page from the pyFlowParameters page before checking for mandatory parameters.

SR-A1948 · Issue 210407

Enhancement added to Edit in Excel for large data instances

Resolved in Pega Version 7.2

Edit in Excel was failing with an error when editing data instances of a class having more than 245 columns mapped to its external mapping tab. In Excel 2003, The maximum number of columns is A to IV (i.e. 256 columns), so when the number of columns exceeds 256 (including "Import status", pzInskey, PxInsname), macros were designed to throw an error to be consistent with various versions of MS office. As Excel 2007 allows more than 256 columns, a new XLSX user template has been introduced to leverage that ability. A new node "pyGenericXLSXTemplateName" has been added to "ImportManager_Settings" for this purpose.

SR-A4549 · Issue 213015

Fixed browser display issues for AttachContent

Resolved in Pega Version 7.2

Google Chrome and Microsoft Internet Explorer were improperly displaying pages using the out-of-the-box pxAttachContent control. In Microsoft Internet Explorer, the select files button text is off of the side of the button and there was no button animation when pressing the button. In Google Chrome, the "Select Files" button text was off of the button, there was no 'hover hand' indicating the button was clickable, and attaching a file caused the window to stretch. The code has been modified to update the style wrappers, and these display problems are now resolved.

SR-A4549 · Issue 215159

Fixed browser display issues for AttachContent

Resolved in Pega Version 7.2

Google Chrome and Microsoft Internet Explorer were improperly displaying pages using the out-of-the-box pxAttachContent control. In Microsoft Internet Explorer, the select files button text is off of the side of the button and there was no button animation when pressing the button. In Google Chrome, the "Select Files" button text was off of the button, there was no 'hover hand' indicating the button was clickable, and attaching a file caused the window to stretch. The code has been modified to update the style wrappers, and these display problems are now resolved.

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