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-D34214 · Issue 511814

API available to skip defer loading in Single Page Applications

Resolved in Pega Version 8.1.7

The wait message "Loading ..." was displayed on check on defer load in Single Page Applications. The browser refresh worked as expected if 'defer load' was unchecked. This was traced to SPA not containing the handling necessary to publish the forced replace to other modules: in SPA cases, the dashboard is forcibly replaced with workobject harness, causing defer loads in dashboard to be processed in the wrong thread. To resolve this, there is now an exposed API pega.ui.DCUtil.skipDeferredLoadFrom() to skip defer loading when true in SPA.

SR-D5904 · Issue 490489

Discard changes dialog now showing for local actions

Resolved in Pega Version 8.1.7

After having modified case data without saving and clicking on a menu entry (left menu, search, ...), the system shows a dialog box to ask the user to confirm it is ok to discard changes. However, this confirmation dialog did not work with local actions, leading users to lose their work without any warning nor any way to step back. This was traced to a difference in the dirty form check, which was not present when launching a local action from a case. An enhancement has now been added to the handleMenuAction js function in pypega_ui_harnessactions.js which will perform a dirty form check with a prompt.

SR-A6265 · Issue 214301

Enhanced justification carryover during migration

Resolved in Pega Version 7.2

It was noted that after upgrade, some justifications were lost due to the differences in the warning messages between versions. Justifications are attached to each individual warning and each individual warning is saved with the rule, and the intent was that the justifications come with the RAP on a migration. However, many warning messages have been updated for language, style, content, etc., in new versions. This meant that after migration, resaving a rule caused the old warning (and hence justification) to be lost when the new and improved warning message was attached in its place. To ensure expected behavior, the system will now look for old warnings and map them to updated warnings while keeping the associated justification.

SR-A9225 · Issue 222951

Long word break added to SMA tables

Resolved in Pega Version 7.2

In Microsoft Internet Explorer 11, the SMA system management screen (the screen right after login) would sometimes not display the relevant fields in the tables until the horizontal scrollbar was moved all the way to the right. This was different behavior than with other versions of Microsoft Internet Explorer , and occurred when the content of a table-cell included a very long value without any word break. In this case, current style control could not break the long wording out to pieces, resulting in it crossing over the whole screen until the word was displayed. This was a cosmetic issue that did not influence operations, but style control has been added to enforce long word break in these cases.

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