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-191226 · Issue 679379

Corrected data page value loading

Resolved in Pega Version 8.7

Values were not loading from a data page in Property. This was traced to a leading "." character in the property name, i.e. ".PropertyName" which prevented the rule being opened from the database due to incorrect property rule keys . This has been resolved by removing the leading dot.

INC-191567 · Issue 676156

New application wizard security updated

Resolved in Pega Version 8.7

Security around displaying and running the new application wizard has been enhanced.

INC-191902 · Issue 677412

Updated security for importing Excel to a decision table via a delegated rule

Resolved in Pega Version 8.7

An error was seen when attempting to import an Excel file into a delegated decision table when using the case manager portal. This has been resolved by correcting a BAC issue for decision table import in the pzRuleDeclareDecisionTableStandard.js file.

INC-192092 · Issue 677438

Info messages added to merge and errors on merge failure

Resolved in Pega Version 8.7

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 681751

PackageComponent updated for use with repositories

Resolved in Pega Version 8.7

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 678115

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

Resolved in Pega Version 8.7

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 679210

Security updated for @baseclass

Resolved in Pega Version 8.7

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 679897

New Application wizard disabled or enabled correctly

Resolved in Pega Version 8.7

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.

SR-D91834 · Issue 554425

Related cases of different types properly linked in Case Worker Portal

Resolved in Pega Version 8.5

After creating a case of type1 in the Case Worker portal, creating a case of type2 from the first case showed the case ID of the second case in the Related Work section as expected. However, after clicking on the link of the case ID of the second case from the related work section, the second case opened but the case ID of the first case was not shown in the Related work. The cases were correctly associated when the Case Manager portal was used instead. This was traced to the Case Worker clipboard continuing to hold the previous case ID thread, and has been resolved.

SR-D71475 · Issue 538721

Check added to apply values of newAssignPage.pxFormName

Resolved in Pega Version 8.5

After upgrade, trying to open existing assignments resulted in a different harness being opened. This was traced to changes in how the property newAssignPage.pxFormName was used, and has been resolved by checking whether the harnesspurpose is dynamic before setting the pxFormName. If formname is already present, the system will proceed with picking the harness from the shape.

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