SR-B89509 · Issue 339155
Localization handling added for multiple messages on the same property
Resolved in Pega Version 7.4
If more than one validation message was set on a single property, localization was not performed. This was due to multiple validation messages being appended into one string and the system failed in looking for a localized message for this appended string. In order to ensure the expected messages are localized, the code has been modified to get the localization for the individual components if it encounters a compound string.
SR-B89780 · Issue 337097
CSV upload to Excel template ruleform fixed
Resolved in Pega Version 7.4
The upload dialog appeared while trying to upload a CSV file using the Excel template ruleform, but clicking the 'Upload' button did not actually transfer the file. The 'Download' button was also not appearing for newly-created files. This was traced to a missed case in recent changes made to the Decision Table and Map Value export/import functionalities, and has been fixed.
SR-B90131 · Issue 339459
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-B92742 · Issue 341398
Fixed property type for indexing
Resolved in Pega Version 7.4
The property type "SelectedSalesAreas" was being found as a date type in index mappings, causing the indexing to fail. This has been fixed by explicitly creating field type mapping as string in the dynamic template.
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.