SR-B75131 · Issue 336171
Added missed use case to Date/datetime formatting
Resolved in Pega Version 7.4
Due to a missed use case, the format type for date/datetime was not sent to the formatter, causing the function Date Format to change on declare expression trigger. This has been corrected by adding formattype in the format tokens of the pzGetControlsFormat RUF along with the added parameter 'formatTypeForFormatting' in the pzFormatControl RUF.
SR-B75373 · Issue 328291
Fixed error when updating change tracking in declare expressions
Resolved in Pega Version 7.4
An error occurred when trying to update the change tracking in a declare expression rule. This was caused by ACR using a reference to an old expression rule cache, and has been corrected by updating the code.
SR-B75383 · Issue 328651
Unit test of decision tree repaired
Resolved in Pega Version 7.4
Unit testing of a decision tree was not working consistently when running the rule from the Actions button (Actions | Run). This was an issue with the timing of page creation, removal, and clipboard use, and the handling has been corrected to ensure consistent behavior.
SR-B78964 · Issue 336274
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-B83070 · Issue 338342
Tree grid alignment fixed
Resolved in Pega Version 7.4
An alignment problem was seen with a Tree grid layout when the Freeze grid header check box from the presentation tab of Tree grid layout was checked. This was due to the system not updating the width of the header in sync with the body cells, and has been fixed.
SR-B83419 · Issue 334589
Tree grid alignment fixed
Resolved in Pega Version 7.4
An alignment problem was seen with a Tree grid layout when the Freeze grid header check box from the presentation tab of Tree grid layout was checked. This was due to the system not updating the width of the header in sync with the body cells, and has been fixed.
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.