SR-B74583 · Issue 325617
SendEmail smart shape fixed to populate PartyRole correctly
Resolved in Pega Version 7.4
Due to issues with populating the pxPartyRole property, emails were not being sent to all members in a repeat party after upgrading. This was traced to a missing call in the modified SendEmail smart shape, and has been fixed.
SR-B75096 · Issue 329151
Bulk actions filter clears previous value
Resolved in Pega Version 7.4
When running Bulk Actions, attempting to delete filter conditions was resetting clipboard values and no results were displayed. This was an unintended consequence of changes that retained pyUserIdentifier on the conditions page even when "Assigned to Operator" was not in the filter list. To correct this, it will be removed when pyUsage is not equal to Operator.
SR-B75096 · Issue 329225
Bulk actions filter clears previous value
Resolved in Pega Version 7.4
When running Bulk Actions, attempting to delete filter conditions was resetting clipboard values and no results were displayed. This was an unintended consequence of changes that retained pyUserIdentifier on the conditions page even when "Assigned to Operator" was not in the filter list. To correct this, it will be removed when pyUsage is not equal to Operator.
SR-B78236 · Issue 332447
Add file correctly saves pxCreateOpName
Resolved in Pega Version 7.4
Attaching a file using the out-of-the-box functionality was not saving the pxCreateOpName in the pc_link_attachment table. Only the pxcreateoperator was saved. This was caused by pxCreateOpName being blank for link-attachment on file attach, and has been fixed by setting pxCreateOpName in the Work-AttachFile activity.
SR-B78236 · Issue 328422
Add file correctly saves pxCreateOpName
Resolved in Pega Version 7.4
Attaching a file using the out-of-the-box functionality was not saving the pxCreateOpName in the pc_link_attachment table. Only the pxcreateoperator was saved. This was caused by pxCreateOpName being blank for link-attachment on file attach, and has been fixed by setting pxCreateOpName in the Work-AttachFile activity.
SR-B79946 · Issue 329632
Removed unnecessary check for duplicate Question AnswerIDs
Resolved in Pega Version 7.4
It was not possible to add a Complex Question into a Question Page when the page already contained another Question with the same AnswerID(s) as the newly added one. This was traced to a call to ValidateAnswerIDofQuestionCollections in the Validate rule of Rule-PegaQ-QuestionGroup, used to check for duplicate answer IDs. Because this code was maintained for backward compatibility and is no longer needed, it has been removed.
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.