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.

INC-146098 · Issue 633722

Keyboard shortcuts work in Decision Trees

Resolved in Pega Version 8.3.6

Keyboard short cuts in Decision Trees used to copy/paste by holding ctrl button in Decision Trees were not working. This was an unintended side effect related to changing non-auto grid to an auto-generated hierarchical table to make the Decision tree rule form multi-browser compatible, and has been resolved by adding cut/copy/paste/insert-after/insert-before functionality to the decision tree context menu.

INC-151662 · Issue 626576

Handling added for application which includes production ruleset

Resolved in Pega Version 8.3.6

When creating the Email channel or Webchat channel, the Text Analyzer and its respective class (Data-Decision-Request-MCP-WebChat-xxxxx) was being saved in the ruleset of the built-on application while there were rulesets open in the top application. This was a missed use case, and has been resolved byupdating the logic to account for the scenario where an application includes a production ruleset.

INC-164944 · Issue 636290

Logic updated to handle decision trees over 64k

Resolved in Pega Version 8.3.6

An exception was thrown when decision trees reached the 64K size limit. This has been resolved by modifying the logic in the DecisiontableMethodBody Rule-Utility-Function where the split size PropRowLimit is based on the number of columns.

INC-169112 · Issue 647080

Decision Trees refresh after updating a new row

Resolved in Pega Version 8.3.6

Updating a decision tree row did not display the updated data until after save and refresh. This was traced to the first row not meeting the condition for refresh on change because the first row was created as part of the decision tree creation, so the data was not persisted and the update was not registered as a change. This has been resolved by adding explicit handling for the first row to persist its expression string and show the data as entered.

INC-155276 · Issue 622816

Null check added for step page

Resolved in Pega Version 8.3.6

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.

INC-156647 · Issue 626293

Improved disconnected requestor cleanup for FieldService

Resolved in Pega Version 8.3.6

A large number of requestors from FieldService with the status as 'Disconnected' were accumulating and causing performance issues. This was traced to the requestors not getting passivated due to users not logging out and new requestors being created for the same users next time, and was caused by the value of the DSS Initialization/PersistRequestor being set as "OnTimeout". When the DSS prconfig/timeout/browser/default is not configured, the default browser requestor timeout is 60 minutes. In this scenario, requestors were not passivating as the requestor passivation timeout was set to the refresh token lifetime for mobile users, which was very large and overwrote the DSS value. This has been resolved by removing the code which set the passivation timeout to the OAuth2 refresh token lifetime.

SR-A19119 · Issue 241157

Improved error handling for XML-executed BIX extract failures

Resolved in Pega Version 7.2.2

When BIX extracts configured through an XML script encountered a target table that did not exist, the script itself did not visibly fail even though the error "Table doesn't exist in target database" was logged, and any extracts that were executed after that error did not generate any output. This has been corrected to set the correct error flags to ensure expected behavior.

SR-A87291 · Issue 255631

JDBC password encryption check logic updated

Resolved in Pega Version 7.2.2

When using a Database instance with a JDBC connection URL, the specified password is encrypted. An issue was occurring where multiple saves of the instance caused the encrypted password to be encrypted again, causing the agent to lose access to the DB due to an authentication failure. The problem was traced to a logic flaw in the method used to check whether the password was already encrypted, and has been fixed.

SR-A76706 · Issue 252781

Modified pyLoadDataTypes data transform to match expected type

Resolved in Pega Version 7.2.2

Activities configured with "Double" as the data type were converted to "String" datatype in the activity after upgrade. This was due to the Data Transform pyLoadDataTypes rule using the pyLabel "DOUBLE" for double parameter type instead of "Double", and has been corrected.

SR-A77495 · Issue 254777

Corrected delete error with first row of Decision Table

Resolved in Pega Version 7.2.2

After clicking 'delete row' on the first row of a decision table the first row was not visible, but it was observed that when saving the first row it remained as it was and instead the second row was deleted. This was an error in highlighting and positioning, and has been fixed.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us