Adobe Acrobat Sign Authoring - FAQ

Cause

Assign at least one signature field to each recipient if you are assigning them signer role.

Following are the reasons for signature block Auto-generated even if there is a signature field assigned to the signer:

  1. If one or more signatures fields are not set as Required.
  2. If signature fields have Conditions (Show/Hide/Enable/Disable) applied to them.
  3. For Widgets, if you have not applied any Email field on the document.
  4. Also, the account is set up to require Title and/or Company fields.

Resolution

Following are the options to resolve the issue in each scenario:

  1. If the signature field is not set to Required make it a required field.
  2. If there are Conditions in the signature field, either remove the conditions or add one more signature field without conditions.
  3. Add an Email address field to the widget.
  4. If Title and Company are set to required, add the Title or Company field on the document or disable the setting from Signature Preference under Account Settings.

You can fetch the result of templates by running the report and later filtering the Agreement Status as "FORM_PROTOTYPE, FORM_PROTOTYPE_EMBEDDED."

However, it does not show the sharing permission set for each template.

No.

Acrobat Sign text tags do not include directives for Bold, Italic, or Underline.

No.

The user must rotate the page before uploading it into Acrobat Sign.

In Acrobat Sign, the default format for date fields is Month Day Year (mm/dd/yyyy)

You can use the formatting scheme from calculated fields to specify the date field format, for example:

{{date1_es_:signer1:date:format(date, "mmm dd, yyyy")}}

This causes the date field format to appear as: Dec 01, 2018

Alternatively, you can use a calc formula to generate the same format:

{{date_es_:signer1:calc(now()):format(date, "mmm dd, yyyy")}}

Both these fields behave the same and result in the same format being displayed in the date field.

You can use following characters to specify the formatting of an output in the form of a date, time, and AM/PM.

Calculated field variables for dates

After adding (tt), it displays the A.M./P.M. designator.

Following is the example: 

{{DateTime_es_:signer1:calc(now()):format(date,"mmm d,yyyy, hh:nn:ss:tt")}}

Due to functional limitations of CSV documents in an Excel environment, taking credit card information on a form is more complex than it seems at first.

Adobe recommends that if you are collecting credit card information, you design your card input to capture the first 11-12 digits in a masked field, and the last four digits in a separate field that you can elect to mask or not. You can capture credit card numbers this way using any of the form creation methods as described below.


Use the drag-and-drop authoring tool

  1. Set the Field Names to be descriptive of the field.

  2. Set a Tooltip that describes the field content.

  3. Set the field as Required if necessary; it sets the red border around the field

  4. Mask the data; it's highly recommended, but requires that you capture the content of the field using the CSV export of the form data.

    Pastaba:

    Often the last four digits are not masked, so in the second field you see that masking is deselected

  5. Set field validation; it is set as a String for two reasons:

    • If the number starts with a zero, and the validation is Number, the zeros are stripped off.
    • If you want to set a maximum number of characters, use String. Using Number as the validation only allows a range of numbers.
  6. When you set the String validation, you have the option to use Letters, Digits, or both. Credit cards in all cases use only Digits, so constrain the option to just Digits.

  7. Set the Maximum Length of the string

    • For the first field, we set the maximum length to 12. All major credit cards have 15-16 digits in the full number value
    • The second field is only four characters
    Credit card field properties


Add credit card fields using text tags

If you are using Text Tags, you probably want to drop some of the optional features like Tooltip and Default Value, as they extend the footprint of the tag itself and interfere with the layout of the document. And it's likely you will want to resort to Tag shortening anyway for the smaller field. That said, your text tags would look like this:

{{*CCN1_es_:signer1:string(char=num,maxlen=12):mask}}

and

{{*CCN2_es_:signer1:string(char=num,maxlen=4)}}

In the above Tags we have the same common values as in the drag-and-drop environment (as read from left to right):   

  • The pair of curly brackets defines the width of the field on the final document.       
  • The first pair of curly brackets defines the font (height) of the field.   
  • The asterisk (*) is the flag that makes the field required   
  • The name of the field follows (shortened to CCN1 and CCN2 to minimize the footprint of the tag)   
  • The Role (signer1)   
  • The String validation that defines the character type and the maximum length of the string.   
  • The optional Masking of the value

Clearly these field sizes are much too large for the intended content, and in these cases we recommend using Text Tag Shortening which effectively allows you to define a variable value: {{$ccn2}}    with a much larger tag that is referenced on a different page:{{#ccn2=*CCN2_es_:signer1:string(char=num,maxlen=4)}}

See this article for more information on text tags and text tag shortening

By default, signature and initial fields can be placed and configured to fit into a designated space. 

For most customers this is desirable as forms often have unpredictable formats, and getting one "standard" field to fit in all places isn't practical.

However, enterprise customers that want to enforce the default fields size for all signature and initial fields may do so by contacting their success manager and requesting that the resizing of signature fields be disabled.

Default field size

Disabling the resize feature prevents new agreements and templates from allowing signature and initial fields from having their default field size changed in the drag and drop environment.

 

Text tag fields present differently depending on the size of the field that the tag defines:

  • If the text tag is smaller than the default field size, then the default field is rendered during authoring and signing
  • If the text tag is larger than the default size, the size defined by the tag is respected during authoring and signing, but the final signature graphic will only occupy the space of the default field size
    • The common anchor point is the botton-left corner of the tag/field

 

Other things to keep in mind...

  • This setting only applies to signature and initial fields
  • Making a change to this setting only impacts newly sent agreements.  Any agreement in-flight retains the setting value that was in place when the agreement was originally sent
  • Draft agreements haven't been sent yet, so they adopt the new setting value
  • Widgets and Library documents are templates, so they adopt the new setting value. Once an agreement is produced from the template, the value is fixed

The length of the text tags decides the length of the field. There are two methods to decrease the field length: 

  • Decreasing the font of the text tag:
    The first open curly bracket decides the font type and size of the field. You can decrease the font size of the later part of text tag to decrease the field length. 
    For Example, you can change {{Birthday_es_:signer2:isdate(format=dd/mm/yy)}} to

  • Using Text tag Shortening:
    A shortened text tag consists of two parts:

    1. Reference Tag: The reference tag controls the size and location of the actual form field in the document. A reference tag has the following syntax: {{$shortened_name}}.
      For example, {{$r}} defines a reference tag where "r" is the short name of the tag.
    2. Definition Tag: It refers to the complete definition for a specific tag and can be defined anywhere in the document.
      A definition tag has the following syntax: {{#shortened_name=Standard Tag Syntax}}.
      For example, {{#r=[]ReceiveCommunication_es_:signer1}} defines a complete tag definition for the reference tag named "r."
      To learn more about text tag shortening, see Shortening Text Tags.
  • Increasing the font of the text tag:
    The first open curly bracket decides the font type and size of the field.  eg:
Large font text tag

  • ​​​Increasing the length of the text tag field
    The length of the field can be increased by increasing the space before the end brackets. 

eg: {{Birthday_es_:signer2:isdate(format=dd/mm/yy)                                      }}

„Adobe“ logotipas

Prisijunkite prie savo paskyros