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-B69406 · Issue 325269

GetLinkedSpecsForRule will preserve existing framework rule spec links

Resolved in Pega Version 7.3.1

When a framework layer rule was opened Specs were not listed, and checking out and checking in the rule caused the link to spec which was associated in the framework layer to also be deleted. This appeared as specifications created for the FW layer not being visible from the Rule form when the current access group pointed into the Implementation layer. It should be noted that the Framework layer specs cannot be linked with framework layer rules when doing development in the implementation layer - that is an expected behavior. Therefore the fix for this issue will just retain the existing rule specification links even for framework rules: On Report definition pzGetLinkedSpecsForRule context mode was changed to All Rules in Application and Frameworks except PegaRULES. PostCheckOut activity in following classes were updated to call PostCheckOut from Rule- Rule-HTML-Section Rule-HTML-Harness Rule-File-Stencil Rule-File-

SR-B77272 · Issue 326822

TransformerFactory security functions reverted

Resolved in Pega Version 7.3.1

Export to Excel was broken in the IBM environment. This was related to compatibility with security updates which were not consistently implemented by TransformerFactory installations. To resolve this condition, those security changes have been removed from the following functions: DCOdocumentToBytes DCOnodeToString DCOgetStringFromDocument

SR-B77713 · Issue 327047

Null check added to pxSystemFlow to handle post-upgrade assignment display

Resolved in Pega Version 7.3.1

After upgrade, assignments were not being displayed. This was due to pxSystemFlow being blank in earlier versions of Pega. In the Flows section the assignments are filtered based on false check, hence assignments were not seen. To prevent this issue, a null check has been added.

SR-B77745 · Issue 327019

pyCaseBreadCrumb control localized

Resolved in Pega Version 7.3.1

When viewing a case, the pyCaseBreadCrumb control was not localizing the value, instead always displaying the value of pyLabel. This has been corrected.

SR-B64309 · Issue 315889

PDN help properly reflects FlowAnalysis implementation in the Diagram tab

Resolved in Pega Version 7.3.1

The documentation has been updated in the PDN to reflect that the ruleform "Flow Analysis" option is no longer available. The references to this were mistakenly left visible due to a build issue and the help files have now been republished so they match the current implementation of the Flow Analysis option, which is available on the Diagram tab.

INC-143025 · Issue 600610

API performance improvements

Resolved in Pega Version 8.3.5

Performance improvements have been made for running the get assignment action details API.

INC-136208 · Issue 585228

Case history filter added for manual instantiation of Child Case

Resolved in Pega Version 8.3.5

After upgrade from v7.4 to v8.3, creating any child case from a parent case unexpectedly added the audit history "Child case xxxxx has been manually instantiated" to the parent case. In order to make this customizable, an "isHistoryAvailable" function has been added in the 'when' condition of "AddCoveredWork" Activity's "History-Add" Step. This will use the FilterHistory decision tree, which now has a setting for "ChildCaseInsAudit" to control whether or not the manual Instantiation of a Child Case will appear in the case history. The default is "true"; setting it to "false" will suppress the message.

INC-134113 · Issue 591543

Child case locking error message has correct parameter

Resolved in Pega Version 8.3.5

A locking error message was appearing without the case parameter, showing "Error Message : Could not lock the cover ; has it. Please wait and try again later." This was traced to the cover already being present, causing the step to open the Cover Object to fail. To resolve this, and update has been added to pass the Cover case ID to the field value.

INC-139074 · Issue 587813

Email handling security updated

Resolved in Pega Version 8.3.5

Cross-site scripting protections have been enhanced for email activities.

INC-140266 · Issue 602075

Log-access security updated

Resolved in Pega Version 8.3.5

Access control has been updated for Log-Usage class.

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