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.

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.

INC-146098 · Issue 633722

Keyboard shortcuts work in Decision Trees

Resolved in Pega Version 8.3.6

Keyboard short cuts in Decision Trees used to copy/paste by holding ctrl button in Decision Trees were not working. This was an unintended side effect related to changing non-auto grid to an auto-generated hierarchical table to make the Decision tree rule form multi-browser compatible, and has been resolved by adding cut/copy/paste/insert-after/insert-before functionality to the decision tree context menu.

INC-151662 · Issue 626576

Handling added for application which includes production ruleset

Resolved in Pega Version 8.3.6

When creating the Email channel or Webchat channel, the Text Analyzer and its respective class (Data-Decision-Request-MCP-WebChat-xxxxx) was being saved in the ruleset of the built-on application while there were rulesets open in the top application. This was a missed use case, and has been resolved byupdating the logic to account for the scenario where an application includes a production ruleset.

INC-164944 · Issue 636290

Logic updated to handle decision trees over 64k

Resolved in Pega Version 8.3.6

An exception was thrown when decision trees reached the 64K size limit. This has been resolved by modifying the logic in the DecisiontableMethodBody Rule-Utility-Function where the split size PropRowLimit is based on the number of columns.

INC-169112 · Issue 647080

Decision Trees refresh after updating a new row

Resolved in Pega Version 8.3.6

Updating a decision tree row did not display the updated data until after save and refresh. This was traced to the first row not meeting the condition for refresh on change because the first row was created as part of the decision tree creation, so the data was not persisted and the update was not registered as a change. This has been resolved by adding explicit handling for the first row to persist its expression string and show the data as entered.

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