SR-B82049 · Issue 341054
pxCoverInsKey set in audit history when childcase created
Resolved in Pega Version 7.4
On adding an audit note during the creation of the child case, the audit history did not contain the reference to the parent case. Eventually, when the case was referenced, the pxCoverInsKey was populated in the history table. This was caused by an ordering error in the logic and the system has been updated to correct it.
SR-B84173 · Issue 333881
Fixed intermittent Bulk Transfer failure
Resolved in Pega Version 7.4
Bulk Transfer action was not working for some cases in a flow which applied to an embedded data class, resulting in nothing showing up when attempting to 'transfer' those cases. This was caused by bulk transfer running the "pyTransferAssignment" flow action on the flow's applies to class (i.e., embedded data class); that flow action calls "pyTransferAssignment" section which is present in "@baseclass" which would run on the top page. In case of bulk transfer, this top page would be the flow's applies-to class, causing failure in cases using "Data-Party" flows. To correct this, the system will call the top page FA for embedded pages.
SR-B85795 · Issue 334278
InstructionsForApproval modified to include customizable field value
Resolved in Pega Version 7.4
Assignment instructions are generated by the data transform rule pzInstructionsForApproval. This DT generates a text that did not include a delimiter before the case label, causing it to appear to be a single sentence that may not be meaningful. In order to enhance clarity, this label has been modified to a field value and made available as an extension point for applications to customize.
SR-B87611 · Issue 341746
Null check added for invoking processassignment
Resolved in Pega Version 7.4
After inputting a surname and postcode on the Customer Service Portal and pressing search, the screen froze. Eventually an activity status error message appeared. This was traced to a unexpectedly null page being used to invoke processassignment, and a check has been added to the re-worked logic to avoid this error.
SR-B89142 · Issue 336394
Duplicate cases issue fixed
Resolved in Pega Version 7.4
Duplicate cases were shown in worker case compensation due to a case-sensitive values check. The 'when' condition has been modified to correct this.
SR-B89155 · Issue 337930
Case stages correctly displayed in Microsoft Internet Explorer
Resolved in Pega Version 7.4
Case stages were not being properly displayed when using Microsoft Internet Explorer. This was due to the UI kit version of the "pxDisplayStages" rule using the Dynamic Layout with inline format, causing the parent div to not be used for width in Microsoft Internet Explorer. This has been fixed.
SR-B89321 · Issue 337392
Display cases in each stage properly refreshing
Resolved in Pega Version 7.4
The report from GetWorkInStage which displays cases in the stage was not refreshed/reloaded when a different stage was clicked. This was due to the report parameters not being considered while opening the report, resulting the system displaying the existing opened report even though it had different filter parameters. The dynamic container (pzpega_ui_dynamiccontainer) - reportDefinition API has now been modified to consider report parameters and reload the report with new parameters as expected.
SR-B92095 · Issue 342336
Resolved exception on added nested case
Resolved in Pega Version 7.4
An exception was being generated when attempting to add a case which had a child case. This was due to a missing check for an empty coveredInskey, and has been fixed.
SR-B92186 · Issue 342002
Removed max for case dependency updating children
Resolved in Pega Version 7.4
If more than 50 child cases existed for a Parent Case, case dependency was only being updated for a maximum of 50 cases. The others remained parked at the same state as before the parent case was updated. This limit has been removed by eliminating pagination from the pzGetChildCases report definition.
SR-B94242 · Issue 341369
Case creation works in Interaction API
Resolved in Pega Version 7.4
It was not possible to create cases in the pyInvokeInteraction Interaction API due to a missing property. This has been corrected.