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-A19119 · Issue 241157

Improved error handling for XML-executed BIX extract failures

Resolved in Pega Version 7.2.2

When BIX extracts configured through an XML script encountered a target table that did not exist, the script itself did not visibly fail even though the error "Table doesn't exist in target database" was logged, and any extracts that were executed after that error did not generate any output. This has been corrected to set the correct error flags to ensure expected behavior.

SR-A76706 · Issue 252781

Modified pyLoadDataTypes data transform to match expected type

Resolved in Pega Version 7.2.2

Activities configured with "Double" as the data type were converted to "String" datatype in the activity after upgrade. This was due to the Data Transform pyLoadDataTypes rule using the pyLabel "DOUBLE" for double parameter type instead of "Double", and has been corrected.

SR-A77495 · Issue 254777

Corrected delete error with first row of Decision Table

Resolved in Pega Version 7.2.2

After clicking 'delete row' on the first row of a decision table the first row was not visible, but it was observed that when saving the first row it remained as it was and instead the second row was deleted. This was an error in highlighting and positioning, and has been fixed.

SR-A67932 · Issue 251208

Blank query field in Bulk Actions defaults to none instead of all

Resolved in Pega Version 7.2.2

Due to the MyCheckedOutRulesBulk Listview not adding a default 'when' condition in the query when the query value was blank, using Bulk Actions -> Select All would return a list of all non-resolved rules in the system rather than the expected value of 'none' for the list of checked rules for the bulk processing tool. This has been resolved.

SR-A19246 · Issue 254062

Customized ordering ability for delegated rules added

Resolved in Pega Version 7.2.2

Previously, the order that delegated rules were displayed in was always the reverse of the order they were added to the System-User-MyRules form, showing the most recently delegated items at the top regardless of the order they have on that page. An enhancement has now been added to allow customization of the order through a provided extension point using 'post load processing' of the data page D_pzFilteredDelegation.

SR-A19246 · Issue 254058

Customized ordering ability for delegated rules added

Resolved in Pega Version 7.2.2

Previously, the order that delegated rules were displayed in was always the reverse of the order they were added to the System-User-MyRules form, showing the most recently delegated items at the top regardless of the order they have on that page. An enhancement has now been added to allow customization of the order through a provided extension point using 'post load processing' of the data page D_pzFilteredDelegation.

SR-A22331 · Issue 252650

Blocked EditList rules ignored in listview

Resolved in Pega Version 7.2.2

When attempting to open the Data table list from the Designer studio through DesignerStudio > Data Mode > Data Tables > Data Tables, an exception was generated if the EditList rule was blocked. This was traced to the activity for displaying EditList rules opening the ruleform regardless of the availability of the rule, and has been resolved by adding a check that will filter blocked or withdrawn rules from being processed for the listview.

SR-A77382 · Issue 253160

Requestors correctly populated in Remote Tracer dropdown

Resolved in Pega Version 7.2.2

When running Tracer and selecting the Remote Trace, the connection dropdown loaded the first time but was empty when attempting to change the requestor. The dropdown sometimes loaded on subsequent tries. This was traced to a race condition with custom event handling, and the code has been updated to ensure all requestors load as expected.

SR-A83178 · Issue 254824

Resolved Null Pointer Error in edited complex data transform

Resolved in Pega Version 7.2.2

While editing a data transform, using a "For Each Page" step with a "When" child step and a "Set" grandchild step along with checking "Also use each page as source context" on the "For Each Page" step, the expression builder for the set "Set" did not launch when initially clicked. Clicking to another tab in the Designer Studio and then back to the data transform allowed the expression builder to launch, but once launched it did not have the source value populated. Submitting, closing, or canceling the modal (regardless of whether or not changes were made) resulted in a popup indicating a Null Pointer Error. This was caused by a java script Null Pointer Error in the OpenRuleAdvanced_OverLabel control which led to the sourceElement value being reported as null in the mentioned scenario. This has been fixed.

SR-A94166 · Issue 262015

Fixed misaligned headers in decision table

Resolved in Pega Version 7.2.2

A misalignment of column headers was seen in a decision table when the number of columns added exceeded 18-20. This has been corrected by adding pixel adjustment of the scroll width to the decision table header when a range is selected for a column in pzRuleDeclareDecisionTableStandard js.

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