New Signer Experience Settings

Hi Ryan,

Happy new year! And for your two questions:

(1)automatically expand documents tab, it's a package setting

“settings” > “ceremony” > “leftMenuExpand” : true/false

which you can specify at package level or contact support and specify at account level.

I have a blog describing this change since release 11.37(https://www.onespan.com/blog/onespan-sign-release-1137-person-page-configuration)

(2)for in-person or notary signing scenario:

https://www.onespan.com/blog/onespan-sign-release-1137-person-page-configuration

for normal signing scenarios:
https://www.onespan.com/blog/new-signer-experience-thank-you-summary-page-part-1

These are three separate account level settings, which all have to set via support team.

Duo 

Duo,

I added the leftMenuExpand option and that did the trick. I appreciate that.

As far as the download documents go, we are already hiding that feature. I'm talking more about the Review Document button. Is there a way to hide that button?

Ryan,

You can choose to show or hide all six components above and customize their contents by sending a request to our support team or complete the Branding Migration forms to change them. Above screenshot is when normal scenario, there are additionally two separate settings to customize the thank you summary page for in-person and notary signings.

Duo

Duo,

While testing the notary signing experience I noticed there is no way to change the user like in the old signing experience. Is this a control we have to turn on as well in the package configuration?

Duo,

I've figured out the issue with not being able to switch signers. Apparently, we needed to update the url that we using for the new signer experience. I am now, however, having issues getting this signing url to work in an iFrame. If I use the original signing url, it works fine. When I use the new one that works and allows us to switch signers, it doesn't work. When I open up the developer console and look at the issue we are getting the "X-Frame-Options: deny". 

Any idea on how to get around this? If we use the same link and open it up outside of our application, it works fine, just not in our normal iFrame. I hate to ask but is there an account setting that needs to be turned on to allow iFrames?

Lastly, I am seeing the Owner of the package being shown on the list of signers. I know in the old system we were able to hide that via a package setting. Is there a new setting that we need to pass to accomplish this as we are using almost all of the old package settings currently when creating a package for the new signing experience.

Hi Ryan,

Try with this format:

https://sandbox.esignlive.com/auth?authenticationToken=MjU1NTA2ZmUtZWVkMy00YTkyLWI2YzktMDMzNWYzMmE1MTAx&target=https%3A%2F%2Fsandbox.esignlive.com%2Ftransaction%2F4x0n51M422VslLe3NaLyj6SmbCQ%3D%2Fsign%3Fiframe%3Dtrue%26loggedInUser%3Dmyusername%2540gmail.com

where the encoded URL looks like:

https://sandbox.esignlive.com/transaction/4x0n51M422VslLe3NaLyj6SmbCQ=/sign?iframe=true&loggedInUser=myusername%40gmail.com

Seems still working at my end.

Duo

Duo,

Thank you! That did work. 

The last question we have about this is the one about hiding the owner in the list of signers. Since the owner will never be a signer, how do we hide this? In the old experience we were using a package level setting. How do we accomplish this in the new signing experience?

Hi Ryan,

I think we've brought this to R&D few months back, and looks like this still hasn't been implemented. I can raise another ER for you and ask for updates.

Duo

Duo,

Upon further testing I am still not able to get this to work in an iframe. I've noticed that for the notary signing experience, it has to be in this format for it to work.

"https://sandbox.esignlive.com/a/transaction/4x0n51M422VslLe3NaLyj6SmbCQ=/sign?iframe=true"

Notice the /a/ right after the esignlive.com portion of the url. When I don't use that, it takes me to the package but doesn't allow me to sign it or switch users.

Hi Ryan,

 

I think we've brought this to R&D few months back, and looks like this still hasn't been implemented. I can raise another ER for you and ask for updates.

 

Duo

Duo,

I am circling back around on this to see if any progress has been made on this. Has R&D gotten back to you guys on the implementation of removing/hiding the owner from the signers list?

Hi Ryan,

It was internally confirmed that "hidePackageOwnerInPerson" only works for in-person transactions in new signer experience, hence we have to submit an Enhancement Request instead. The reference number of the request is: OSSSAAS-I-1224. It's still not on the roadmap yet and I will let you know as long as there's any updates.

Duo