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-D60206 · Issue 529327

Resolved null pointer on Reference Helper startup

Resolved in Pega Version 8.5

An issue with the system failing to start and generating a NullPointerException on RUFReferenceHelper.java has been resolved by modifying some Rule-Utility-Function code to better handle threads that are not completely initiaized yet but still running rules.

SR-D74534 · Issue 538945

Decision table and tree obey allow missing properties checkbox

Resolved in Pega Version 8.5

Calling the decision table/tree inside another decision table/tree which has a missing property was throwing an error even though the "AllowMissingProperties" checkbox was enabled in the caller activity. Analysis showed that the setting for AllowMissingProperties did not carry into any subsequent DecisionTree/DecisionTable calls from the top DecisionTree/DecisionTable, and this has been resolved by modifying the decision table and decision tree obtain value functions to pass AllowMissingProperties.

SR-D66615 · Issue 536242

API added to minimize calls to set parameters in datapage

Resolved in Pega Version 8.5

Differences were seen after upgrade when using a datapage associated with a property which was application-specific and that had Data Access for the property defined as “Copy data from a data page" with parameters whose value was set by an activity from the associated property of type single page. Prior to upgrade, only one call was seen to set the values for the parameters in datapage, but post-upgrade multiple calls were used to set the values to these parameters. This was traced to logic used for extraction and invoking the perform, and has been resolved by adding the new API 'DeclarativeAction.shouldExtractWatchedProperties'. It will return true or false, depending whether the extraction of watch properties is needed or not.

SR-D69836 · Issue 529729

Context retained during nested automation

Resolved in Pega Version 8.5

Issues were seen with context being passed correctly with automation. When a Data Page that was used to abstract the call to a REST API used a Data Transform which in turn used a Data Page which also used a call to a REST API to retrieve an OAuth Token, an error appeared. The same worked when a URL was provided on the Connect REST. When a service case was launched but a Flow Action wasn't submitted, then another service case was added and submitted, the post-processing robotic automation activity used the run robotic automation activity from the previous service case instead of the current service case targeted for completion. This has been resolved by updating the webwb • pzpega_ui_doc_submit.js file to pass the correct MDIContext based on the event target of FA submission while invoking RDA automation.

SR-D62840 · Issue 534125

Updated HashMap logic for better concurrent thread handling

Resolved in Pega Version 8.5

The Pega execution engine was getting stuck at com.pega.eclipse.util.collections.HashtableOfIntValues.get for many thread within thread dumps. Investigation showed that when the key was not present in keytable, a thread would be stuck in an endless 'while' loop related to mapping. To resolve this, the data structure that is used for ruleset mapping from HashtableOfIntValues to Concurrent HashMap has been modified to better handle concurrent threads, and the handling for get and put has been updated.

SR-D60830 · Issue 533030

Logic update for classloading synchronization

Resolved in Pega Version 8.5

The synchronization logic for classloading has been updated to resolve intermittent deadlocking seen when two DataFlow threads are executing a distribution test.

SR-D84880 · Issue 546891

Null check added to resolve addmapcasetomap error

Resolved in Pega Version 8.5

Using a createcase flow shape to create child cases by looping on a page list on the parent case resulted in pzaddmapcasetomap throwing an exception related to the activity pzLoadCaseHierarchyWrapper in step 5. This was traced to a page being removed after the list of pages was received in findPageByHandle, and has been resolved by adding a null check.

SR-D78531 · Issue 542001

Encoding added for special characters in JFROG filenames

Resolved in Pega Version 8.5

A blank screen or the error "Unable to get the file from Repository" appeared when attempting to attach a file from JFROG Repository if the file name contained special characters. This has been resolved by modifying the artificatory URL generation to properly encode special characters during file download.

SR-D67142 · Issue 548642

Enhanced CMIS connector logging

Resolved in Pega Version 8.5

Additional diagnostic logging has been added to enhance investigating CMIS connector health.

INC-129171 · Issue 566576

Field added to configure jFrog artifactory context root

Resolved in Pega Version 8.5

After configuring a JFrog repository rule and successfully testing the connection (from the rule configuration page), attempting to browse the remote repository from the "File Storage" landing page did not work. Investigation showed that ArtifactoryStorage.java was automatically appending "/artifactory" to the host name of any artifactory repo instance, causing a mismatch with the configured URL. There was a workaround of configuring the hostname with a context root, but this issue has been resolved with an additional ruleform field to specify the context root. Leaving this field blank will create the url using strictly what is contained within the host name field, while populating it will construct the url as follows: url + contextRoot + "/artifactory" This field will default to "/artifactory" to help preserve backwards compatibility.

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