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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-130421 · Issue 200325

Corrected double firing after copying trigger to superclass

Resolved in Pega Version 7.1.8

After copying a commit trigger from PegaSample-CustomerRequest to PegaSample and withdrawing the original, the new version fired twice on commit. This was caused by the RuntimeDeclarativeClassCore not properly handling the duplicate, and has been corrected.

SR-130429 · Issue 197603

Digitally signed legintwincapture.cab made available

Resolved in Pega Version 7.1.8

The use of legintwincapture.cab to install image capture on client workstations required "register server = yes" for PegaJpegLibrary15.dll, and the installer and components needed to be digitally signed and timestamped. The *.INF file in the installer has been modified to register PegaJpegaLibrary15.dll, and each Pega component has been signed and timestamped.

SR-131814 · Issue 200274

Cross-activity copy/paste added for steps

Resolved in Pega Version 7.1.8

An enhancement has been added to support copy/paste of activity steps across different activities.

SR-132143 · Issue 201187

Enhancement added to allow setting extract directory for BIX

Resolved in Pega Version 7.1.8

An option has been added to override the output directory of the command line BIX extraction. The command line parameter -P allows specifying the desired path by saving a copy of the Extract Rule XML and setting appropriate pyOutputDirectory path value in it.

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.

SR-108009 · Issue 154664

Execution plan reuse on SQL Server 2008 R2

Resolved in Pega Version 7.1.7

Due to the way a SQL server treats execution plans, each decimal bind value with a different scale is treated as a different type. To optimize the execution, the scale value for the execution plans will now be set the same as the table definition for obj- methods.

SR-110773 · Issue 160105

WorkPage now properly deleted after rule checkin

Resolved in Pega Version 7.1.7

There was an issue with rule check-in where it created the WorkPage with the obj-class Work-ProjectManagement-CheckIn, but it did not delete WorkPage when the check-in was complete. To address this, protective code has been added that checks the class of WorkPage for the existence of expected properties in order to properly handle the related clipboard pages.

SR-111606 · Issue 163137

Improved consistency with multiple class inheritance rules

Resolved in Pega Version 7.1.7

A gap in the handing of multiple class inheritance was causing an issue with the consistency in picking the correct rule from a cache. If the entry was placed in a class where the applies-to class of the rule could not see it, that entry was missed from invalidation later on during the save. This could be temporarily remedied by clearing the cache, but the rule handling has been updated to consistently choose the correct rule from the cache under multiple inheritance.

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