Notify call

Hi Wendy,

Sorry about the confusion, I can experience the same now, I believe this is because the notify event (click the notify button at UI, or invoke the signer notification API) triggers "email.notify" template when package hasn't been completed and triggers "email.complete" template when package has been completed, which has already been disabled at account.

So I am wondering what is the business motivation behind this requirement that you don't want to deliver the completion email until sender triggered the notify button? If it's a review process, you can require the package to be "mark to complete" and the package status won't be changed until sender did so.

Duo

Hi Duo,

Except MarkComplete call to trigger compete email, is there any other API call to trigger a complete email when a package is completed and ready to download?

Thanks

Wendy

Hi Duo,

Hi Duo,

The business motivation is for some package, an complete email should be send to signer when the package is completed, for some case, an complete email should not send to signer. That is why we want to disable complete email and only send compete email by explicitly call a API.  Except MarkComplete call to trigger compete email, is there any other API call to trigger a complete email when a package is completed and ready to download? 

Thanks

Wendy

Hi Duo,

The business motivation is for some package, an complete email should be send to signer when the package is completed, for some case, an complete email should not send to signer. If OneSpan don't have a API call to trigger sending complete email except makeComplete. Could you create an ER for it?

Thanks

Wendy

Hi Wendy,

Unfortunately, there's only one Signer Notify API, which is to trigger the email.notify, not the email.complete. I've raised an ER to the support team on your behalf mentioned the request and the business motivation.

Duo