SR-C691 · Issue 349064
VBD reworked to retrieve IH DB metadata
Resolved in Pega Version 7.4
Campaign dashboard performance was slow when accessed via the Navigation bar button PRPC user configured for app server has restricted access to schema metadata. This causes VBD to be unable to build SQL query used to synchronize Actuals data set with Interaction History. It was possible to optionally configure vbd/useTableMapping = true in PR Config or DSS (owning RS: Pega-DecisionEngine) in order to force VBD to load IH database column metadata using Pega table info mapping instead of using database connection API, but the issue has now been fixed by reworking VBD to use Pega class/database mapping rules instead of JDBC DatabaseMetadata to retrieve IH fact/dim table columns.
SR-C8023 · Issue 350229
Updated dataflow used after pause/continue
Resolved in Pega Version 7.4
When using an event dataflow that has a Kafka dataset as the source, running the flow, pausing it, and importing updated rules was resulting in the resumed flow still using the old rules. This was a known limitation in the data flow metrics management where when a run was resumed, the previous metrics were "merged" with new metrics. In cases where the structure of a data flow changed between pause/resume, merge failed silently and new metrics were not saved to the database. The metric management has now been updated to merge metrics correctly: in case of a data flow structure update (e.g. shapes added/removed), after the data flow is run, stage metrics will be cleared up as it is not possible to match them with the new structure, and all other metrics will be properly resumed from the "paused" position (e.g. number of processed records, throughput etc.).
SR-B50830 · Issue 318366
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-B64752 · Issue 327010
MapValue null value handling added
Resolved in Pega Version 7.4
The exception "clipboard.InvalidReferenceException: The reference * is not valid. Reason: invalid property name: '*'" was being logged sporadically. This exception was thrown when the MapNametoTitle Map Value tried to map the first row as @replaceAll(.pyWorkParty(param.WorkPartySubscript).pyFirstName, "a", "o") and param.WorkPartySubscript was null. The "*" appeared due to a wild card inserted by the system when the value is null. Handling has been added for the null value, and the error message has been updated to be more informative.
SR-B74504 · Issue 328594
ValidateTargetURL now more flexible for port number length
Resolved in Pega Version 7.4
After configuring the system name, clicking "Migrate" in the migration wizard generated the error "Invalid URL". This was due to the validation of "pxValidateTargetURL" encountering an unexpected 5-digit port number in the URL. The regex validation rule has now been made less restrictive when checking the URL generated using the system name.
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.