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-132414 · Issue 201583

Resolved duplicate result column on Decision Table

Resolved in Pega Version 7.1.8

On a decision table rule, checking "Allowed to return values" check box caused an additional Result column to be added to the table configuration if the Microsoft Internet Explorer or Google Chrome browser was used. On saving, this erroneous result column was inconsistent about being removed. This has been corrected.

SR-132547 · Issue 200946

WAR file updated for WebSphere

Resolved in Pega Version 7.1.8

The web.xml file within the prweb.war file has been updated with the resource references that are needed to run within WebSphere.

SR-128963 · Issue 197101

Agent no longer exceeds lock timeout

Resolved in Pega Version 7.1.8

If an agent was accessing a work item for a long time, it was possible to exceed the lock timeout and have an agent on a different node open a new lock and overwrite the first agent's work on the item. To resolve this, mDBOpenTime has been set to persist through passivation.

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.

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