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.

INC-192092 · Issue 677439

Info messages added to merge and errors on merge failure

Resolved in Pega Version 8.6.3

Logging used in the Merge Wizard process has been updated to provide feedback as the branches merge. In addition, the merge logic has been modified to use StepStatusFail as opposed to StepStatusGood.

INC-192464 · Issue 681752

PackageComponent updated for use with repositories

Resolved in Pega Version 8.6.3

Exporting a zip file created by the Component wizard to a repository resulted in an error, however the same process worked as expected when the zip file was created by the Product wizard. Investigation showed that pxPackageComponent was not kept up to date with new metadata requirements for Artifactory export. This has been resolved by modifying pxPackageComponent step 7 to set Param.ArtifactType to "component" and Param.ArtifactName to [component name]_[component version]. A privilege check has also been added to zipMoveExport.

INC-192833 · Issue 678116

New Application Wizard will default to existing work groups if none are created

Resolved in Pega Version 8.6.3

When using the new application wizard to create a new application, the new app API replaces the old work pools with the newly generated ones. If the new application configuration was done in such a way that classes are not generated due to reusing existing classes, access groups were being generated with empty work pools. To resolve this, the system has been updated to use the existing work pools if the new app didn't generate new work pools.

INC-193289 · Issue 679211

Security updated for @baseclass

Resolved in Pega Version 8.6.3

After update, searching for a baseclass 'when' rule returned no results. Listing the rules under baseclass in App Explorer resulted in the error "Applies To: The Class with key value(s) %40baseclass does not exist". This was an unintended side effect of security updates, and has been resolved by creating an exception path for "@baseclass".

INC-194227 · Issue 679898

New Application wizard disabled or enabled correctly

Resolved in Pega Version 8.6.3

The New Application wizard was disabled with the error message: "Application creation is disabled as the current operator is in invalid state". This was traced to edits made to the Operator page which caused the new app wizard to not be shown due to failed validation. To resolve this, an update has been added which will refresh the operator page on click of the menu so the New Application wizard is disabled or enabled correctly.

INC-196266 · Issue 694838

Performance improvements for CDH

Resolved in Pega Version 8.6.3

Significant slowness was seen in Customer Decision Hub (CDH) during save-as or check-in/check-out of an offer rule. This has been resolved by passing the current parameter page to the RuleCheckOut activity in pxUpdateRecordInner so that CDH can pass a skipValidate parameter to skip the validation during checkout.

INC-198113 · Issue 693354

Link-Association-Follow updated

Resolved in Pega Version 8.6.3

The report definition 'pyGetAssociations' was generating the error "data.internal.rd.reference.InvalidReferenceException InvalidReferenceException .pxLinkedRefTo Cannot use an unexposed property as there is no BLOB column for the class: 'Link-Association-Channel'". This has been resolved by updating pzUnfollowReview to handle Link-Association-Follow, which will prevent these log errors.

INC-203548 · Issue 694854

Performance improvements for CDH

Resolved in Pega Version 8.6.3

Significant slowness was seen in Customer Decision Hub (CDH) during save-as or check-in/check-out of an offer rule. This has been resolved by passing the current parameter page to the RuleCheckOut activity in pxUpdateRecordInner so that CDH can pass a skipValidate parameter to skip the validation during checkout.

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