SR-B93584 · Issue 340019
Removed unneeded guardrail warning for backwards chaining
Resolved in Pega Version 7.4
If the "whenever used" option was included in declare expressions, an additional guardrail warning appeared. This has been resolved by modifying the activity 'Rule-Declare-Expressions!CheckForWarnings' step2(Java) to not to add the guardrail warning 'pxCalculateWheneverUsed'.
SR-B93784 · Issue 341474
Validate rule can add another under a page
Resolved in Pega Version 7.4
Trying to add a row inside a validation rule by mapping a Page property to call validate was not working. This was due to pyEcho (which is used to hold the function) being validated for empty string even though the property was of page type, and has bene fixed.
SR-B93986 · Issue 340258
Decision tree logic refactored for DetermineNodeCaption
Resolved in Pega Version 7.4
The decision tree DetermineNodeCaption for XML rules was failing due to the ObtainValue RUFs for Decision Tree matching on any string that started with "call " when calling another decision tree. To fix this, the ObtainValue RUF with a Boolean parameter has been updated to use (String starts with "call ") AND (String is at least 6 characters) AND (substring at index 5 is a valid java identifier) to enter the chaining and call another Decision Tree, instead of just (String starts with "call ").
SR-B94324 · Issue 340952
URL accepts qualifier #comment
Resolved in Pega Version 7.4
The URL was not accepting the # comment when using the pxValidateURL validation rule. This has been fixed.
SR-B95229 · Issue 351434
Validation modified for importing DT data exported to Excel
Resolved in Pega Version 7.4
If decision table data was exported to Excel and edited, attempting to import that edited xlsx file generated the error "Incorrect file. Please attach the same .xlsx file that was exported earlier". Importing an unedited version of the file worked as expected. Upon investigation, it was found that extra key words were added when the file was saved in the customer environment, meaning the system should not rely on these keywords to check whether the file is the same or not. To resolve this, the validation clauses have been reworked.
SR-C1622 · Issue 348799
Hidden ruleform column also hidden in Excel
Resolved in Pega Version 7.4
When the "evaluate all rows" option is chosen for decision tables, the "Return" column is hidden on the ruleform but the column still shows up in Excel. In order to prevent confusion, the system has been modified to hide the return column when the 'evaluate all rows' option is set.
SR-C16525 · Issue 356495
CheckDependency improvements
Resolved in Pega Version 7.4
String and character checking have been reworked in order to improve the CheckDependency process for DL files from PegaSupport.
SR-C6156 · Issue 351338
Changed RDE 'when' process to avoid syntax errors
Resolved in Pega Version 7.4
The syntax of the Rule-Declare-Expression was incorrect, enclosing the expression in apostrophe('). There was no change in the functionality, but it was not possible to use 'save as' on the rule and an error was generated. In addition, the function calls syntax was missing the @ symbol before the function. These errors were traced to conditions previously fetched from the HTML form data: instead of parsing the html and retrieving the condition, the system will now check if a pyWhen value is available. If it is present, the system will directly use that to create the UI.
SR-C6156 · Issue 350820
Changed RDE 'when' process to avoid syntax errors
Resolved in Pega Version 7.4
The syntax of the Rule-Declare-Expression was incorrect, enclosing the expression in apostrophe('). There was no change in the functionality, but it was not possible to use 'save as' on the rule and an error was generated. In addition, the function calls syntax was missing the @ symbol before the function. These errors were traced to conditions previously fetched from the HTML form data: instead of parsing the html and retrieving the condition, the system will now check if a pyWhen value is available. If it is present, the system will directly use that to create the UI.
SR-C6899 · Issue 351811
Decision tree correctly evaluates condition
Resolved in Pega Version 7.4
A decision tree was going to the 'otherwise' condition even though satisfying 'if' blocks existed. This was an unintended consequence of another fix related to the handling of brackets, and has been corrected.