Michael_S_Smith's account

I would agree controlling the email notifications at the package level is important. For our in-person signing we will control the process completely and the email is unnecessary. For other clients we would like to sent the email. We would like to be able to implement this with a single service. Hoping this enhancement gets on the roadmap.

Actually I see this post is 4 years old - is this now possible?

Sorry to bring this up again, but I was told by legal that we pay for each *created* package rather than each completed package. I dont know if this is really true, but if true, then we need to figure out how to update packages rather than delete them and recreate them. This has turned out to be extremely difficult.

So first - since I dont completely trust the answer I got from legal - are customers charged for package creation or package completion? It would solve a big problem for me if I could simply delete/recreate. Our customer wants to be able to make wholesale changes to packages - change signers, add/remove documents etc. 

Second - while my update code seems to work (the package looks as I would expect), when I make a subsequent call to eslClient.getPackage for that packageId I get the following error:

[403, Forbidden]. Optional details: {"technical":"Cannot access a package that can be edited

So after I do my update, how do I signify the package is no longer editable? Will the system resend the notification emails? I tried to call 'sendPackage' after my updates but I get a similar error.

Thanks

Thanks this was helpful. From your reply I was able to gather in need to invoke a SEND after doing my update operations and my code now works. You are right about getPackage - the problem was actually later in my code due to the fact there was no signingUrl - after the SEND this problem was fixed.

Thanks

Likely something I am doing wrong then. May package is 24dfwzxRo7YGtuDHw8rZ1lhW994=

The package I created did not assign the notary as the sender, but it is coming back that way. The notary I assigned is a sender in my dashboard but was not assigned as the sender on this package.

Is there a way to create a notary that is not a sender?

Ok this is a bit odd. After creating the package, the signingOrder on the notary is zero. After invoking the REST code (taken from here https://community.onespan.com/documentation/onespan-sign/guides/feature-guides/developer/creating-notary-signer), the signingOrder on the notary has been changed to 2. The package I just created is 54v6lmpjdNXifSRiI3WpEE7MMGg=

My code does:

1) create package

2) Invoke the REST code

3) Send package

After step 1 the signing order is 0 and after step 2 it is 2

Additionally I notice even though I send a signerType of 'NOTARY' for this signer, the created package has his signer type set to ACCOUNT_SENDER. I dont know if this is a problem. The user is configured as a sender, but is not the sender of this package.

                        Mike