irsragu

Extra long text truncated in Esign stamp - need to retain the whole text

0 votes

Hi,

 

We have a scenario where there is extra long names and the Esign stamp is truncating those at about 70 characters. We need to retain the whole text for legal purposes. Is there a solution or work around that we can implement?

 

Thanks.


Reply to: Extra long text truncated in Esign stamp - need to retain the whole text

0 votes

Hi irsragu,

 

From my own test, for an OSS recipient, the length limitation for first and last name is 64 characters. As long as the fist/last name is stored at package metadata, they should be able to fully rendered in the e-signature stamp. See below screenshot:

5-22-1

 

So here are my few questions:

(1)Is the signer's first/last name has length around 70 chars or the full name?

(2)If first/last name exceed 64 limitation, can you pass in the signer information when package creation?

(3)Any possible to share a package ID so that I can check with support team?

 

Duo

 

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Reply to: Extra long text truncated in Esign stamp - need to retain the whole text

0 votes

Hi,

 

Here is a package ID. We are actually using the GOV sandbox - signer-sandbox-gov.esignlive.com.

 

Please view this package ID: B6_yc7rzmZMyr5zxcOx0Dg6S4SQ= 

 

payload used:

 

{
    "roles": [
        {
            "id": "SignerA",
            "signers": [
                {
                    "email": "[email protected]",
                    "firstName": "first",
                    "lastName": "ABCDEFGHIJKLMNOPQRSTUVWXYZ----ABCDEFGHIJKLMNOPQRSTUVWXYZ###ABCDEFGHIJKLMNOPQRSTUVWXYZ",
                    "company": "AFS"
                }
            ]
        }
    ],
    "documents": [
        {
            "approvals": [
                {
                    "role": "SignerA",
                    "fields": [
                        {
                            "page": 3,
                            "subtype": "FULLNAME",
                            "type": "SIGNATURE",
                            "extract": false,
                            "extractAnchor": {
                                "text": "Signature",
                                "index": 0,
                                "width": 500,
                                "height": 40,
                                "anchorPoint": "BOTTOMRIGHT",
                                "characterIndex": 3,
                                "leftOffset": -50,
                                "topOffset": 5
                            }
                        }
                    ]
                }
            ],
            "name": "Contract"
        }
    ],
    "name": "Example Package",
    "type": "PACKAGE",
    "language": "en",
    "emailMessage": " ",
    "description": "N",
    "autocomplete": true,
    "status": "SENT"
}
 


Reply to: Extra long text truncated in Esign stamp - need to retain the whole text

0 votes

Also please look at this package ID: ZvRvmNPljjrHUaaeoeLgtHoWb7E=


Reply to: Extra long text truncated in Esign stamp - need to retain the whole text

0 votes

Also is use of Custom fields a solution? We tried to use it, but the Custom fields did not work as intended in the first place.


Reply to: Extra long text truncated in Esign stamp - need to retain the whole text

0 votes

just to confirm - we are passing the signer info while creating the package and it is still truncating.


Reply to: Extra long text truncated in Esign stamp - need to retain the whole text

0 votes

Hi irsragu,

 

I've checked your package in the backoffice, the first name has been truncated to 64 chars in the package metadata ever since uploaded, and in turn, every where reference the signer name (E-signature stamp, Signer Name field, etc) will be truncated as well. So it backs my assumption that it is the system's length limitation for signer's first/last name that caused this issue.

 

Duo

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Reply to: Extra long text truncated in Esign stamp - need to retain the whole text

0 votes

Hi irsragu,

 

If you just want to put the text to the contract, you have many ways to do so like using the text injection to stamp the value when document upload or use a label or custom field. But the issue is, the uploaded signer name will still be truncated, so it may be a concern to you.

I can create a support ticket on your behalf and report our findings to R&D team to see if there's easy way to solve the issue.

 

Duo

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Reply to:

0 votes

Hi Duo,

 

Can you please create that support ticket for us? 

 

We tried using the custom Field, but that did not work as expected. The Custom field pops up, but the value does not show up nor the the value is shown in the document.

 

Can you please also elaborate and possibly give us a code snippet of how to inject the text. We want to present all the alternatives to this issue.

 

Thanks.

Srini.

 

 


Reply to: Extra long text truncated in Esign stamp - need to retain the whole text

0 votes

Hi Srini,

 

For custom field, it's only for senders (versus normal signer), as supplementary information for the sender profile, senders need to input the values from their sender portal. Although it may not be the solution for you, I have a blog here for your reference.

 

To inject the text, you can either use field injection feature (guide here), or use a label field with values, the value will populate after signer signed.

 

Duo

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Reply to: Extra long text truncated in Esign stamp - need to retain the whole text

0 votes

Hi Srini,

 

Based on the discussion we have today, below steps showcase you a workaround which involves label field to display the POA information:
(1)contact support team([email protected]) to have your e-signature stamp ("E-SIGNED by $signer_name;") and the signing date field ("yyyy-MM-dd HH:mm:ss z") formatted

(2)create a test package with the attached PDF and the JSON payload. (All offset positions have been preciously adjusted )

(3)during signing, this is how signer will see, with New Signer Experience:

6-5-1

(4)And this is how it looks like in the signed PDF:

6-5-2

 

 

Duo

 

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off