SR-B56835 · Issue 312521
Checked in SLA values updated by delegated use
Resolved in Pega Version 7.3.1
Once checked in to the application, the SLA value was not being properly updated when edited by an delegated operator and instead retained the value given by the Case Manager. This was a clipboard handling issue, and has been fixed.
SR-C1507 · Issue 344564
Existing Kafka topic name used for connection
Resolved in Pega Version 7.4
When running a Kafka dataflow, Pega was using the dataset name instead of the topic name for the topic connection. This has been fixed, along with forcing a capital letter for the first character of the dataset name in order to ensure proper matching.
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-B94216 · Issue 345203
Support added for buttons using simple image
Resolved in Pega Version 7.4
When using a customized Perform Harness set to use images instead of the icons class for Action buttons, performing the flow and closing the dirty Step Section generated a confirmation popup with the work area behind grayed out as expected. However, after pressing Cancel the image on the button was still greyed out even though the work area was not. This was due to the system not enabling the buttons using simple image as a source, and has been fixed by adding code to enabledisable.js to re-set the opacity for the buttons with simple image.
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-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-B65837 · Issue 317187
Handling added for blanks when copying parameter pages
Resolved in Pega Version 7.3.1
After Configuring a Call-Asynch-Activity method step on an activity and refreshing the ruleform, the name of the activity being called in the method was no longer shown. To correct this, a 'when' condition has been added to the pzAddAdditionalMethodParameter activity to handle blank pages when copying parameter pages to pyStepsParamUI pages.
SR-B67171 · Issue 317155
Handling added for blanks when copying parameter pages
Resolved in Pega Version 7.3.1
After Configuring a Call-Asynch-Activity method step on an activity and refreshing the ruleform, the name of the activity being called in the method was no longer shown. To correct this, a 'when' condition has been added to the pzAddAdditionalMethodParameter activity to handle blank pages when copying parameter pages to pyStepsParamUI pages.
SR-B68818 · Issue 318268
Corrected section refresh when target section is not in DOM
Resolved in Pega Version 7.3.1
An empty composite tab was displayed after processing a service case due to a reload section request being triggered for the CPMCompositesContainer section that was included in the first tab of the layout group. To resolve this, the system will ignore a refresh client expression if the target section is not in DOM.
SR-B68818 · Issue 316252
Corrected section refresh when target section is not in DOM
Resolved in Pega Version 7.3.1
An empty composite tab was displayed after processing a service case due to a reload section request being triggered for the CPMCompositesContainer section that was included in the first tab of the layout group. To resolve this, the system will ignore a refresh client expression if the target section is not in DOM.