Skip to main content
gembry1
gembry1
Inspiring
September 16, 2016
Question

VAR names w/ old syntax "_es_" & colons w/ new syntax

  • September 16, 2016
  • 3 replies
  • 767 views

Here are two generic questions.

I have a few PDF's that are using the old _es_ naming convention with no colons. I need to convert to the new convention and have two issues to resolve.

  1. How can I reference a VAR in the PDF that uses the new syntax?

    My code uses the old reference below and I can't use colons in my variable names. Any thoughts?
    Ex: (old reference works) txtOwnerName_es_signer_signature >> (new reference w/ colons breaks) txtOwnerName_es_:signer:signature

  2. This one pertains to existing _es_ variables that I don't need EchoSign to handle at this point. Will there be any issues if I leave the _es_ reference alone and can I assume that EchoSign will ignore processing those items? If I can leave them alone then I can avoid making more changes on our end.

    Ex: txtOtherVar_es_signer_date --- in this example, I'll handle the date from my side and DO NOT need EchoSign to do anything. Will this cause problems?

If you need more detail I can update as needed.

Thanks.

This topic is closed to new replies. Start a new post to keep the conversation going.

3 replies

gembry1
gembry1Author
Inspiring
September 19, 2016

Disregard Question 1 above. I resolved that issue.

How can I reference a VAR in the PDF that uses the new syntax?

The problem was with the double-quotes and copy&paste. The Left & Right Double Quote mark made an appearance at that point. Once I replaced them with the correct U+0022 Quotation Mark then all worked. A simple syntax issue.

> pdfForm.removeField('txtDate_es_:signer1:calc(now()):format(Date,"mm/dd/yyyy")');

" U+0022 QUOTATION MARK
“ U+201C LEFT DOUBLE QUOTATION MARK
” U+201D RIGHT DOUBLE QUOTATION MARK

R
Rijul Raj Khurana
Inspiring
September 18, 2016

Hello Greg,

The new text tags mentioned are correct and ideally should work however, where exactly are they breaking up while being uploaded and sent using Adobe Sign? Is it possible to share the screenshot and inbox me the original document used so that I can further more check?

-Rijul

gembry1
gembry1Author
Inspiring
September 19, 2016

Hello Rijul,

Nothing is breaking at the moment. If I leave the "old" _es_ syntax as-is with some inputs, will this cause any problems with EchoSign? Will EchoSign bypass processing them if they are not using the "new" syntax? I'm trying to avoid making to many changes.

Ex: txtOtherVar_es_signer_date  <- Will echosign ignore this old syntax?

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices