SR-B84781 · Issue 337707
Modified RuleFormToolBar for enhanced custom skin use
Resolved in Pega Version 7.4
A delegated decision table was not opening in a custom portal unless the sysadmin role was included in the access group. The root cause is that the custom CSS class 'hidden' is used by the system to hide the section 'pzRuleFormToolBarHotKeys', ensuring a section is generated (HTML generation) in the background but not visible to all users. Since this CSS class 'hidden' is available for out-of-the-box skins only, using a custom skin revealed the hidden class and made the hotkeys section visible. In order to allow the enhanced use of custom skins, the pzRuleFormToolBar has been modified to put a visible 'when' that will not display the hotkeys section if the rule is opened from delegation screen (Portals).
SR-B85062 · Issue 343019
Corrected items missing from filter view
Resolved in Pega Version 7.4
When declare index was added in the report definition and the RD was run and filtered, no records were seen. To correct this, and additional check has been added to ensure the Index information is available from the temporary page (in pzCopyPySource activity ) when clicking on a column for filtering.
SR-B87204 · Issue 338827
Handling added for null value in CaseMatch
Resolved in Pega Version 7.4
The 'Case Match' decision rule was not working as expected when the FirstName had a null value. This has been fixed.
SR-B88055 · Issue 342975
Parts Return process fires more than once when active
Resolved in Pega Version 7.4
The Parts Return process from Repair Order was not invoked for the second time even though the program configured on it was still active. This was traced to an Issue where multiple declare expressions that were fired when submitting the first repair order had an unintended side effect of calculating property values incorrectly, and handling has been added to resolve this.
SR-B88376 · Issue 335739
Logic update for expandAll to ensure consistency in nested structures
Resolved in Pega Version 7.4
Declare expressions were not triggering properly when using a nested tree structure. This was traced to a CME error on the expandAll(true, true) function that led to a declare expression not being fired to incorporate property value changes on the clipboard. To correct this, expandAll() has been modified to expand a stream inside an already expanded page even when the embedded page has not been moved or copied.
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'.