Ensure that Liquid Mode is enabled in the Acrobat Sign Admin menu:
- Navigate to Send Settings > Liquid Mode
- The setting can be modified at the account or group level
- The setting can be modified at the account or group level
What's New
Get Started
Administer
Send, Sign, and Manage Agreements
Advanced Agreement Capabilities and Workflows
Integrate with other products
Acrobat Sign Developer
Support and Troubleshooting
The Liquid Mode signing experience improves the display of your documents based on the recipient's device type, reducing the need to pinch and zoom and easily focus on the fields that need to be filled.
Liquid Mode compliant agreements are generated with two views for the recipient:
The interface allows your recipient to easily switch between the Liquid Mode and traditional PDF views of the document, depending on their preference and captures the same legally binding signatures that you expect.
Liquid Mode compliant agreements are created with a single HTML file as the source content.
There are a few restrictions on the HTML and form field constructs in the uploaded HTML document. Specifically:
As the Liquid Mode view has a very curated experience, CSS specified in the HTML file is ignored (ONLY for the Liquid Mode view) and only the attributes of the supported HTML tags will influence the Liquid Mode view. However, there are no such restrictions for the PDF view. Acrobat Sign uses the full gamut of attributes that are available for the supported tags as well as the CSS specified in the HTML document to generate the PDF view.
Adobe Acrobat Sign text tag notation is used to specify the form fields in the HTML document.
If the Liquid Mode feature is enabled but the Liquid Mode view can not be generated for any reason the agreement is created with the PDF view only.
The confirmation email sent to the sender will list the reasons why the Liquid Mode view could not be generated.
Liquid Mode is currently supported on mobile phone devices, with additional support in development.
Ensure that Liquid Mode is enabled in the Acrobat Sign Admin menu:
Submitting a single HTML file using one of the following means:
To successfully create an agreement with the Liquid Mode view, the HTML document may NOT contain JavaScript constructs.
Only the following tags can be used in the body of the HTML document:
Category |
HTML tags |
Attributes that impact Liquid Mode view |
Restrictions |
Headers |
<h1>, <h2>, <h3>, <h4>, <h5>, <h6> |
NONE |
|
Content Division |
<div> |
align |
|
Break |
<br> |
NONE |
|
Horizontal Rule |
<hr> |
NONE |
|
Paragraph |
<p> |
align |
|
Images |
<img> |
src, alt, height, width |
Please see section "Image Support" |
Inline text |
<b>, <i>, <u>, <s>, <strong>, <em>, <span>, <sub>, <sup> |
NONE |
|
Ordered List |
<ol>, <li> |
value, type, reversed, start |
|
Unordered list |
<ul>, <li> |
value, reversed, start |
|
Hyperlink |
<a> |
href |
URL protocol is restricted to http, https and mailto |
Table |
<table>, <thead>, <tbody>, <tfoot>, <th>, <tr>, <td>, <caption>, <col>, <colgroup> |
NONE |
1.Nested tables are NOT supported 2.Form fields within tables are NOT supported |
Form field label |
<label> |
for |
Please see section “Form Field Labels”. |
Form field grouping |
NONE |
Please see section “Labelling Groups of Fields”. |
|
Images |
<img> |
src, alt, height, width |
The size of the image plus the entire HTML should be less than 400KB. The following formats are supported JPEG, PNG, GIF, BMP, and TIFF. The image source must be a HTTPs URL. |
Form fields need to be specified in the HTML document using Adobe Acrobat Sign text tag notation.
The table below shows sample form fields using Acrobat Sign text tags:
Field |
Sign Text Tags |
Signature Fields (Signature, Initials, Signature Block, Stamp) |
{{Sig_es_:signer1:signature}} |
|
{{Int_es_:signer1:initials}} |
|
{{SigB_es_:signer1:signatureblock}} |
|
{{OSig_es_:signer1:optsignature}} |
|
{{OInt_es_:signer1:optinitials}} |
|
{{SigStamp_es_:signer1:stampimage(25)}} |
{{Cmpy_es_:signer1:company}} |
|
|
{{N_es_:signer2:fullname}} |
|
{{Dte_es_:signer1:date}} |
|
{{Em_es_:signer1:email}} |
{{*Ttl_es_:sender:title}} |
|
{{userstamp_es_:signer1:stamp:repeat}} {{transstamp1_es_:transactionid:repeat}} |
|
{{!price}} {{price_es_:readonly}} |
|
{{address_es_:signer1}} {{*city_es_:signer1}} |
|
{{CB1_es_:checkbox(checked)}} |
|
{{(Red)Color_es_:signer1:label(“Red”)}} {{(Blue)Color_es_:signer1:label(“Blue”)}} {{(Green)Color_es_:signer1:label(“Green”)}} |
|
{{Image1_es_:signer1:inlineimage(4)}} |
|
{{Color_es_:signer1:dropdown(options="Red,Green,B lue”, values=”R,G,B”)}} |
|
{{companywebsite_es_:link(http://www.adobe.com):label(Adobe)}} |
|
{{*DriversLicense_es_:signer1:attachment}} |
|
{{Car_color_es:signer1:tooltip('Choose a color')}} | |
{{digsig1_es_:signer1:digitalsignature}} |
|
{{*Mobile_es_:signer1:phone}} {{d_es_:signer1:num(>0,<60)}} |
|
e.g. {{field_es_:showif(price>60)}} |
|
{{TV_es_:calc([SubTotal]+[Tax])}} |
All Acrobat Sign form field constructs are supported except for the following:
Category |
Unsupported Constructs |
Exceptions |
Digital signature form field |
:digitalsignature will not be supported |
|
Prefill workflows |
:prefill directive will not be supported. |
|
Hyperlink form field |
:page(N) directive will not be supported. :link with protocols other than http, https and mailto. |
:signer1 and :everyone directives will be supported. |
Unnamed form fields |
Unnamed form fields will not be supported. |
Unnamed checkboxes will be supported |
Renamed form fields |
Multiple form fields with same name but different directives will not be supported |
|
Each form field should have an associated label. Although labels are not mandated for every form field, it is highly recommended that form fields have labels.
Specifically, in Liquid Mode:
Form fields can be bound to labels using the HTML <label> tag in one of the following ways:
Labels that cannot be bound with form fields by the above rules will be rendered as an unbound label text.
Additionally, Acrobat Sign text tags support the :label directive for the form fields types:
The Acrobat Sign text tag :label directive and <label> tag can be combined in the following ways:
Form field type |
Role of :label directive |
Role of HTML <label> tag |
File Attachments, Hyperlinks |
Specifies the label displayed inside the form field box. |
<label> tag specifies the label or header for the form field. |
Checkbox, Radio button option |
Specifies the label or header for the form field. |
If the Acrobat Sign text tag :label directive is absent, <label> will take its place for the form field. If both :label and <label> are present, Liquid Mode view will fail to create. Examples:
|
Labels can be specified for checkboxes in the following ways:
Labels can be specified for radio button options in the following ways:
Normally in HTML, the “for” attribute refers to a field id value. Liquid Mode uses the “for” attribute to refer to field names. This can cause ambiguity for cloned form fields -- where there are multiple instances of form fields with the exact same Acrobat Sign text tag directive. In this case, we need to avoid using the “for” attribute and must associate labels by enclosing the text tag inside a <label> element.
For example, the following usage will create cloned form fields with different labels for each of the two instances in mobile reflow view:
If a cloned form field specifies a label using a "for" attribute, the references are ambiguous and cannot be resolved. in this case, a Liquid Mode view will not be created.
For example, the following usage will only create a PDF view:
Labels are associated with a single form field. When we want to associate a label/caption with a group of fields (notably, groups of radio buttons) we encourage the use of fieldset and legend elements. The fieldset is used to group the elements, and the legend is used to provide a caption/label for the group. Similar to label, the benefits in Liquid Mode are:
For Example:
<legend>Choose your favorite primary color</legend>
{{(Red)Color_es_:signer1:label("Red")}}<br/>
{{(Blue)Color_es_:signer1:label("Blue")}}<br/>
{{(Green)Color_es_:signer1:label("Green")}}<br/>
</fieldset>
For most documents, the author won’t want the default rendering of a fieldset.
The bounding box can be removed with this CSS:
fieldset {
border: none;
margin: 0;
padding: 0;
}
Images are supported with the following restrictions:
Liquid Mode does not support the following Acrobat Sign workflows:
An attempt to create a Liquid Mode view in the above workflows results in the creation of an agreement with the PDF view only. The confirmation email sent to the sender lists the reasons why Liquid Mode could not be generated.
If the sender tried to generate an agreement with a Liquid Mode view, but Acrobat Sign could not generate it, the sender is notified in the agreement confirmation email with the specific issues that prevented the creation of the Liquid Mode view. The sender can address the reported issues and attempt to create the agreement with a Liquid Mode view in subsequent attempts.
The reported issues can be grouped into the following categories:
Liquid Mode internal errors occur when the server encounters unexpected error conditions while trying to create the Liquid Mode view.
For the other error categories, you can find details of the reported issues in the following sub-sections:
Form qualities that are prime targets for Liquid Mode creation are: