Log in as an Account Administrator and navigate to: Account > Workflows
The Workflow Designer is used to create workflows that tailor the signing processes to fit your specific business requirements. With this new tool, administrators can design and manage workflow templates easily with an intuitive drag-and-drop editor. It's easy to specify the documents to be included in an agreement; the characteristics of the participants—including predefined names, roles, and routings; form fields to be pre-filled by the sender; emails to be sent to the participants; agreement expiration or password options; and more.
Workflows also create an easy-to-follow send experiences for your users so process steps can be followed consistently every time. Senders using a workflow template are guided through the send process with custom instructions and fields, making the send process easier to use and less prone to errors.
Only administrators can create workflows. Account administrators can create workflows for their entire account or for specific groups within their account. Group administrators will be able to see all workflows but can only edit the ones in their group.
Creating a workflow consists of defining the following information:
Required fields are identified with a red asterisk. Some field labels are editable, as indicated by the
pencil icon, for example, Agreement Name:
Click the pencil icon to enter a custom label. This label will display on the Send page when the workflow is used to send a document. To revert back to the original label, click the revert icon.
Explicitly defined custom workflow settings will override the default group or account level settings (if configured).
Log in as an Account Administrator and navigate to: Account > Workflows
Click the Create a New Workflow button to open the Workflow Designer.
The Workflow Designer opens and the Workflow Info panel displays:
In the Workflow Designer banner, the default name of the workflow displays (e.g., New Workflow).
The dot next to the workflow name indicates whether the workflow is draft/inactive (grey dot) or active
The following controls are located to the right:
In the Workflow Info page, enter the following information:
Instructions can be added using HTML tags. The following html tags and their attributes can be used in the instructions section: <p>, <br>, <b>, <i>, <u>, <ul>, <ol>, <li>, <img src=”fully qualified path”>, and <a href=”fully qualified path”>.
If you intend to use src or href paths, you will need to have the paths whitelisted. Please send the URLs to your Customer Success Manager
Below is an example of Workflow Info:
Click Agreement Info in the left rail
2. In the Agreement Info section, define the agreement information as it should display on the Send page for the sender:
Below is an example of Agreement Info:
Click Recipients in the left rail to access the Recipients Routing section
In the Recipients Routing section, you can specify the recipients and the routing order per your requirements. You can build very complex workflows with serial, parallel, hybrid, or nested hybrid routing. The following instructions highlight the functionality available for Recipient Routings.
When editing a Recipient, you can configure the following:
Enabling the password as identity verification will add the same password to the Document Security, preventing viewing the PDF until the password is entered.
Be sure to click Save to save any recipient configurations made.
Below is an example of Recipients information and a routing where the labels for both signers (Buyer and Sales Director) and for the approver (VP Sales) have been customized.
Click Emails in the left rail to move to the Emails section
Check the boxes for the events you want to trigger an email notification
Click Documents on the left rail to move to the Documents section
In the Documents section you can configure the following
Below is an example of a configured Documents section:
Click Sender Input Fields on the left rail to access the Sender Input Fields section.
These input fields are mapped to form fields defined in the documents that are attached (either as part of the workflow design, or as a sender uploaded file).
The sender can use these fields to prefill content prior to sending the agreement to the recipient.
In the Sender Input Fields panel, click Add Field
Then for each row added, you can configure the following:
Below is an example of Sender Input Fields:
Sending an agreement with a workflow starts on the Home page by selecting the Start from library button and then selecting the workflow you want to use.
Once you select a workflow, a modified Send page displays, showing the customized recipient order, any custom instructions, attached files, and so forth.
1. From the Home page:
The Send page displays:
In the example Send page shown above, the following customizations display:
A. From the Workflow Info section:
○ The Workflow Name (GlobalCorp Service Contract <50K) at the top
○ Instructions for the Sender (This workflow is used for contracts under 50K...)
B. From the Agreement Info section:
○ Custom Agreement Name (GlobalCorp Service Contract for 2018)
○ The Message (Please find attached the service contract...)
○ Password protect the signed document (Permitted but not defined)
C. From the Recipients section:
○ The custom labels for the recipients (Signer and Counter Signer) and for the certified recipients (Legal team) display
○ The email addresses is hidden when the sender is one of the signers, listing "Myself" instead
○ The email addresses for the recipient group (Legal team). The recipient group can either be left empty for the sender to populate, or preconfigured in the workflow template.
D. From the Documents section:
○ The name of the pre-attached contract (Service Contract) displays in the Documents area
○ The name of the file that the sender must upload, the Referral Document, also displays
E. From the Sender Input Fields section:
○ The fields defined display in the Fields area
○ The default value is imported, but editable
2. Complete the fields that are required by your workflow.
In the example above, that would be:
3. Click Send.
4. Optionally, in the authoring environment, make modifications of fields as required, then click Send
Custom workflows do not support a Written signature type.
If an agreement is created via the REST API with signatureType=Written, the agreement is still created and sent for Electronic signature.
The workflow agreement is sent out in the order specified in the routing. The signers and approvers can sign using the link in the Please sign/Please approve email or from their Manage pages if they are registered Acrobat Sign users. This works the same way as the standard send process.
The history and audit report for the workflow agreement can be accessed from the Manage page. While the agreement is in process, you can add reminders and perform other tasks.
Log in as an Account Administrator and navigate to: Account > Workflows
In the Workflows list, click to select a workflow
In the context menu, click Open. The Workflow Designer displays
Once the Workflow Designer is open, the workflow is fully editable. All sections can be changed as needed, and no changes will be saved until the Update button is clicked.
In the Workflow Designer, you can make the following changes:
Custom workflows have had significant improvements added, which are gated by controls in the admin menu.
Customers that want to enable workflows are encouraged to enable the first three options below to get the best experience for their users and recipients.
To even have the option to configure workflows, the feature has to be enabled.
Navigate to Account Settings > Global Settings > Custom Send Workflows and enable access for your administrators.
Enabling the newest workflow experience brings workflows closer to the functionality of the manual Send process.
Features enabled with this option:
To enable the newest experience, navigate to: Account Settings > Send Settings > Custom Workflow Controls
In the Workflow Designer, all the enabled authentication methods are displayed in the recipient object.
The authentication methods have been updated to display as checkboxes, allowing the workflow design to permit options for the sender.
If multiple options are checked in the designer, these same options will be available to the sender during the send process.
The new sending experience adds phone (SMS) as an option in the designer.
The recipient objects in the designer can be marked as recipient groups. This allows for an array of email addresses to be entered into the Email field (comma delimited) that are permitted to sign for that one signature step.
For example, if you need one of five managers to countersign, you can list all five emails, but only one needs to apply a signature.
During the sending process, documents can be attached from any of the enabled Acrobat Sign sources.
The user experience under the "new" setting has been updated to a modern reflowable design, like the Send page.
The instructions that are to the right of the recipient list in the legacy experience have been moved to the top of the page in a collapsible window.
Template-defined field assignments strongly relate the recipient list, as defined in the workflow designer, to the appropriate field assignments on your authored forms.
Example uses case:
Traditionally this would require two forms because of how the recipients were indexed on the Send page:
Under the "template defined" rule structure, you construct one fully enabled form with all possible recipient fields defined.
The recipient signer index (as defined in the Workflow Designer) is strongly enforced, disregarding any fields that are assigned to any omitted (optional) recipients when the agreement is sent.
So in the use case above, the co-signer is always signer index 2, but if the co-signer is not included at the time the agreement is sent, those signer2 fields are ignored, and the counter-signer (signer index 3) will still only have access to the signer3 fields.
Enable this new functionality by navigating to: Account Settings > Send Settings > Custom Workflow Controls> Enable template defined signature placement
Enabling the template-defined signature placement feature will disable the option to author the agreement during the sending process.
Each recipient involved with an agreement is assigned a signer index number. This index number is required to associate the recipient with the fields they have authority to add content to (such as a signature field).
Recipients acquire their index number based on the stack order on the Send page. The recipient at the top of the stack is 1, the next recipient is 2, and so on. This index number can be seen when the agreement is configured to"Complete in Order" but is still present when the workflow is "Complete in Any Order."
When building a recipient flow in the workflow designer, the signer index is assigned following the rules:
In the example below, the Signer and Co Signer are at the top of the stack.
In this use case, it doesn't matter which physically signs first, so they are inserted into a parallel signature flow. However, the signature index is rigidly enforced to ensure the Signer applies their content to the correct "Signer" fields, and the Co Signer only has access to their assigned "Co Signer" fields.
The "Sales Rep" signs third, after both the Signer and Co Signer are done.
The "Exec Approval" is requested fourth, after the Sales Rep counter-signature is in place.
The recipient names "Signer," "Co Signer," "Sales Rep," etc. have no bearing on the field assignment. These are just admin-defined labels used for user clarity in the workflow template.
The above designer recipient flow will produce a Send page template that looks like the below.
(On the Send page, the stack order is more apparent, though the index numbers are not exposed.)
When authoring a form with fields, each field is explicitly assigned to a signing index (ignoring "Anyone" fields for the moment).
In the Acrobat Sign authoring environment, this is done by selecting a Participant and placing fields for that participant.
Each participant is color-coded to keep a visual distinction between what fields are assigned to each participant.
If you use text tags, the tag itself provides an argument (e.g. :signer1) that designates the field to the signer index.
Accounts that want to strongly enforce specific workflows for all of their documents and streamline the process of sending to the minimum amount of input by the user can fully define all of their document workflows and restrict users from ad hoc sending entirely.
Accounts that leverage Users in Multiple Groups can extend the configurable options at the group level settings, thereby ensuring the correct signature options and notification processes are rigidly enforced.
To limit users to only sending with approved workflows, navigate to Account Settings > Global Settings > Workflows and check Enable sending agreements using only workflows.
Some elements of the legacy workflow experience will produce errors under the new interface as a result of improved control and security in the newest experience. Additional error trapping has been put into place to better expose and explain these errors when encountered.
If the account is configured to use the Modern Send experience, and a problematic workflow is launched, the user is presented with a red banner indicating the error:
If the account is still configured to use the classic experience by default, the workflow may continue to work under those rules.
The modern experience displays errors as detected.
In the case where more than one problem is found, all errors detected will be listed.
To make the workflow valid under the new interface ruleset, an admin must edit the workflow and correct the detected issues:
Under the classic ruleset, email strings could be malformed or improperly delimited (with spaces vs. commas, for example).
When this error is produced, the admin should check:
When designing a workflow, it is possible for an Admin to attach a document template that has a limited access scope.
When a user that is outside this scope attempts to load the workflow, the document cannot be attached, and a security violation is triggered.
For example, an Admin may create a new document template with properties that limit access to the owner only. The admin can attach that document to the workflow because they are the owner.
Any other user of the system is not the owner, so is outside the scope of the document.
When this error is prompted, the admin will need to adjust the properties of the attached document template.