Signer Order - Auto notification

Hi mattsota,

It turned out that your account has "email.activate" template turned off, that's why no invitation email has been sent out. Please contact our support team ([email protected]) and enable this setting if this isn't what you expected.

Duo

Hi mattsota,

In an expected scenario, OSS system should automatically email the next-in-order signer. Could you share the package ID of that one so that I can check the email history for you?

For "account user always be in signer list", you can hide sender from the signer list if you add a package level attribute when creating your package:

"data": { "senderVisible": false }

Note:
#1. It's just to hide sender from UI, sender will ALWAYS be added to the signer list, which is designed

#2. If you didn't explicitly assign a signature to your sender in package creation JSON, the sender won't be involved in the signing flow, and therefore shouldn't affect the email notification.

Duo

Package with Role Index at 1 and 2: kmzQ6zfln_8xGASeKSMPjzejVCw=

Package with Role Index at 0 and 1: FHZcBUuwETEkVf99pbewWlBgA24=

It was for the second one that I explicitly tested sending an email at Thu 3/17/2022 1:19 PM EST. So if you see that in the logs, that was not automatic, it was me clicking the 'resend' button in the Dashboard.

Thank you for that information. Reading about 'email.activate', it states: 

If a package is configured to use in-order signing, only the first signer will receive an invitation when the package is initially sent. The second and following signers will receive an invitation email when the previous signer has completed their part of the process.

Now, the first Signer is receiving the email notification, and the email looks like it matches the "default template" described in the documentation. Doesn't that mean the 'email.activate' is already working? I'm just confused how Signer1 gets the automatic email, but Signer2 does not. 

Separately, in the near future I will work on customizing the email message. It looks like we can do that with the package via the API, according to the "Customizing Invitation Emails" info. Please clarify if that is true, and how that API works with the 'default template' in 'email.activate'. Thanks.

Hi mattsota,

#1. Most likely the email notification signer 1 received is "email.reminder.signer", which subject and content is similar to email.activate.

#2. What described in "Customizing Invitation Emails" guide can only customize the value of "$PACKAGE_MESSAGE;" variable. In order to modify static content like email subject, body, footer, etc, you will need to modify on the default HTML template and sent the HTML file to support team. 

For more information, you can also refer to my blog series:

https://www.onespan.com/blog/onespan-sign-developers-email-templates-part-1

https://www.onespan.com/blog/onespan-sign-developers-email-templates-part-2

https://www.onespan.com/blog/onespan-sign-developers-email-templates-part-3

Duo

Just to follow up and finalize this, enabling the "email.activate" on our account did indeed solve the issue. After Signer1 signed, then Signer2 automatically received a notification.