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-A7290 · Issue 216208

Made autocomplete field visible for mobile

Resolved in Pega Version 7.2

There was a problem with the visibility of the autocomplete field when used for add/remove buttons on mobile. The webkit-transform function was updated for smoother transition.

SR-C6751 · Issue 349286

Corrected duplicate table names for DB2 z/OS import

Resolved in Pega Version 7.4

When using Explicit DDL generation for DB2 z/OS, auxiliary tables were generated with the same name when deploying on single schema deployment. This happened when importing archives that created tables in both the PegaRULES and PegaDATA logical DBs when those logical DB names corresponded to the same database schema, and was due to the handling of lob table names for single schema deployments using Pega DB logical names for storing the last generated index. This has been fixed by changing to tracking the last generated index by DB2 z/OS database name / database schema name in order to prevent PegaRULES and PegaDATA lob tables from having naming collisions.

SR-C6751 · Issue 349078

Corrected duplicate table names for DB2 z/OS import

Resolved in Pega Version 7.4

When using Explicit DDL generation for DB2 z/OS, auxiliary tables were generated with the same name when deploying on single schema deployment. This happened when importing archives that created tables in both the PegaRULES and PegaDATA logical DBs when those logical DB names corresponded to the same database schema, and was due to the handling of lob table names for single schema deployments using Pega DB logical names for storing the last generated index. This has been fixed by changing to tracking the last generated index by DB2 z/OS database name / database schema name in order to prevent PegaRULES and PegaDATA lob tables from having naming collisions.

INC-140821 · Issue 600750

Resolved Intermittent Access Group Issue for GetBundleEventDecisionDetails

Resolved in Pega Version 8.4.4

When using a REST service that calls the GetBundleEventDecisionDetails activity and dataflow to send the treatment in multiple channels, intermittent access issue related errors appeared while running the activity in logs for multiple customers. This was traced to a missed use case for authentication, and has been resolved.

INC-177665 · Issue 662020

Security updated to allow Access group switching

Resolved in Pega Version 8.7

When a member of two different access groups attempted to switch from one group to another, an "access denied" message occurred. This was traced to the use of BAC, and has been resolved by updating the pzProcessApplicationSwitch activity to use the pzEncryptURLActionString function to register the request.

INC-186868 · Issue 675245

Security updated to allow Access group switching

Resolved in Pega Version 8.7

When a member of two different access groups attempted to switch from one group to another, an "access denied" message occurred. This was traced to the use of BAC, and has been resolved by updating the pzProcessApplicationSwitch activity to use the pzEncryptURLActionString function to register the request.

INC-176205 · Issue 655938

Secure shared link generation added to scheduled reports

Resolved in Pega Version 8.7

When a scheduled report with a link was sent in email, clicking the link displayed an access denied message. To support this use, logic has been added to pytaskoutputprocessor in the pega-scheduledtask-reporting and pega-scheduledtask classes that will create a secure encrypted URL using the PublicLinkURL function.

SR-A9198 · Issue 218533

Text retrieval for deprecated "Query" button updated for universal browser support

Resolved in Pega Version 7.2

The Firefox popup window provided by the Product rule when querying "Individual Instances to Include" failed to transpose the selected rule information back into the Product ruleform when the OK button was clicked. This was due to the use of the deprecated "Query" button, which does not have support for all browsers, to launch the ListView. To handle this, the node text retrieval method in DataInstancesQueryScript has been updated to use the 'textContent' function (compatible with all browsers) instead of the previous 'innerText'.

SR-B97032 · Issue 342812

Target stale check added to cascading dropdowns

Resolved in Pega Version 7.4

The system was hanging when hovering on the drop down after selecting a parameter for which the dropdown did not have any values. This was due to the target element becoming stale when cascaded dropdowns were used, and has been fixed by adding a check for this condition.

SR-A7482 · Issue 220320

Reset validation activity for deferred loading with alternate page context

Resolved in Pega Version 7.2

If a section was configured to use a defer load activity and the page context was set to something other than the defer load activity class, the defer load activity was not visible when attempting to set the pre-load activity and an error was generated. This was caused by a change to the defer load activity validation that pointed to the using page class instead of the previously used section class. The validation has now been reset to to use the section class instead of using page class in order to support rendering on a different page.

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