New to the Community? Get started by checking out our community guidelines and any news in the Forum World.
A success message is displayed in the iframe once the document is signed. Our client would like to either remove this or customize based on language preferences - can you please advise if this is feasible and what parameters in the rest api or client side that we can use to achieve the same.
We would like to have multiple senders creating and sending transaction. But we want one or more accounts to be able to see all the transaction that are in draft, completed or in-progress for all senders. These user would be used as quality control and audit to ensure all required transaction get created and completed.
Looks like the default is that a sender (even if they are the owner) can only see transaction they created and/or are a signer in.
Hi,
I have some questions regarding about the customized field using sender UI:
1) from the documentation, it seems we have to enable the feature, could you let me know where to enable it in the account level?
2) Currently, I am not sure if it's enabled in my account or not, but from testing result, it seems only apply to the package owner once package owner signed, the value will be automatically populated. is it correct? or it should apply to all the signers if it's enabled in the account?
Hi,
In sandbox, with classic UI, I created the package with 'in person' signing enabled, from desktop, I can see the 'in person' dropdown showed in the signing ceremony, but in mobile device, I don't see the dropdown. is it as expected?
thanks,
Cindy
Hello,
Our integration using the .NET SDK involves showing the designer view in an iframe through our website. This has served us well over the years but recently we have gotten more and more customers reaching out with issues regarding IE 11 and getting an error of "Could not connect apps.e-signlive.com" - usually this is resolved by having them add app.e-signlive.com to the trusted sites in their security settings - however this is becoming increasingly more cumbersome.
Is there something we can do on our end to prevent this from being a regular occurrence?
You moved the location of the personal certificate client and didn't let your users with on-site instances of OneSpan Sign know about the change. As a result, a few of our users were unable to download it and sign documents. Fortunately, we put two and two together and discovered the change in the URL. Couldn't you have redirected the old URL?