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-102005 · Issue 556731

Child case ID prefix preserved

Resolved in Pega Version 8.4.2

When configuring a case as a child case in App Studio, the case ID prefix was cleared out of the field on the Settings tab for the case type. Investigation showed that when the child case was added to the parent case in App studio, pzaddcasetypetoapp was called but the parent activities did not pass the CaseID parameter of the child case type. This caused the CaseID prefix of the child to be null and displayed as blank in the Settings and Application. This has been corrected by ensuring the system will get and set the parameter value.

INC-119754 · Issue 561523

Corrected 'when' rule context for GetCaseDetails

Resolved in Pega Version 8.4.2

The Pega REST API Get Method /cases{CaseID} failed if the Child Case was set with Manual instantiation using a 'when' rule. This was traced to the 'when' rule being resolved using @baseclass instead of the class of the case type, and has been resolved by updating the pzGetCaseDetails activity to evaluate the 'when' rule on the case page.

INC-120608 · Issue 573001

Temporary case creation from Cosmos resolved

Resolved in Pega Version 8.4.2

Creating a temporary case in Cosmos Portal was not working. Investigation showed that the pySkipCreateHarness and pyCreatesTemporaryObject properties were not populating properly on the D_StartingFlows data page, which was traced to the way openSelectedColumns API handles non-exposed columns. To resolve this, the system has been updated to use the openEngine API for opening starting flows if the pySkipNewHarness or pyCreatesTemporaryObject property values are null.

INC-121435 · Issue 563877

Handling added for null requiredskillcount on assignment

Resolved in Pega Version 8.4.2

If the property pxRequiredSkillCount was blank on an assignment when moved to a workbasket, it was never presented for Get Next Work. To resolve this, handling has been added which will change the null to 0 so the assignment is properly queued.

INC-127077 · Issue 564109

Busy indicator appears when uploading via Select

Resolved in Pega Version 8.4.2

After upgrade, the “loading symbol” (busy indicator) was not appearing while uploading large attachments using the Select button. This was a missed use case in recent changes to related to AsyncUpload, and 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