Account


Earned badges

Achievement: Latest Unlocked

Topic Started

This user has not created any forum posts.

Replies Created

Reply to: Modifying a signer

0 votes
I just wanted to add that in cases where the initial recipients of the package recognizes that somebody else should be signing the documents it is possible to empower them to do so thus decentralizing the burden of making these type of modifications. This feature is called Change signer and is documented here in our online help. HTH

Approved Answer

Reply to: Signing for a spouse - 2 signers, but one session?

1 votes
We understand this would be convenient in certain situations and have considered implementing the so called “spouse signing” feature in the past but decided against putting it on our roadmap so far given how easy it is now a days to create an email address and the security tradeoff involved. Although technically feasible, in its simplest form when no alternate authentication mechanism is used, this would weaken considerably the authentication process and could even raise questions about the validity of the whole e-signature process.

Reply to: Support for non-latin characters

0 votes
Non-latin characters support in form fields, including signature, was actually introduced to on-premise customers in the fall of 2015 and should be available to our cloud customers any day now with the upcoming deployment of the Spring 2016 release. Of course the Signing and Sending user interfaces have been available in a number of languages for some time, however the eSignLive front end Application didn’t support entering and rendering form fields data (including signatures) in non-latin character sets/fonts in both the actual documents and the evidence summary. The product was enhanced to leverage the transaction level language attribute (available programmatically). A transaction flagged as Simplified Chinese for e.g. would ensure that the Document Engine uses the installed default Simplified Chinese font.

Reply to: Add support for non-latin characters

0 votes
Non-latin characters support in form fields, including signature, was actually introduced to on-premise customers in the fall of 2015 and should be available to our cloud customers any day now with the upcoming deployment of the Spring 2016 release. Of course the Signing and Sending user interfaces have been available in a number of languages for some time, however the eSignLive front end Application didn’t support entering and rendering form fields data (including signatures) in non-latin character sets/fonts in both the actual documents and the evidence summary. The product was enhanced to leverage the transaction level language attribute (available programmatically). A transaction flagged as Simplified Chinese for e.g. would ensure that the Document Engine uses the installed default Simplified Chinese font.

Subscriptions

Topics Replies Freshness Views Users
2 7 years 1 month ago 11
Profile picture for user fperrault
Hi, I've tried to fill fields with non-latin characters like łóźćżę, but the result in signed PDF is wrong (see attachment). Is there any way to enable UTF-8 for it?
2 7 years 11 months ago 21
Profile picture for user harishaidary
Profile picture for user fperrault
Years ago, with our initial eSign implementation we noticed a significant drop off when we required a married couple to sign separately.
2 8 years 1 month ago 20
Profile picture for user harishaidary
Profile picture for user fperrault
Sometimes we encounter an issue where we need to change the signer on the package. I know I could resend a package to the new signer, but this would require us to start from the beginning.
3 7 years 11 months ago 132
Profile picture for user fperrault

Code Share

This user has not submitted any code shares.

Subscriptions Release Notes

This user is not subscribed to any release notes.