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-232449 · Issue 742978

Able to use filter range on a table column

Resolved in Pega Version 8.8

While trying to filter results between a range in table column, the error "This results in an invalid numeric range" was generated. This has been resolved by adding a check for not setting the 'data-value' if the formatted value and target value are same.

SR-A85709 · Issue 255759

Cleared erroneous dirtycheck popup on DropDown using lazyload

Resolved in Pega Version 7.2.2

When a pxDropDown was configured with load mode "After screen renders", the "selected" attribute was not correctly set on the HTML and the dirtyCheck failed even when the values were saved. This was due to the "Selected" attribute on options tag not being set properly when the dropdown mode was set to lazyload (after screen render), and has been fixed.

SR-A88481 · Issue 256518

VBS starts with DDS configured to use external Cassandra

Resolved in Pega Version 7.2.2

If DDS is configured with Internal Cassandra which is then switched to External, DDS reports to be in state NORMAL and VBD can start. However, when starting from scratch with DDS configured to use External Cassandra, DDS was failing validation and reporting to be in state CLIENT, so VBD was unable to start due to VBD's check that ensures at least one DDS is in the NORMAL state before starting. To address this, the validation code that checks the DDS state when VBD is starting has been removed and the system will instead rely on the DSM service layer to ensure that DDS is functional before VBD can start.

SR-A22284 · Issue 249432

Data pages used as search fixed for mobile clients

Resolved in Pega Version 7.2.2

In an application accessed via mobile client, a data page used as source for a search was not rendering results when attempting a second search. This issue was happening because of a race condition, and has been resolved with an added settimeout for the asyncrendercallback of the RDL template.

SR-A90821 · Issue 258447

Delayed Learning data flows use dynamic objects

Resolved in Pega Version 7.2.2

Data flows with delayed learning enabled were failing to run when initiated by a campaign. The root cause for this bug was the process where a data flow object was created only once and the same object was shared between multiple data flow runs in the node. The changes for this fix include making the DataFlow object non-static in the DelayedLearning.java class.

INC-216490 · Issue 713634

pxIdentifier dynamically set for DecisionData while using GOS

Resolved in Pega Version 8.8

When using a Decision Data component in a strategy which was wrapped with Globally Optimized Strategy (GOS), no results were generated from the DataJoin shape under optimized execution. Investigation showed this was caused by a missing .pxIdentifier for the DecisionData shape during GOS execution. There was a workaround of unselecting the checkbox on the Advanced tab in the Decision Data component, but this has been resolved by updating the strategy kernel service so it will dynamically construct the pxIdentifier based on the skills assignment module (SSA).

SR-A77555 · Issue 259289

Improved handling for multiple access 'when' in business event processing

Resolved in Pega Version 7.2.2

It was possible to encounter a missing page in the business event processing if event processing performed a call to tools.getThread().getAuthorization().haveAccess in multiple activities and there were several access 'when' actions defined for the class. The access 'when' requires that a work page be present to evaluate against, and depending on how the call was being performed or if passivation has occurred the process could throw an IndeterminateConditionalException and pass a null as parameter value for "aPage" parameter. To prevent this error, the activities pxCreateSummary and pxGetPrimaryClasses have been changed to pass the ClipboardPage of class for which haveAccess() is being called.

SR-A77555 · Issue 260161

Improved handling for multiple access 'when' in business event processing

Resolved in Pega Version 7.2.2

It was possible to encounter a missing page in the business event processing if event processing performed a call to tools.getThread().getAuthorization().haveAccess in multiple activities and there were several access 'when' actions defined for the class. The access 'when' requires that a work page be present to evaluate against, and depending on how the call was being performed or if passivation has occurred the process could throw an IndeterminateConditionalException and pass a null as parameter value for "aPage" parameter. To prevent this error, the activities pxCreateSummary and pxGetPrimaryClasses have been changed to pass the ClipboardPage of class for which haveAccess() is being called.

SR-A22996 · Issue 250572

Logic updated for 'when' controlled edit modes in embedded sections

Resolved in Pega Version 7.2.2

Complex layers of 'when'-controlled edit modes were not being properly applied in embedded sections. For example, if the main section included another section and the read-only nature of the included section was controlled by a when rule and the included section went on to include another section that contained a Repeat Grid/ Row repeat, the edit mode of the parent was not considered when evaluating the edit mode of the child. This was an issue with the logic governing precedence considerations, and has been updated with additional checks.

SR-A22996 · Issue 252883

Logic updated for 'when' controlled edit modes in embedded sections

Resolved in Pega Version 7.2.2

Complex layers of 'when'-controlled edit modes were not being properly applied in embedded sections. For example, if the main section included another section and the read-only nature of the included section was controlled by a when rule and the included section went on to include another section that contained a Repeat Grid/ Row repeat, the edit mode of the parent was not considered when evaluating the edit mode of the child. This was an issue with the logic governing precedence considerations, and has been updated with additional checks.

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