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.

INC-125803 · Issue 568661

Cross-site scripting updated on activities

Resolved in Pega Version 8.1.9

Additional Cross-site scripting work has been done on activities.

INC-127981 · Issue 563000

Rulesets removed from direct invocation ability

Resolved in Pega Version 8.1.9

Internal rules have been updated so that they are no longer available to be invoked directly by a client or service.

INC-146837 · Issue 602673

PerformCriteria contains CurUserHasRequiredSkills 'when' rule

Resolved in Pega Version 8.1.9

A customer version of the PerformCriteria data transform was generating a validation error due to a qualified statement that resulted in a null result. This has been resolved by updating the PerformCriteria DT to include the CurUserHasRequiredSkills 'when' rule.

SR-D65866 · Issue 536427

Corrected approval step task message

Resolved in Pega Version 8.1.9

When a case progressed to the approval step, the task name did not properly appear as part of the "Please approve or reject this" message. In another scenario, a portal which supported locale switching was not translating "Please approve or reject this" when the locale was switched, but instead displayed the message in the original language. Investigation traced this to the pzInstructionsForApproval data transform storing the localized field value, causing it to persist inappropriately. This has been resolved.

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.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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