kamranwali | Posts: 27

Error when Multiple Signers With Same Email

0 votes

Hi,

I am getting below error when I am trying to notify signer.

{"messageKey":"error.validation.notifySigner.outOfOrder","code":400,"message":"Unable to notify the signer until it is their turn to participate.","name":"Validation Error"}

package id: UUEAxeNG2AmU5hLxXlN7HbL0ZH0=

Both signers have same email addresses with different custom ids.

It used to work fine when we had "email.activate" template active, but now we have disable it and notify users manually.

I raised a ticket 

https://community.onespan.com/forum/change-package-expiry-without-sending-email

why we disable "email.activate" template

We are using the second option

"(2)You can contact support team and disable the "email.activate" template entirely. Instead, you'd call below method to manually send invitation to signers. It uses a different email template "email.notify":
eslClient.PackageService.NotifySigner(packageId, "[email protected]", "HELLO SIGNER");""

 

Please suggest what we can do to have email.activate" template disabled and notify signers if they share the same email address.

please note It works fine when we have signers with different email addresses.

 

Thanks,

Kamran

 

 

 

 


Duo_Liang | Posts: 3776

Reply to: Error when Multiple Signers With Same Email

0 votes

Hi Kamran,

 

Thanks for your post! If you have multiple signers sharing the same email, this SDK function won't be able to distinguish them. You may consider to implement another API via RESTful code:
POST /api/packages/{packageId}/roles/{rolesId/CustomId}/notifications

This API is able to uniquely identify the signers by custom ID.

 

Duo


kamranwali | Posts: 27

Reply to: Error when Multiple Signers With Same Email

0 votes

Hi Duo,

None of the Notification api accepts customerId.

I have attached a screen shot of API page.

 

Thanks,

Kamran

 

 


Attachments
Duo_Liang | Posts: 3776

Reply to: Error when Multiple Signers With Same Email

0 votes

Hi Kamran,

 

The custom ID in SDK defines both the role ID and signer ID. Thus every occurrence of role ID or signer ID, you can use custom ID instead.

 

Duo


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off