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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-130147 · Issue 196723

pxCWOptionsMenu now localized

Resolved in Pega Version 7.1.8

Localization has been added for the section pxCWOptionsMenu.

SR-130208 · Issue 198155

Handling added for step page call to DeleteAssignment

Resolved in Pega Version 7.1.8

After upgrade, the pxDeleteAssignment with step page Assign-Workbasket was not working as expected. The error was traced to the 'DETERMINELOCKSTRING' activity being available in Work- class while the local customization was passing the Assign- page as the steps page. Handling has been added for cases when the activity gets called on a page other than primary work page.

SR-130224 · Issue 200002

Fixed class pickup when Ticket Urgency is used as reference

Resolved in Pega Version 7.1.8

It was not possible to convert a summary report to a list report if the report had Ticket.Urgency as a reference and Ticket was a single page pointing to data class type property in the work class. This was traced to the drill down picking up the Urgency property from the work class, and has been resolved.

SR-130249 · Issue 199071

Resolved validation error for modal window with right tabs

Resolved in Pega Version 7.1.8

Validation errors in a modal window could cause the user session to hang when the content of the modal window was configured to use a tab group with tabs positioned to the right. This was a div ordering error in the API, and a check was added for tab position right.

SR-130269 · Issue 197947

SmartInfo call updated for Listview in standards mode

Resolved in Pega Version 7.1.8

After upgrade, instances of SmartInfo configured on listview showed improper styles. This was due to the older version of the SmartInfo control being used when the document was in standards mode. The listview function has been updated to use the updated SmartInfo control for proper rendering.

SR-130345 · Issue 199748

Added qualification to validation queue page creation

Resolved in Pega Version 7.1.8

After migration, executing custom business logic validation generated the error "There was a problem getting a list". This was due to the JS code generating an unqualified QueuePage, and has been resolved.

SR-130363 · Issue 200006

Dynamic decimal place value setting added

Resolved in Pega Version 7.1.8

Previously, the 'pxNumber' control had Decimal Places set to 2. This setting became Auto in ML7, which resulted in no decimal values being displayed for whole numbers in some installations with custom settings after upgrade. To facilitate overriding this out-of-the-box function, a dynamic setting has been added: create a dynamic system setting rule with purpose "DecimalPlacesforpxNumber" in the ruleset "Pega-UMicrosoft Internet Explorerngine" with a given value from -1 to 10, and it will override the Auto value in the pxNumber control decimal places setting.

SR-130401 · Issue 201418

Fixed listview filtering header shift

Resolved in Pega Version 7.1.8

When using a list view in a section with filtering enabled, applying any filter criteria caused the header to shift down vertically and create a gap. This was a display div error, and has been fixed.

SR-130401 · Issue 200029

Fixed listview filtering header shift

Resolved in Pega Version 7.1.8

When using a list view in a section with filtering enabled, applying any filter criteria caused the header to shift down vertically and create a gap. This was a display div error, and has been fixed.

SR-130421 · Issue 200325

Corrected double firing after copying trigger to superclass

Resolved in Pega Version 7.1.8

After copying a commit trigger from PegaSample-CustomerRequest to PegaSample and withdrawing the original, the new version fired twice on commit. This was caused by the RuntimeDeclarativeClassCore not properly handling the duplicate, and has been corrected.

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