INC-162881 · Issue 636993
Decision Table check-in warnings supported for large tables
Resolved in Pega Version 8.5.4
After adding an empty row in the middle of Decision Table rows and checking in, the Decision table rule's CheckIn form shows a functionality warning about a conflict in decision table ("This rule contains 1 logic conflict(s). Click the 'Show Conflicts' button for more details."). However, this behavior did not occur as expected if the decision table had more than 500 cells in it, and has now been resolved.
INC-163970 · Issue 636137
Expression Builder updated for special character handling
Resolved in Pega Version 8.5.4
If a modulo operator (%) was used in expression builder, the expression showed the correct value when it was submitted (closed) but on reopen the expression was changed and not calculated correctly. If the expression was not reopened then it calculated the value properly. This issue was traced to a server call to pzEvaluatePegaExpression which treated certain values as containing special characters, and has been resolved by updating the handling for this scenario.
INC-164002 · Issue 639913
Decision table null input handling updated for backward compatibility
Resolved in Pega Version 8.5.4
After upgrade, any null values as inputs in the decision tables were skipped if "Allow Missing properties" was not checked. This behavior was different from previous versions. In order to improve backward compatibility, the new function pxEvaluateDecisionTable has been added which has an additional parameter to set AllowMissingProperties, and the older function logic has been modified to take the parameter value from the parameter page.
INC-164171 · Issue 635868
Support added for connect-SOAP run in parallel mode
Resolved in Pega Version 8.5.4
When connect-SOAP was configured to use the “run in parallel” mode, application settings derived through a datapage had incorrect values. While running the connect-SOAP through an activity, all the values were derived incorrectly. This has been resolved by adding a synchronization enhancement to support parallel run connect.SOAP.
INC-164944 · Issue 636292
Logic updated to handle decision trees over 64k
Resolved in Pega Version 8.5.4
Logic updated to handle decision trees over 64kAn 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 nPropRowLimit is based on the number of columns.
INC-168094 · Issue 642627
Security updated for help URL infrastructure
Resolved in Pega Version 8.5.4
Cross site scripting protections have been added to the help URL infrastructure.
SR-D63307 · Issue 542771
Unneeded class name filter removed from GetRelevantPropertiesForDataType
Resolved in Pega Version 8.4.1
Given one class with a set of properties and another class inherited from the first class containing a relevant records set for class 2, then a new harness did not show the base class fields. Investigation showed that the fields present in the parent class and marked relevant in the case were not being fetched due to pzGetRelevantPropertiesForDataType having a class name filter along with filter by rule resolution. To resolve this, the class name filter has been removed as it is not required due to the report already filtering by rule resolution and relevant class through a join.
SR-D71475 · Issue 538722
Check added to apply values of newAssignPage.pxFormName
Resolved in Pega Version 8.4.1
After upgrade, trying to open existing assignments resulted in a different harness being opened. This was traced to changes in how the property newAssignPage.pxFormName was used, and has been resolved by checking whether the harnesspurpose is dynamic before setting the pxFormName. If formname is already present, the system will proceed with picking the harness from the shape.
SR-D72141 · Issue 542664
Approved flow rule image unlocked
Resolved in Pega Version 8.4.1
When the Approval Required check box was enabled for rulesets (i.e another person with access to this work queue should approve changes to the rules), a rule which was approved was unlocked and moved back to the original ruleset as expected, but the binary image associated with the flow rule remained locked and any other user other than the one who previously checked in the rule was denied access with a "check out failed" error. This locking error has been resolved by modifying the Rule-Obj-Flow!CleanUp activity to set Param.IgnoreInstanceLockedBy = true.
SR-D90544 · Issue 550808
Corrected row focus for deleting in App Studio case model
Resolved in Pega Version 8.4.1
When attempting to delete a row of properties from the 2nd page of the data model of a case type while using App Studio, clicking on the delete icon brought up a dialog box asking for confirmation for deletion but at the same time the screen went back to the first page of the data model instead of remaining on the second page. Because of this, clicking on the OK button to confirm the deletion caused a random property from the first page to be deleted instead of the targeted row of the second page as expected. This was due to the refresh being triggered immediately within overlay UI actions, and has been resolved by updating the first trash icon action set for the section pzExpressFieldActions to be a modal instead of an overlay when launching local action.