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-139086 · Issue 597146

"Show next error" correctly displayed on user portal

Resolved in Pega Version 8.5.3

In the Case Worker user portal, the Show Next Error link was not shown when the layout group had a validate rule in the flow action. The same configuration worked as expected in Case Manager. This was a missed use case, and has been resolved.

INC-144778 · Issue 619615

Performance improvements for Ajax tab switching

Resolved in Pega Version 8.5.3

When using a 360-view of members in a portal implemented with an Ajax container that showed information in multiple tabs, tab switching was taking a lot of time even though the data was already in the memory. Updates have been made to improve performance.

INC-157041 · Issue 626312

Performance improvements for email listener processing

Resolved in Pega Version 8.5.3

Email processing was taking an excessive amount of time when a very large number of email listeners were running. Performance has been improved by updating the implementation of pzGetChannelByName to use obj-browse instead instead of looping through channels.

SR-A89637 · Issue 259256

Search for Work gadget updated to accept "StartsWith"

Resolved in Pega Version 7.2.2

When using a fixed portal, the Search for Work gadget was not working for the option "Starts With" when pxOperatorMap rule was being called from newly added Property-Map-Value methods. This was caused by pxOperatorMap not having a return value for StartsWith, causing the default value"=" to be returned. This has been fixed by adding a return value for "StartsWith", "NotStartsWith", "EndsWith", "NotEndsWith", "Contains", "NotContain", "IsNull", and "IsNotNull" in pxOperatorMap.

INC-155752 · Issue 622772

Hidden Question pages and answers will be saved to database

Resolved in Pega Version 8.5.3

After a question page was shown and some values were entered, going back to the question and reverting an option caused the question page to not be visible, but the answer values persisted in the clipboard and were eventually saved into the database. This was a missed use case for Question page smart shapes, and has been resolved by updating the pzSetQuestionPageParams data transform so that whenever a question page is evaluated to either to show/hide, when the question page visibility is set to false and the pyClearAnswerValuesWhenQPHidden 'when' rule is overridden, the corresponding values will be wiped from the clipboard and only the required values will be saved to the database. However, please note this is not supported for branching logic and visibility conditions should be used instead.

SR-A81527 · Issue 254655

Unlocked rulesets for UI-Kit-7 and Pega-Desktop

Resolved in Pega Version 7.2.2

When using UI tollgate, the message 'Sentence case is not followed' would sometimes appear due to no unlocked rulesets being available in UI-Kit-7 and Pega-Desktop. In order to facilitate the UI issues pass, the rulesets have been made available.

SR-A88333 · Issue 256129

Corrected Interaction Header unexpected refresh

Resolved in Pega Version 7.2.2

Every time a new intent task was launched or closed in Interaction Portal, the Interaction header refreshed without any explicit configuration to refresh the header. This was due to the process used when evaluating the cross thread change tracker and has been fixed.

SR-A81527 · Issue 254654

Unlocked rulesets for UI-Kit-7 and Pega-Desktop

Resolved in Pega Version 7.2.2

When using UI tollgate, the message 'Sentence case is not followed' would sometimes appear due to no unlocked rulesets being available in UI-Kit-7 and Pega-Desktop. In order to facilitate the UI issues pass, the rulesets have been made available.

INC-155276 · Issue 626619

Null check added for step page

Resolved in Pega Version 8.5.3

After creating and adding new Access Roles and application 'Access When' to the privileges instead of Production level, during run time the error "runtime.IndeterminateConditionalException: Trying to evaluate Rule-Access-When conditions L:IsProdAccess when there is no page to evaluate them against" appeared for the specific privileges. This was traced to a missed use case where the system falls back to the step page if the page for evaluating the 'when' condition is null, which did not account for scenarios where the step page can be null. To resolve this, a null check has been added which will fetch the primary page if the step page for the access 'when' condition is null.

SR-A92755 · Issue 261497

Fixed links display with privilege option in repeating grids

Resolved in Pega Version 7.2.2

When making use of the privilege option in the link control configuration as a condition to enable/disable the links in the repeat grid, the links were disabled/hidden even when the operator had the correct privilege. Analysis showed this happened in cases where the primary page was different from the page context on which the current part of the section was rendering (for example, when a grid or repeating dynamic layout is present), and it has been fixed by passing the current step page to the pega_rules_default.ValidatePrivileges function instead of passing the primary 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