某些 Creative Cloud 应用程序、服务和功能在中国不可用。
A signable web form can be created to embed on your website (or send as a web link), allowing multiple people to easily access your form or document and create an agreement.
A web form can be configured to have one or more participants, multiple counter-signers, and multiple CC'd parties as well. The signature flow for a web form is:
- An agreement is created once the first participant completes and verifies their signature/action
- If the web form allows for multiple participants, all partricipants will complete their action on the agreement in the order they are listed
- After the participants have completed their actions, the counter-signers are notified in the order they are listed
- Once the agreement is completed, all parties (including CCs) are notified of the completed agreement
-
Configure the experience for the first participant:
(The first participant is the person that initially interacts with the web form. In the case where multiple participants are allowed, the first participant supplies the email addresses for all subsequent participants.)
- Participant Role:
- Signer - Signers must apply a signature in addition to any other fields that are required
- Approver - Approvers can fill fields, but are not required to apply a signature
- Acceptor - Acceptors, like Approvers, can fill field content but are not obligated to provide a signature
- Form Filler - Form Fillers can only fill fields, and may not have a signature field applied to them
- Authentication:
- None - This option uses only the email verification after the web form is submitted (If configured to do so)
- Password - The password option requires that the recipient enter a password before they can view the document
- Knowledge-based Authentication (KBA) - KBA can be enabled as an authentication method if your account is configured to allow unlimited KBA transactions. Keep in mind that KBA is only valid in the United States
- None - This option uses only the email verification after the web form is submitted (If configured to do so)
Note:
Adobe Sign Authentication and Government ID are not supported for web form authentication.
- Participant Role:
-
(Optional) Add Participant
Clicking the Add Participant link adds an additional participant to the web form.
- Additional participants are defined by the first participant who will supply all email addresses for the subsequent participants
- Instructions can be provided via the template to guide the first participant
- Instructions can be provided via the template to guide the first participant
- Additional participants can be optional or required
- Add Participant - The Add Participant link allows for the addition of one or more subsequent participants (Participant 2, Participant 3, and so on) that are to be defined by the first participant
- Clicking the link adds another Participant line to the page
- Additional Participant can be optional or required
- If optional, Participant 1 is requested to assign the next participant. If no new participant is identified, the signature flow moves to the counter-signers (if any)
- If required, Participant 1 is required to provide a name and email address for Participant 2 to progress the agreement. If they do not, the agreement stalls at this point
- Participant 2 is configured the same as Participant 1
- Participant 2 has two additional roles that can be assigned: Certified Recipient and Delegator
- Participant 2 has two additional roles that can be assigned: Certified Recipient and Delegator
When Participant 1 has completed their required actions and clicks Submit, they are prompted to Assign the next participant:
- Participant 1 is requested to provide the name and email address of Participant 2
- Adding Participant 2 then allows for the option to add Participant 3 and so on...
- Adding Participant 2 then allows for the option to add Participant 3 and so on...
- If Participant 2 is included, Participant 1 must first verify their email address before the system notifies Participant 2
- Disabling Require Signer to verify their email address does not circumvent this verification
- Disabling Require Signer to verify their email address does not circumvent this verification
- Additional participants are defined by the first participant who will supply all email addresses for the subsequent participants
-
If you want your web form to be counter-signed:
- Enter the email addresses of the parties you want to counter-sign or approve the agreement under the Counter-Signers section:
- You can include yourself (the creator of the web form) by clicking the Add Me link on the right
- Configure the appropriate Role for each recipient. All roles enabled by the admin will be available
- Define the correct authentication method for each counter-signer
- All defined counter-signers need to complete their signature/approval in the order you list them for the agreement to complete
Note:
Keep in mind, the counter-signers will always be the final signers. The process always starts with the individual who visits the web form.
- Enter the email addresses of the parties you want to counter-sign or approve the agreement under the Counter-Signers section:
-
Drag and drop the files you want to use as a the base for your web form into the Files section, or click Add Files, and navigate to the document on any networked drive or integrated file storage.
Existing Libary templates can also be imported (with authored fields intact).
-
Configure the Options
- Password Protect - If you would like to apply a password to open the final PDF produced by the web form signing, check this box. You will be prompted for the password
- Recipient's Language (Business and Enterprise service levels only) - This setting will dictate the language used for the on-screen instructions, as well as the email notifications related to the web form
To insert values into a web form field, there are two things you need to know:
- How to mark a field as available for URL parameters
- How to construct the URL parameters to be inserted
How to mark a field as available for URL parameters
To make a field available for URL parameters:
In this example we are creating two fields to be filled by the URL:
- Branch_Office - A field that accepts the branch office string (shown above)
- Emp_ID - A field that accepts the employee ID
How to construct the URL parameters to be inserted
An easy way to construct the URL is to:
-
Add your parameters
- The start of the parameters are identified by adding a hash (pound, #) symbol at the end of the web form URL.
- Then add the parameters in the format of {field_name}={value}
Example URL with one parameter
https://secure.na1.echosign.com/public/esignWidget?wid=CBF2s*#Branch_Office=San Jose #621
- Multiple values are added by inserting an ampersand (&) between field values.
Example URL with two parameters
https://secure.na1.echosign.com/public/esignWidget?wid=CBF2s*#Branch_Office=San Jose #621&Emp_ID=429939
Properties and Limitations
- You only use the hash mark once to define the beginning of the paramater(s)
- Using a subsequent hash mark in a value does not negatively impact the result
- Using spaces in values is acceptable
- Using spaces in the field name is only acceptable if you explicitly insert %20 as the space character in the URL
- This will work: https://secure.na1.echosign.com/public/esignWidget?wid=CBF2s*#Branch%20Office=San Jose #621
- This will not work: https://secure.na1.echosign.com/public/esignWidget?wid=CBF2s*#Branch Office=San Jose #621
- It is generally recommend that an underscore be used in field names instead of spaces. It will ultimately save you time
- There is no space allowed between the Field Name, the equals mark, and the beginning of the value (Fieldname=Value)
- No space to either side of the ampersand if you have multiple values
- There is no limit (other than perhaps URL length limits) to the number of fields that can get their value from URL parameters
- Calculated text fields can not be overridden and do not have the checkbox displayed in their field properties.
- URL parameters do not work with authenticated web forms. Due to the use of URL Hash Fragments, if a web form is protected via a password or other authentication, the URL parameters are not passed back to the client after authentication is complete (the server never sees that part of the URL).
Error handling
- Any URL parameter that does not match a form field name exactly is ignored
- Any URL parameter that tries to assign a value to a non-text field or a text field that does not have Default value may come from URL enabled is ignored
Setting the dimensions of a web form requires a bit of knowledge of HTML, but the process is simple. This process allows you to customize how the web form fits on your web page.
Note:
This procedure only applies to the JavaScript code for a web form.
- URL web forms cannot be resized.
By default, a web form's height and width scale with the size of the browser. This dynamic property makes it so the web form can be viewed in most screen resolutions.
To adjust the dimensions of the web form, add a style <div> to the code surrounding your web form. This step is done with HTML, making the widget frame appearance fully customizable.
The code for the web form appears below, as provided by clicking the corresponding get code link on the Manage page:
<script type='text/javascript' language='JavaScript' src='https://secure.echosign.com/public/embeddedWidget?wid=2AAABLblqZhCb3ZNyEbi1ywHYaBw893IPRafJOjVvgE44n4Kb36XRArp5QgTpBhUWhLa7x81ek18*'></script>
To adjust the size, add the following code before the web form code. This code sets the width to 500 pixels and the height to 600 pixels.
The border for the web form frame can also be adjusted by changing the border properties.
<div style="height:500px; width:600px; border:1px solid black;">
The code to put in the website that hosts the web form follows:
<html>
<div style="height:500px; widget:600px; border: 1px solid black;">
<script type='text/javascript' language='JavaScript' src='https://secure.echosign.com/public/embeddedWidget?wid=2AAABLblqZhCb3ZNyEbi1ywHYaBw893IPRafJOjVvgE44n4Kb36XRArp5QgTpBhUWhLa7x81ek18*'>
</script></div></html>
As you can see, the resulting web form is displayed with the stated dimensions.
Obviously, these dimensions aren't ideal, but it shows how setting the height and width values affects the posted web form.
When you disable a web form, it is longer accessible by signers, but is visible in your account. You can re-enable the web form under your authority at any time.
-
Select the experience that you want to provide for any user that attempts to access the web form URL
- Redirect signers to another web page - You can redirect the signers to another web page, like a current version of the web form
- Enter a custom message to signers - You can enter a message that will be displayed in place of the web form
- You can add hyperlinks to the message by enclosing them in brackets [ ]
- You can add labels by using the | (pipe) symbol after the URL
e.g: [https://www.sign.adobe.com/ | Adobe Sign] displays as Adobe Sign.
Disabled web forms can be re-enabled at any time and resume function.
To enable a disabled web form:
If you would like to remove a web form from the Manage page view, you can hide it.
Hiding a web form only hides it on your view, any other users that have access (via share) will still be able to see it.
Business and Enterprise service levels have the option to configure the web form access and signer options.
Web form access and signer options can be enabled or disabled at the account or group level by navigating to Account > Account Settings > Global Settings > Web Forms
Web forms have four optional configurations:
- Allow CCs within Web Forms:
- When enabled, email addresses can be added as CC'd parties to the web form. Otherwise, the option to add CC'd parties is removed from the creation process
- Allow PDF preview of Web Forms:
- When enabled, a PDF link is exposed on the web form, allowing the recipient to view the web form as a PDF
- Be aware that the PDF is a document the recipient can save to their local system
- When enabled, a PDF link is exposed on the web form, allowing the recipient to view the web form as a PDF
- Require an email address in the signature block of Web Forms:
- When enabled, an Email address field is required for each signer within the bounds of the document
- Adobe Sign will automatically place a signature block for any recipient that does not have an email field on the document
- When false, the recipient is prompted to provide an email address on an interstitial page
- When enabled, an Email address field is required for each signer within the bounds of the document
- Require Signer to verify their email address:
- When enabled, the recipient is required to verify their signature before the agreement is completed (Signed)
- When disabled, the recipient does not need to verify their signature, and the agreement progresses to the next recipient or completes
- If an additional recipient is included by the first recipient, then an email verification must be completed before the second recipient is notified (regardless as to this setting)
- Unverified signatures are subject to repudiation
- If an additional recipient is included by the first recipient, then an email verification must be completed before the second recipient is notified (regardless as to this setting)
Caution:
If you disable the email authentication of the signature, and you require a legally binding signature, ensure that you are using some form of authentication that identifies a unique person (eg: KBA, Password).
Yes.
Instruction for disabling the email verification process can be found in the Configuration section.
Caution:
If you disable the email authentication of the signature, and you require a legally binding signature, ensure that you are using some form of authentication that identifies a unique person (eg: KBA, Password).
