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-129117 · Issue 196578

Resolved agent/tenant parent/child access for disabled agents

Resolved in Pega Version 7.1.8

When a shared system had an agent which was disabled, doing a "Save As" of the agent into the tenant env (to different application / RS) by logging into the tenant and enabling the agent failed with the error "No such Access group." This happened because the agent rule (created in the tenant) was running in the context of the shared system instead of the tenant system and could not find the access group. The issue was that the runActivityAsTenant function was not working as expected in the case of a child requestor trying to use the parent requestor's authorization, and this has been fixed.

SR-130345 · Issue 199748

Added qualification to validation queue page creation

Resolved in Pega Version 7.1.8

After migration, executing custom business logic validation generated the error "There was a problem getting a list". This was due to the JS code generating an unqualified QueuePage, and has been resolved.

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-128463 · Issue 193907

Create KeyRing updated for split schema

Resolved in Pega Version 7.1.8

If a command line script is configured (viz. keyringGen.sh) to encrypt user passwords for prconfig.xml databases using Keyring utility, a prconfig.xml could have three database entries but the keyring tool only prompted for two databases and did not allow encrypting password for the user for the third database. The prconfig.xml file requires very specific location information to run: to resolve this, the variables to hold schema name in case of split schema configuration have been added.

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.

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