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-182150 · Issue 669853

DSS added to control Pega Version Banner

Resolved in Pega Version 8.7

Nuisance errors were being logged related to the application trying to connect to Pega to confirm available versions. This has been resolved by adding the 'when' rule pyShowVersionBanner to pzStudioHomeWrapper which allows disabling/enabling the Version Banner based on the setting used in the DSS ShowVersionBanner. pyShowVersionBanner defaults to true when DSS ShowVersionBanner does not exist.

INC-220770 · Issue 718027

Null check added to getBaseRef

Resolved in Pega Version 8.6.5

When using a customized Cosmos portal that included tabs, some of the Pega APIs were not available in the child frame and javascript errors were generated when calculating the clipboard path for live UI elements. This was traced to invalid references to "pega.api.ui.util.getBaseRef", and has been resolved by adding null checks to the getBaseRef API call to make sure javascript errors are not thrown.

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-179769 · Issue 671024

Document generation new line formatting made consistent

Resolved in Pega Version 8.7

The GenerateWordDocument API and Generate Document shape were not adding new line to a Word document even when Text Area format was used. This was traced to a difference in document generation which varied between adding \n and adding \r\n for new line, causing inconsistent behavior, and has been resolved.

INC-164171 · Issue 644707

Support added for connect-SOAP run in parallel mode

Resolved in Pega Version 8.7

When connect-SOAP was configured to use the “run in parallel” mode, application settings derived through a datapage had incorrect values. While running the connect-SOAP through an activity, all the values were derived incorrectly. This has been resolved by adding a synchronization enhancement to support parallel run connect.SOAP.

INC-181091 · Issue 662778

Strategy rules open from proposition filter after update

Resolved in Pega Version 8.7

After update, strategy rules could not be opened from the proposition filter. This was caused by the pxInsName property being populated only when a strategy rule gets selected/configured from the CB gadget. For upgrade scenarios where the condition is already configured with a strategy rule, the pxInsName property will be missing. To handle this upgrade use case, the "Rule-open-by-keys" action will be used instead of "Rule-open-by-name", as rule keys are always present while pxInsName gets populated for only new configurations.

INC-136187 · Issue 596094

Mask hidden as expected in small window/tablet view with Dragon

Resolved in Pega Version 8.5.2

When using Dragon in a small window/tablet view, the mask was not getting removed as expected. Performing a mouse click on the tab was successful for hiding it. To resolve this, Data-portal!pzProfileMenu has been modified to run the script removeScreenLayoutMask after clicking Profile, Preferences, Operator, Access Group, and My Favorites > Edit .

INC-175533 · Issue 678909

Improved Page compare for page groups

Resolved in Pega Version 8.7

Field level auditing on embedded properties sporadically did not report the "old" value when a property was modified even though the page was listed as "Modified". This has been resolved by adding logic to the pxComparePages algorithm to treat Lists and Groups differently. Now Page and Value Groups will use pxSubscript as the primary way to detect add and deletes.

INC-182576 · Issue 677527

Improved Page compare for page groups

Resolved in Pega Version 8.7

Field level auditing on embedded properties sporadically did not report the "old" value when a property was modified even though the page was listed as "Modified". This has been resolved by adding logic to the pxComparePages algorithm to treat Lists and Groups differently. Now Page and Value Groups will use pxSubscript as the primary way to detect add and deletes.

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.

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