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-140160 · Issue 597037

NLP model update reflected on utility nodes

Resolved in Pega Version 8.5.2

After training models on a web node, model updates were not reflected in the email listeners running on the utility nodes. This was traced to the implementation of the model storage using obj-save, which does not propagate the static content on nodes apart from where it was saved. To resolve this, the implementation has been updated to use WBSave which clears static content on all the nodes.

INC-205453 · Issue 706568

Pega Keystore supported for hotfix signature verification

Resolved in Pega Version 8.6.4

In order to support custom trust managers which require an alternate method for supplying the root certificate via a platform trust store, an enhancement has been added to allow Pega Keystore to be used as a hotfix verification source. Detailed information on this can be found in https://docs.pega.com/keeping-current-pega/87/verifying-hotfix-authenticity-using-pega-keystore

INC-204998 · Issue 705630

Data page definition reload made more robust

Resolved in Pega Version 8.6.4

The data page was intermittently being removed from the cache. This was traced to the use of a thread from ThreadContainer to reload the data page definition: a null thread could be returned if the request came from a master agent, which would then cause the definition reload to fail. This has been resolved by updating the system to use the current thread in context to reload the data page definition.

INC-211599 · Issue 708542

Data page definition reload made more robust

Resolved in Pega Version 8.6.4

The data page was intermittently being removed from the cache. This was traced to the use of a thread from ThreadContainer to reload the data page definition: a null thread could be returned if the request came from a master agent, which would then cause the definition reload to fail. This has been resolved by updating the system to use the current thread in context to reload the data page definition.

INC-142214 · Issue 598766

Null Checks added for Null Dereference

Resolved in Pega Version 8.5.2

Null checks have been added to CSSAsJson and to the activeValue variable, which is used for the checked attribute generation.

SR-D48248 · Issue 517238

Cross-site scripting filtering added to URLs

Resolved in Pega Version 8.2.5

Cross-site scripting filtering has been added to prevent the injection of a script into a URL using ViewXML.

SR-D47752 · Issue 513751

Resolved Assembly time error for findPage signatures with two arguments

Resolved in Pega Version 8.2.5

Due to the introduction of IL assembly, an Assembly time error was generated after upgrade when saving a 'when' rule that had a page with the same name defined in both Parameters and Pages & Classes. To resolve this, if the system is generating PegaAPI#findPage or PegaAPI#findPageWithException and passing a null as the second argument, then it will be cast as a String. This will ensure the compiler will not become confused as to the type of null when there are multiple findPage signatures with two arguments.

SR-D40778 · Issue 512975

Asterisk symbol displayed for radio button set to required always

Resolved in Pega Version 8.2.5

When marked as required, the "Asterisk" symbol did not show up on the radio button label. This was traced to an XML cleanup issue with the pyReqRunOnClient property when required was configured as 'always' and has been corrected.

INC-145540 · Issue 601590

Added handling for email folder close exception

Resolved in Pega Version 8.5.2

EmailListeners were marking messages as ERROR when it encountered a FolderClosedException when retrieving message detail from the inbox. This has been resolved by adding handling for the folder closed exception in getMessagebyMessageId method so that the message will be marked as initial and retried.

INC-180246 · Issue 664947

Support for apostrophe added to keyword tokenization

Resolved in Pega Version 8.6.4

A keyword containing an apostrophe was not detected properly in Text extraction model. This has been resolved by updating the annotator used in the tokenization.

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