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-121820 · Issue 182933

Next button behavior in a modal dialog corrected

Resolved in Pega Version 7.1.8

A workflow issue was found with the 'Next' button on a last row of a repeating grid where clicking on the 'Previous' button would then improperly make available a previously grayed out 'Next' button. Similarly, clicking the 'Next' button on the next-to-last row fired the validation but then disabled the 'Next' button. This was traced to the "NextDisabled" parameter being set incorrectly in case of server side errors, and has been fixed.

SR-121828 · Issue 179859

Localization added for the "Loading" text of the busy indicator

Resolved in Pega Version 7.1.8

Previously, the 'alt' values of the "Loading" text for the pega_ui_busyIndicator (pxThrobber) were hard-coded to English. This has been changed to allow localization.

SR-121969 · Issue 184370

Deleted attachments flow error fixed

Resolved in Pega Version 7.1.8

If an attachment was added and submitted and then deleted from the attachment tab, the application then generated an error. This was caused by the system passing an invalid FromFrame after closing the modal dialog, and the code has been updated to use the originalFromFrame value when launching the flow.

SR-121980 · Issue 181118

Microsoft Internet Explorer 11 support added for auto-complete with multiple line properties in Report Definition

Resolved in Pega Version 7.1.8

If a property in a column of ReportDefinition that contains a carriage return (in order to input and display the value on two lines in the results) was then used as a source to Autocomplete control, then autocomplete control was not displaying the results. This was caused by a broken display with the Microsoft Internet Explorer 11 browser in compatibility mode, and code has been added to escape the new line character before converting the string to a JSON object so it will display as expected.

SR-122118 · Issue 180259

Improved condition handling for complex harnesses

Resolved in Pega Version 7.1.8

If a Review Harness had multiple embedded tab sections with includes, a read-only condition in the parent section was not being honored in a sub-section if the 'when' condition became false. This happened when a SectionIncludeInCell RUF passed an unquoted null value as a 3rd argument while invoking stream reference, and has been resolved.

SR-122118 · Issue 183909

Improved condition handling for complex harnesses

Resolved in Pega Version 7.1.8

If a Review Harness had multiple embedded tab sections with includes, a read-only condition in the parent section was not being honored in a sub-section if the 'when' condition became false. This happened when a SectionIncludeInCell RUF passed an unquoted null value as a 3rd argument while invoking stream reference, and has been resolved.

SR-122176 · Issue 184992

Older button visibility conditions retained after upgrade

Resolved in Pega Version 7.1.8

After migration, older button controls set to visibility "ALWAYS" and when condition "canPerform" became visibility "WHEN" and when condition "canPerform". To resolve this, the logic for the activity Embed-Harness-Section!UpgradeOnOpen has been updated to check for "VISIBILITY" first before "visible when" to retain the proper settings.

SR-122191 · Issue 182679

Smoothed post-upgrade ApplicationSetup that uses previously generated LDAP configs

Resolved in Pega Version 7.1.8

An LDAP configuration created under a previous version of the software was generating an NPE after upgrading. This was traced to step2 of the ApplicationSetup activity where the system was expecting a page which was missing at that point due to the user not yet being fully identified. To avoid this, a step has been added to check if the page is available and avoid the NPE.

SR-122213 · Issue 184299

Cache clearing corrected for muti-tenant environments

Resolved in Pega Version 7.1.8

A problem with the caching system in a multi-tenant environment led to a situation where a change in a rule in the shared layer did not invalidate that rule's entry in the tenants' rule cache. This was caused by the clearing of the cache not being fully propagated to all tenants, and the system has been updated to ensure the SMA clear cache fully clears all shared and tenant instances.

SR-122264 · Issue 182315

Preview Included Section corrected for Case Manager portal

Resolved in Pega Version 7.1.8

The Section Include preview feature was implemented with support in the Developer Studio, but was found to not be working as expected in the Case Manager Portal. This was due to a wrong 'if' condition for span identification, and the system has been updated.

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