Error Trying to Edit a Transaction that as a rejected Attachment

Hi Tricia,

From the code snippet you provides, it seems you are trying to update the signer, which I assumed the goal is to reject the attachment. If that's the case, you can have a quick try with below SDK code:

            EslClient eslClient = new EslClient(apiKey, apiUrl);
            DocumentPackage pkg = eslClient.GetPackage(new PackageId("9XQRLxddM9Hmz-giVWUNs3IClok="));
            Signer signer = pkg.GetSigner("[email protected]");
            eslClient.AttachmentRequirementService.RejectAttachment(new PackageId("9XQRLxddM9Hmz-giVWUNs3IClok="), signer, "Driver License", "Expired driver's license");

This is the function signature:

public void RejectAttachment(PackageId packageId, Signer signer, String attachmentName, String senderComment)

Duo

Let me clarify.  In our situation the attachment is already rejected.  The package is edited and we are just trying to update the recipient details.  Here is the exact flow of this use case.  Note that all of these actions are happening in our system where we communicate to OneSpan using the .Net SDK.

1) The transaction is created and sent out.  (1 doc, 1 recipient, 1 attachment required)

2) The transaction is signed and attachment is uploaded.  When this happens the transaction in the 'In Progress' status but it is flagged as Review before Completion.

3) Sender Reviews the Transaction and Rejects the Attachment.  They enters a reason and notify the signer.  The transaction in the 'In Progress' status and it is flagged as Review before Completion with a rejected attachment.

4) The sender then hits 'Edit' on the Transaction.  The package status changes to 'Draft'.  The sender can make some edits but in this case no edits are made.

5) The sender clicks Next to navigate to the designer which we have iframed into our application.  It is at this point that before we render the Designer we first save the transaction details in case there were some editing changes.  It is at this moment that we are using the .Net SDK to update the Signer for this package.  It is at this point we get the error above.  

You can refer to the attachment as I have included screenshots to help explain the scenario.

Thanks Tricia for the detailed explanations, now I understand your use case. And I believe most likely the error is caused because of either "SenderComment" or "Status" are updated by your frontend. (SenderComment and Status will be automatically cleared/updated once signer re-uploaded a new attachment)

I understood why you "save the transaction details" in case the sender updates the KBA/Signer Authentication information/attachment descriptions, etc in edition mode. (You may have known that once a signer has started to sign, you can't update signer information like first/last name or email, but recipient information mentioned above can be edited) However, for attachment update:

(1)you can only update attachment name, description and whether required, and make sure the Id, SenderComment and Status keep the same.

TIP:

Although allowed to update, the attachment name should be unique within a package.

(2)It doesn't allow to exclude/delete an attachment from the attachment list if signer has already uploaded a file to this attachment requirement. (Same limitation as from UI)

(3)IF you allowed the sender to add a new attachment requirement, the attachment Id can't be specified - if it's an existing attachment, Id must be specified. 

Duo

Duo thank you for your guidance.  We were able to figure out the issue.  When updating the signer on the transaction, we needed to set the rejection reason so it didn't appear to be edited.

Thanks,

Tricia