INC-154290 · Issue 613471
Signature capture exception resolved
Resolved in Pega Version 8.4.4
The signature capture control was throwing a JSON parse exception when the value was set and section was refreshed. This was caused by the signature for PIMC passing incorrect data which Preview could not parse, and has been resolved by ensuring the correct data for PIMC local store.
INC-154495 · Issue 613700
Null check added to DT set action
Resolved in Pega Version 8.4.4
Attempting to open row item details in a repeating dynamic layout in which a data transform was called on click action resulted in the error "Failed to run data transform error ". This has been resolved by adding a null check in Set action.
INC-155214 · Issue 617007
GetBinaryFilesRef updated for resolving wildcard
Resolved in Pega Version 8.4.4
After upgrading from 8.2 to 8.4, errors related to "Unable to serve file java.lang.IllegalArgumentException: Illegal characters detected in the path" appeared numerous times during full syncs, either on first time login or after cache clear. This was traced to normalizeRelativePath failing, and was caused by a resource declaration in pzGetBinaryFilesRef that encountered an issue where wilcarded URLs were not automatically resolved while packaging Static resources. This has been resolved.
INC-155971 · Issue 616031
Handling added for missing data transform in offline mode
Resolved in Pega Version 8.4.4
A "data synchronization failed" error appeared when trying to login to a Mobile App that had offline mode enabled. The login worked when offline mode was not enabled. Investigation showed that when the pyDataTransformWhitelistForOffline application rule contained an entry for a data transform that did not exist, DataTransformPackager.canProcess() was throwing a null pointer error trying to access it. This has been resolved by adding a null check.
INC-156211 · Issue 620192
Verbose comments removed from wrapper
Resolved in Pega Version 8.4.4
Comments with references to external links have been removed from some harness wrappers.
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-143036 · Issue 599191
SurveyPage loads when ruleset is locked
Resolved in Pega Version 8.3.6
When the ruleset containing the survey rules was locked D_pzSurveyPage did not load and errors were generated. Investigation showed that if the flow was in a locked version, the PopulateShapeNodesFromFlowData activity did not call EvaluateConnectorState, causing the mapping of the transitions for connectors to fail in the activity MapBranchShapeConnectors. This has been resolved.