The Automatic Field Detection feature in the Authoring environment is enabled by default for individual, team, business, and enterprise service plans.
When uploading a new form to the Authoring environment, Adobe Sign automatically evaluates the document, and places candidate fields where landmarks on the page indicate that fields are likely needed.
Candidate fields that are in close proximity to a signature field type are further evaluated to determine if the field types are predictable, and will attempt to place the logical field type (e.g.: Full names, Signature dates, Titles, Companies)
Candidate fields can be accepted as placed, deleted, or converted to other field types by the user.
Field detection is automatic when a document is sent to the Authoring environment. This includes the process for creating a Template, a web form, or during an individual Send event.
○ If candidate fields are identified, an icon is displayed at the top left of the Authoring window with a descriptive text bubble instruction the user to click the icon to place the suggested fields.
○ If no candidate fields are detected, then the icon is not present.
○ Each individual page is evaluated separately, and each has its' own icon to place fields for that discrete page.
Field detection will not happen if the uploaded document already has fields applied to it of any type (Text tags or Acroform fields).
Clicking the candidate field icon places all of the suggested fields for that page.
The user can click the X in the text bubble to remove the bubble without placing the fields.
Once the fields are placed, the text in the bubble changes to instruct the user to review the fields.
Adobe Sign has no ability to understand what the field should be called, so all fields have a generic name applied (e.g.: Custom Field 1).
Further, Adobe Sign has no ability to determine which participant the field should be assigned to. By default, all fields are assigned to "Participant 1".
It is recommended the users first delete any extra fields that were placed incorrectly.
You can select multiple fields by holding down the Shift key, and then using your mouse to click on the form, and draw a box. All fields that touch the described area are selected.
You can then move or delete the group of fields.
Then move or add any fields that were misplaced.
Once the form has only the fields needed, review each field in turn by opening it with a double click.
It is recommended that a meaningful name be applied to each field so that Reports are easier to read, and data-mapping is easier to design.
To rename a field, click the Edit icon next to the field name, and then type in the full name of the field.
If the form only needs to have the first recipient enter all content, then the default Participant 1 role is exactly what you need.
However, if there is a need for the Sender to prefill any fields, or if there are multiple recipients, the Assigned To field should be checked and adjusted as needed.
Another thing to evaluate at the field level is the Field Type.
By default, all placed candidate fields are Text fields. However, they can easily be converted to most of the other common single-line field types:
○ Signature Fields
○ Signer Info Fields
○ Text Fields
Automatically placed fields support all of the normal field options like field validation rules, conditional statements, font appearance tools etc.
Once all of the fields are verified, progress through the other pages of the document, placing and verifying the fields as you go.
When all fields are in place, click Save or Send to complete the Authoring process.
If you are creating a Template, the fields are fully editable from the Manage page.
If you leave the Authoring environment before Saving or Sending, the document can be found on your Manage page in the Draft section, but all field placement is lost.
The Automatic Field Detection feature can be enabled or disabled at the Account and/or Group level by Adobe Sign Support only.
Group level settings are permitted, and will over-ride the Account level values.
Agreements with a total page count over 25 pages will not trigger automatic field detection.