Reviewer/Signer Behaviors & Signing url

Hi D'Metrius Agurs,

 

Do you minding sharing such a package ID so that I can learn better about your scenario?

 

In general:

1.) Does a Reviewer with signature fields lose its ability to see all documents if it has signature fields? 

Not sure if we are talking about the "Reviewer" concept in OneSpan Sign (which means when a signer doesn't have signatures, the signer's responsibility is literally just to review the package), or the concept in your business scenario.

 

2.) Is there a way to generate a unique url for the Reviewer to sign their documentation as well as be able to have all the signers in said package present in the drop down menu when in person signing is selected?

There are two types of signing links in OneSpan Sign, and for an in-person signing scenario, they are working in two different ways exactly like you expected:
#1 Signing URL

Signing Url is the link behind the "Go to Documents" button in the activation email, which leads you to a remote and personal session where signers can sign their signatures individually - a unique url for the Reviewer to sign their documentation

 

#2 a signing link built by signer authentication token

In order to kick off an in-person signing ceremony where signer names are presented in the drop down, you need to first generate a signer authentication token for the reviewer:

POST /api/authenticationTokens/signer/multiUse 

or 

 

POST /api/authenticationTokens/signer/singleUse

with payload

{"value":"","packageId":"{packageId}","signerId":"{signerEmail_or_signerID}"}

Then build below link:

https://sandbox.esignlive.com/access?sessionToken={signerAuthToken}

 

Duo

Hey, 

From your second suggestion I found a solution using the .Net code. We found that we could call the authenticationtokenservice and create a token for our signer in code. 
Here is the snippet below: 
 

 string signerAuthToken = _eslClient.AuthenticationTokenService.CreateSignerAuthenticationToken(new PackageId(result.Item2.PackageId), hostSignerId.Key);
                        signingUrl = $"..../access?sessionToken={signerAuthToken}";

 

thanks for the assistance,

 

D'Metrius Agurs