Bug Report: Attachment Carry Forward Issue in Approval Workflow

Symptoms

A bug has been identified in the current approval workflow where attachments uploaded by the approver during a rejection scenario are not carried forward to the preparer when the task is rejected.

This issue causes the preparer to miss important attachments and comments added by the approver, disrupting the rework process and potentially causing delays.

Description of the Workflow:

1. Preparer Step: The preparer uploads an attachment (e.g., a file or document) to the task and submits it for approval.
2. Approver Step: The approver reviews the attachment and either accepts the task, ending the process, or rejects it. If rejected, the approver may upload additional attachments (e.g., comments or modified documents) to provide feedback on the task.
3. Preparer Rework Step: When the task is returned to the preparer after rejection, the system should automatically carry forward all attachments, including those added by the approver. However, currently, only the original preparer's attachments are visible, and the approver's attachments are not carried forward.

Workaround

<No workaround is available>

Affected version

<RMF 2024.3>

Resolution

The issue has been acknowledged as a bug and is scheduled to be addressed in a future update.

The expected resolution timeline is in the 2025.1 release.

ROSO-14500.