The user guide chapter is providing a basic documentation for envelope senders, registered users and administrators of an organization for the eSignAnyWhere product. After reading this guide you will know how to create and send signature requests and manage all organization related settings.
Further reading:
For users who want to go deeper into product capabilities, we recommend to consider also the following chapters:
Create and Send Envelopes
In addition an electronic signature guide is available for further information (also linked at relevant chapters).
To create a new envelope (or documents you want to have signed), just click on “New Document” or directly click “Upload” on the Dashboard. In addition, if you upload a document via Microsoft Office Plugin (available in the user menu top-right), you can select it from the Clipboard.
To send an envelope you have to go through three steps:
- Create envelope and define its workflow
- Designer to place signature and form fields
- Send Envelope
You also can save the envelope as Draft or Template.
(1) Create Envelope
When you create a new envelope, you can set at least the following parameters:
- Envelope: Name of the envelope and if you want to prevent the envelope from sharing in your team
- Documents: The documents in the envelope
- Recipients: define recipients and their order (sequential or parallel)
- Recipient Types:
- Needs to Sign: the recipient must sign the document to continue the workflow
- Receives a copy: the recipient gets a copy of the documents via email, the workflow continues automatically
- Needs to view: the recipient must open the document to continue the workflow
- Bulk: optional feature to split the document to send a unique document to recipients defined in the bulk
- Automatic Remote Signers: optional feature to sign with an automatic remote signature (For more information:Envelope structure)
- Needs to Sign (PKCS#7): optional feature to sign a document with a PKCS#7 signature (For more information: Envelope structure)
- Authentication: define if the recipient has to authenticate
- Access Code: The recipient has to enter the code to open the envelope (pre-shared code)
- SMS Code: The recipient receives a SMS with the one-time-password (OTP) to open the envelope
- Windows-Live Authentication
- OAuth / SAML / BankID as optional authentication methods (if available and configured)
- Personal Message for recipient and language
- Settings for Digital Remote Certificates, Disposable Certificates and SMS-OTP signature (optional)
- Message: Define the message and subject for the envelope
- Document Visibility: optional feature, which allows to define the document visibility defined by recipient (only if you use more than one document in the envelope and more than one recipient)
Meta Data: if enabled, the sender can add metadata to the envelope (e.g. for hybrid use cases)
To create an envelope following steps are necessary: Name the envelope, upload a document, select one to many recipients, (additional) design a personal message. The next figures will show you exactly how to create an envelope.
Error rendering macro 'multimedia'
com.atlassian.renderer.v2.macro.MacroException: Cannot find attachment 'CREATE.mp4'
| - Envelope
- Documents
- Recipients
- Message
|
You can replace documents. The signature fields are kept, except they can not be applied (e.g. page in new document doesn’t exist any more). If a recipient is replaced his/her fields get unassigned, except there is only one recipient.
If you open a template or an envelope, where you have already set signature and form fields, but you need to replace the document without losing the configuration, just click after loading the template or envelope, on the replace icon of the document.
| - Defines order in workflow
- Address book
- Phone number
- Task
- Personal message
- Authentication
- Additional details
|
Error rendering macro 'multimedia' com.atlassian.renderer.v2.macro.MacroException: Cannot find attachment 'phone_video.mp4' (2) Designer
The Designer helps you to assign predefined signature fields of the document to the recipients and define additional signature fields and form fields. - Recipients: Select a recipient for placing signature or form fields by drag and drop. Every recipient has its own color to be easily visible at the document preview.
- Form fields and predefined fields: signature field and form fields (e.g. text form, checkbox, radio button) and predefined field (e.g. initials of the recipient)
- Document: The document shows the pages of the envelopes documents and the placed elements (signatures and form fields) can be easily moved, edited (by clicking on it) and deleted (except predefined form fields of the uploaded PDF document).
Error rendering macro 'multimedia' com.atlassian.renderer.v2.macro.MacroException: Cannot find attachment 'Fields.mp4' |
Define Signature of Recipient
Please also see the electronic signature guide.
By clicking on a signature field, you can define its setting and behavior. Following options are available:
- Recipient: which recipient has to sign the field
- Label: the label of the signature field
- Required: define if the recipient has to sign it or if the field is optional. If a signature field is required it is highlighted with a red border.
- Signature Type: you have to select at least one type. You can select more, if you want to give the recipient the option to choose a specific type. You can also define a preselect type (favorite, click on star-icon). Please note, that not all types are available for all customers.
- Click to Sign: the recipient has just to click on the signature field to sign it
- Draw to Sign: the recipient can draw his signature (e.g. with finger on touch screen)
- Type to Sign: the recipient can type his name for signing
- Biometric Signature: this stores the biometric data of his recorded signature (x,y coordinates; pressure [if available] and time). For that signature type the recipient has to use the SIGNificant SignOnPhone App on his Smartphone or Tablet for recording. The Signature is asymmetrically encrypted and highly secure.
- withinField: the recorded signature must within the signature field
- onPage: the recorded signature must be on the page (can be written outside of the signature field)
- intersectsWithField: the recorded signature must be partly within the signature field (default)
- Local Certificate: the recipient can use a locally on his device installed certificate for signing.
- Digital Remote Signature: the recipient uses a remote certificate for signing
- Disposable Certificate: The recipient will receive an email as usual and when the recipient wants to sign a disposable certificate signature field he/she will get a one-time-password via SMS. The counter on the disposable certificate starts by signing the first signature. (For more Information please have a look into the Beginner Guide)
- SMS-OTP Signature: The recipient receives a SMS with the one-time-password (OTP)
| - No required field
- Required field (highlighted in red)
|
Batch-Signature
To increase the recipient’s user experience, you can use the batch signature. This allows the recipient to sign more than one signature field at once. Therefore, you have to select a first signature field and add the “Batch Signature” option. You can add more signature fields to the multi-signature field. So a signer is optionally able to sign all fields at once!
Properties and Limitations:
- The signer is asked, if he wants to sign all fields at once or one-per-one.
- Per envelope only one multi-signature-field can be defined via the Designer (with one to many fields and even within different files)
- You see the batch-signature-type with the icon
- If you select a batch-signature field, it adds its properties to the multi-signature-field (e.g. first field ist Click to Sign and second field will be added with Draw to Sign. So the multi-signature-field has two properties: Click to Sign and Draw to Sign). If you change the settings of a batch-signature field, it is applied to all fields of the batch-signature-set.
- You can use the batch-signature with limited signature types, because not all are able to be supported
- Changing the recipient of a batch signature causes that this signature field does not remain as a part of the batch anymore
- If you are using biometric signature as multi-signature, it is just able to use it on one physical document (e.g. contract.pdf in your envelope); because of legal aspects.
The following screenshot show you how to configure batch signing:
In the drop down for the batch signature (highlighted with the arrow) you have the following options:
- Simple Batch
- Signature List (unselected)
![](/download/thumbnails/65930085/3.6.png?version=5&modificationDate=1701789594094&api=v2)
- Signature List (preselected)
![](/download/thumbnails/65930085/3.6.png?version=5&modificationDate=1701789594094&api=v2)
- Signature List (selected, required mandatory)
![](/download/thumbnails/65930085/3.7.png?version=4&modificationDate=1701789589055&api=v2)
- Signature List (unselected, required mandatory)
![](/download/thumbnails/65930085/3.7.png?version=4&modificationDate=1701789589055&api=v2)
You can add form fields simply by drag and drop and place it on the document or via the advanced tags as predefined fields.
![user_8.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
The following form fields are available:
- Textfield
- allows the signer to fill in some text (e.g. telefon number)
- Signature (see above)
- Radiobutton
- allows to create a group of field, where just one can be selected (e.g. Yes or No)
- Checkbox
- allows to check a box; if required is set, the checkbox must be selected before the workstep can be finished.
- Listbox
- enables to select 0-many fields of the list
- Combobox
- enables to select one field of the list
- Signer Attachment
- allows the signer to attach a file
Some of the fields enable an advanced setting, where you can define additional settings (e.g. font family).
A more detailled explaination of the different Form Elements and their properties is contained in the Designer Page chapter of the Application Reference.
(3) Send Envelope
With the last step of creating and sending an envelope you get a summary, document list and notification setting of the envelope.
- Summary
- Envelope Name
- Recipients and Tasks: by clicking on a recipient you see the message which will be sent to the recipient
- Documents: List of documents in the envelope
- Notification Settings
- Expiration Date of the envelope
![](/download/thumbnails/65930085/21.16.png?version=3&modificationDate=1701789553451&api=v2)
- Automatic Reminders: configure reminders for the recipient if he has not fulfilled his tasks
- General Setting: To use a qualified timestamp server for all recipients
Regarding the expiration date of the envelope:
Before sending you have to choose between the following two options:
- Envelope expiry as relative time, provided in days:hours:minutes after sending the envelope
- Envelope expiry as absolute time, provided as timestamp and selected in the timezone in the account settings
On the last page (envelope summary) of creating and sending an envelope you can find the settings for the absolute, relative date and also the configuration for the reminders. Please see the next figure for detail information:
![](/download/attachments/65930085/reminder_2.PNG?version=1&modificationDate=1646317552410&api=v2)
Please see the following figure which shows the configured reminders in a timeline. Note that the use case one shows the exact configuration which is configured above in the envelope expiration settings. The difference in the second use is that the "warn signers before request expires (in days)" is 5 days instead of 4 which is shown in the configuration above. Summing up the configuration: The point
is the first reminder after the envelope was sent. After this first reminder the continuing reminders
start. Therefore, as it is configured in the settings above, every second day after the first reminder the recipient will get a reminder for signing the document. If also a reminder is configured before expiration
the continuing reminders will orient themselves on this reminder. This is shown in the second use case. If such a reminder is used, the continuous reminder can be postponed by one day (referring to the last continuous reminder). Overall, the recipient will receive a reminder again two days after the additional reminder
.
![reminder_timeline.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
For more information about the api configuration please also see the beginner guide.
| - Summary
- Notification settings
- General settings
- Send the envelope
|
Envelope Management
In addition an electronic signature guide is available for further information (also linked at relevant chapters).
Documents, Filter and Status
Documents will list your sent envelopes & drafts and envelopes you have to sign (sent by someone else). It also shows you the envelope status and allows you to filter and manage the envelopes.
Features
- Search: enter a text to search the envelopes
- Status: an icon shows the status of the envelope
- Actions: direct on-click to sign or continue
- Export as CSV: export current list of envelopes (e.g. for a reporting)
- Sort by: recent activity or envelope name
- Filter: click on a filter from the menu to apply it to the current list. You can easily apply more filters to the selection or remove them one-by-one.
| Description |
---|
| - Filter
- Search
- Status
- Export as CSV
- Actions
|
Document Status Icons
| Envelope is finished |
![status_2.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2) | Envelope is canceled by one of the recipients |
| Envelope is rejected by one of the recipients |
| Envelope is a Draft |
| Waiting for signing |
| Waiting for acknowledge |
| Caution (e.g. email bouncing) |
| Envelope is expired |
Envelope Details
To modify an envelope just click on it to load the envelope details page. On this page you can see the defined workflow with recipients, the document(s) and basic information about the envelope (e.g. start and expiration date). Moreover, you are able to enable or disable, if the envelope is shared with your team members.
Possible Actions on the envelope:
- Sign: if you are the signer, you can directly open the envelope for signing
- Remind: if a signer is not signing (or rejecting) the envelope, you can remind him manually. The reminder notification will be sent to the recipient (the automatic reminder will still continue to work, if configured). Please note that a manual reminder limit of 12 hours (default value) is set. This means you can only send one reminder every 12 hours, to prevent spamming the recipient. This value can be changed on private SaaS and on premise instances.
- Cancel: Cancel will stop the envelope and cancel the workflow. The recipients will get a notification about cancellation.
- Unlock: if a signer has blocked in a parallel signer step the envelope (opened, but is not finished/rejected), you can manually reset his document changes to enable the envelope for the other parallel signers. (Note: in a parallel signer step, only one can open and sign the document. As long as the envelope is not finished by the signer, the others will not be able to sign the document. This is based on a technical limitation of the security of the PDF document, which is only allowing sequential changes to ensure its security).
- Delete: Delete the envelope
Document Detail Page with highlighted envelope and recipients area.
| Description |
---|
| - Details
- Recipients
- Message
|
Finished envelopes will allow you to download the finished documents and audit trail (log document). If you have the developer mode enabled, you can download the envelope configuration as XML and JSON. The next screenshot shows where you can download the finished document and the audit trail:
| Description |
---|
| - Download documents
|
The audit trail shows all information about the envelope e. g. the general information (status of the envelope, the creation date and more). Moreover, it shows the recipients and all changes made to the document e. g. which signature fields were placed on the document, the information about the time when the workstep was finished and more.
The finished document shows the PDF including the signed signature fields. Please also have a look at the signer guide.
Edit & Delete Recipient
It is possible to edit or delete a recipient after the envelope was sent. Therefore, you just click on “edit” to change user details (First Name, Last Name, Email), set the personal message, change authentication method, set digital remote signature or set SMS-OTP signature. You can just change details of recipients, who did not yet fulfill their assigned task. Finished recipients are shown via icon in the Document detail view. “Delete” will delete the recipient’s envelope, as long his signing task was not yet finished.
![user_13.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
Clipboard
The “Clipboard” link will show you a window with a link (to copy) to the recipients envelope for signing. In case the signer has a problem with receiving the email, you can send the link to the recipient via other channel (e.g. instant messenger).
Figure | Description |
---|
| - Clipboard
|
Document Preview
The document preview will show you a small and, by clicking on it, a large preview of the document.
![user_15.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
Filter Document
- Status
- Drafts, Completed, Active (Action Required, Waiting for Others, Expiring Soon), Rejected, Canceled and Expired
- Sent | Signed
- By Me
- By a team member
- By team
- Sender Date
- Yesterday, Since last 7 Days, 30 Days, 90 Days, 6 Months, Year and Custom Date
- Bulk (if feature is available)
- Exclude bulk children
- Bulk parents only
- Text
- Filter by a text you have entered (at the top bar)
The applied filters are listed at the top and you can remove specific filters by clicking on the “x” or reset all filters.
![user_16.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
Download as CSV
You can also download CSV (comma-separated values) files. So you can open them in e.g. Microsoft Excel for analysis or reporting.
Figure | Description |
---|
| - Download as CSV
|
The CSV contains:
- ID of the envelope
- Name
- State
- Sender
- Sending Date
- Expiration Date
- Subject
- Document(s) as CSV
- Recipient(s) as CSV
Templates
Templates can be used for recurring documents or workflows. You can prepare them and directly use them from the template page. When you use or edit the template the procedure is similar to create envelope, except the prepared configuration is used.
Features:
- Use: directly use the template as a new envelope (same function also available in creation of an envelope in the document section as "add a template"
- Details: show details about template
- Edit: modify template
![user_18.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
We offer to make the document generation easier or support dynamic document length a possibility of document tags (signature fields) and advanced tags (signature fields, workflow, input fields).
Here you can download a PDF which contains one recipient with a Click2Sign signature field by using the tags. For a complex example please see the Text Placeholders Use Case.
This section will show you how you can use documents with eSAW. eSAW will work with PDF documents. To generate PDF documents you can use Microsoft Office, Open Office or most of the typical document suites. If your document suite does not export PDF documents you can install a PDF printer on your computer. Instead of printing a document it will be exported as PDF file. There are many different printers available (open source to commercial).
Placeholder for Signature fields
To place signatures fields via workstep configuration can be a little bit “overhead” in some simple cases. Therefore we offer you the possibility to place signature fields directly in the document via tags. These tags are called SigStrings (SignatureStrings).
Example of a SigString, which is places as text directly in the document:
`sig,fd=Confirm the General Terms`
If you place this string as normal text in your document, eSAW will replace it with a default signature field. The parameter fd=Confirm the General Terms is the field description. We recommend to place the SigString with the paper color (typically white) in the document, so the string itself is “invisible”.
Following Parameter are supported:
req | 0: disabled, default / 1: enabled |
fna | name of the signature field |
fd | field description, gets displayed during signing in WSI |
sigType | signature type, supported: BiometricSignature, Picture (Click2Sign, Type2Sign, Draw2Sign) |
positioning | Defines if the signature can be placed outside of the signature field (onPage, intersectsWithField) or will be placed into the signature filed (withinField). possible values - onPage
- withinField
- intersectsWithField.
|
Example 1: Simplest SigString, just a optional signature field
`sig`
Example 2: SigString, required, with description, name and as biometric signature
`sig,req=1,fd=myFd,fna=myFna,sigType=BiometricSignature`
Example 3: SigString, not required, as Picture (Click2Sign, Draw2Sign, Type2Sign)
`sig,req=0,sigType=Picture`
Example 4: SigString, required, with description and positioning
`sig,req=1,fd=myFd',positioning=onPage`
As position for a signature field, the lower left beginning of the sig-string will be taken. In case the string part of a word, the beginning of the word will be the position.
These SigStrings are also supported via API (use AdHoc configuration to modify them). So you can dynamically place signature fields on the document (e.g. sometimes on bottom of page 3, sometime on top of page 4).
Advanced tags support you with more flexible tags, such as form fields (radio buttons, check boxes, text fields, …), styling and workflow features. Even an input validation is available. If you want to use the advanced tags, please go to the Text Placeholders Use Case.
Additional Envelope Features
Bulk Envelopes ![](/download/thumbnails/65930085/3.1.png?version=6&modificationDate=1701789577136&api=v2)
For further information please see the Bulk Sending Use Case.
This feature allows you to send an envelope to multiple signers. The workflow will be split at this order into unique envelopes for each bulk recipient. This allows you to create a workflow, where the first signer (e.g. head of a department) signs the document and then each of the bulk recipients (e.g. employees of the department) receives a unique document for signing.
Design the Workflow
| - Add a bulk as recipient
- Information to upload a CSV
- Create a bulk CSV for upload
- CSV upload
|
Create a Bulk CSV with a template
![user_21.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
The import CSV (with PIN authentication) should have the following parameter, where the first line is required as column identifier:
FirstName, LastName, Email, Authentication>>Pin, Authentication>>Pin>>Param
Charly, xyzmo, charly@namirial.com, false, 1234
Bob, xyzmo, bob@namirial.com, true, 5555
If the Authentication>>Pin is enabled (true) the authentication is activated. The last number is an example value for a parameter for the authentication.
![user_23.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2) | - Contains all recipients inside the bulk
|
After creating your CSV, you can upload it. Afterwards you can continue the standard process of creating an Envelope. For further information please see the Bulk Sending Use Case.
Automatic Remote Signatures ![](/download/thumbnails/65930085/3.2.png?version=4&modificationDate=1701789571224&api=v2)
eSignAnyWhere allows you to use automatic remote signatures to be applied to a document. Details are available in the Beginner Guide. Please contact your Namirial Sales if you are interested in this feature.
PKCS#7 Signer ![](/download/thumbnails/65930085/3.1.png?version=6&modificationDate=1701789577136&api=v2)
This is a feature to allow the signer to sign a document with a PKCS#7 signature. You find details in the Beginner Guide.
SwissCom On-Demand-Certificate ![](/download/thumbnails/65930085/3.3.png?version=5&modificationDate=1701789582365&api=v2)
Please contact your Namirial Sales if you are interested in this feature.
BankId ![](/download/thumbnails/65930085/3.4.png?version=3&modificationDate=1701789599103&api=v2)
Please contact your Namirial Sales if you are interested in this feature.
Clipboard & Microsoft Office Plugin
You find the Microsoft Office Plugin for download in the top right account menu:
Download the plugin and install it:
![user_25.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
The plugin directly uploads the document in the clipboard of your eSignAnyWhere account. After the installation, you can use in Microsoft Office the eSignAnywhere Plugin, but first you have to configure it with your user token. The user token can be found in your Settings/Account page.
If you upload a file, it appears in your clipboard. A uploaded clipboard file can be used for one envelope. Therefore, if you click on the button “start envelope” the file will be deleted from the register clipboard. If the retention period is enabled, the clipboard files are deleted automatically after 24 hours.
You can find the plugin in “Add-Ins”
![user_27.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
Configure the user token:
![image2022-9-23_13-33-5.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
If you use eSignAnywhere on premise you also can configure the endpoint (URL).
![user_29.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
By clicking “Upload to Clipboard” the document will be uploaded to the clipboard. To use the uploaded file, just go to your clipboard and click on “Start Envelope”. A clipboard file can only be used for one envelope.
![user_30.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
If you want to create your own “upload-to-clipboard” application, you can easily do it via API (UploadUserFile_v1
[SOAP]). Only the user token and a file XML, similar to the upload data structure (UploadTemporarySspFile_v1
) and an optional source of the file.