tlolkus's account

We also have an integrated workflow that deals with required attachments where a package is put in the Ready to Review status once documents are signed.  We are using the Callbacks as our primary source of event updates from OneSpan so when the TRANSACTION_READY_FOR_COMPLETION callback is received we will facilitate the package review in our system before completing it.  In addition to utilizing the callbacks, we have also implemented a polling service that can run to pick up any package updates in the event the callbacks fail because as you know there is no recovery option for failed/missed callbacks.  The question I have is how can we tell from the package data, that it is ready to review?   From what we can see when we check the package status is still in the Sent status.  We are using the .Net SDK (not REST apis) to integrate with OneSpan.  Is there any flag or other field we can go off of in order to indicate it is ready to review or do we need to inspect the package details to infer this.  For example on Sent packages do we also need to check for an Autocomplete flag equal to false and then check to see if all Documents are signed, or if all signers have signed?  Looking for some guidance.  Thanks!

We are an on Prem installation and I was wondering if there is a way in the Back Office to set Visibility=SENDER for all packages we are creating through our integration.  I believe there is a way to do this in code using .withVisibility(Visibility.SENDER) but it would be nice to disable via the Back Office.  If that is available can you let me know what Resource I can update (Feature or Package I would assume) and what the JSON looks like?  We would like to hide the Sharing Layouts feature.  

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.

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

Duo,  Thank you for the above information as this is very helpful.  I too am surprised that when a recipient submits a failed KBA attempt that the call back is not triggered.  Would it be possible to submit an enhancement request for this?