eSignAnyWhere Versions

eSignAnyWhere 3.3

Date: November 2018

Improved security to protect your document

The security of your documents is in our primary focus. Therefore, we improved the security of eSignAnyWhere to ensure the security of your documents.

Improved performance to grant excellent user experience and scalability

We improved the overall performance of eSignAnyWhere for excellent user experience and increased scalability to grant you high performance, even in critical high load scenarios.

Improved support for point of sales use cases

Improvments for point of sale use cases. This includes for example optimizations for timeouts in the clients and data handling for fast responses in a workflow.

Allow to define a logout redirect page

eSignAnyWhere allows you to define a logout redirect page. So you can integrate eSAW in your intranet applications and set a specific logout page for your users.

Improved on-premise setup

We improved the installation procedure for on premise installations of eSignAnyWhere.

SwissCom Support

We added for API use cases the support of SwissCom certificates (personal and organization certificates).

eSignAnyWhere 3.2

Date: August 2018

Automatic Remote Signatures

It is possible (as advanced feature) to use automatic remote signatures. The user manager of an organization can add automatic remote signature profiles, which can be used for any workflow as a recipient (recipient type “Automatic”). This recipient signs automatically the signatures and the workflow continues automatically. Details see Advanced User Guide.

API: allow modification of uncompleted steps

It is possible to use the replace recipient method (ReplaceRecipient_v1) to change the workstepconfiguration. It is only possible to change the workstep configuration if the envelope was created via API and the recipient is a signer.

Full Support of SIGNificant Biometric Server

eSignAnyWhere 3.2 now fully supports the SIGNificant Biometric Server for signature verification, including the SignAnyWhere Viewer and the audit trail file. This feature is not available on significant.com and requires a private SaaS or on premise instance of eSignAnyWhere.

Enhanced SAML Support

The SAML support was extend to allow easier user management directly in the UI of eSignAnyWhere. SAML requires a private SaaS or on premise instance of eSignAnyWhere.

Automatic Delegation

Automatic Delegation is an advanced feature, which allows the user to define a automatic delegation. So all of the user’s signing requests are automatically forwarded to a substitute, which is also a user of the organization. An optional end date automatically disables the automatic delegation.

eSignAnyWhere 3.1

Date: May 2018

Bulk Envelopes

Bulk envelopes allows you to send an envelope to multiple signers. The workflow splits with the bulk recipient, so that you will receive unique signed documents for each bulk recipient. This feature is perfect for let one document (e.g. a new company policy) sign by many recipients. This feature is not available with basic subscription, so please contact your Namirial sales. Details in the Advanced User Guide.

P7M Signers

It is possible to define P7M signers in eSignAnywhere. This allows you to define at the end of a signing workflow to define signers with P7M. Details see in the Advanced Guide.

REST Interface

In addtion to our SOAP interface a new REST/JSON Swagger interface is availabe. See www.significant.com/api

Form Field Data Validation

Added support for Form-Field-Validation. Six types are supported: No-Validation, Date, Email, Number, Phone and Time. It is only supported with the Advanced Tags and via workstep configuration.

Retention Period per Organization

The Retention Period per organization sets an automatic timelimit for deleting old envelopes.

Configure Emailsender Name

You can select now the email sender name. In the organization settings you can select between three options: (1) firstname lastname via eSignAnywhere (2) Organizationname via eSignAnywhere (3) eSignAnywhere. On-premise or private SaaS customer can replace eSignAnywhere with their desired text. Via API you can select the option for each envelope.

<envelope>
   ...
   <displayedEmailSender></displayedEmailSender>
   ...
</envelope>

If the displayedEmailSender is empty only eSignAnywhere is used. If the field is not empty, this text will be used before ” via eSignAnywhere”. Without displayedEmailSender the organization default setting is used.

SAW Viewer: change attachment after uploading

The signer can now remove an already uploaded attachment from a document in case of a mistake.

eSignAnyWhere 3.0

Date: February 2018

Hide documents for certain recipients

With this feature you are able to hide specific documents from specific recipients. So you can create an envelope with two documents, where the first signer just can see the first document, the second signer only the second and the third can see all documents. You can configure it in the eSAW UI or via API.

API Configuration is done via envelope/steps/step/documentOption; Sample:

<envelope>
   ...
   <steps>
      <step>
         <emailBodyExtra>
         </emailBodyExtra>
         <orderIndex>1</orderIndex>
         <documentOptions>
             <documentOption docRef="1">
                 <isHidden>1</isHidden>
             </documentOption>
             <documentOption docRef="2">
                 <isHidden>1</isHidden>
             </documentOption>
         </documentOptions>
         <recipientType>Signer</recipientType>
         <workstepConfiguration>...</workstepConfiguration>
         <recipients>
            <recipient>
               <eMail>next@recipient.domain</eMail>
               ...
            </recipient>
         </recipients>
      </step>
   </steps>
</envelope>

This feature is not available in all subscriptions.

SMS-OTP Signature - one SMS OTP per signature

A new signature type is now available. You can define a signature field, which sends a SMS-OTP in the moment of signing to have a second factor for it. Basically, it is a Click2Sign with an SMS-OTP. You can select it via UI (SMS-OTP Signature Type) or via API:

<recipient>
...
  <smsOtpAdditionalInformation>
    <phoneMobile>...</phoneMobile> <!-- naming consistent with "disposableCertificateAdditionalInformation" -->
  </smsOtpAdditionalInformation>
</recipient>

Moreover, in the workstep config the type must be TransactionCode, with trModType set to TransactionCodeSenderPlugin.

This feature is not available in all subscriptions.

Custom Links for Notifications

For on premise and private SaaS it is possible to configure custom links for notifications. So the workstepRedirector can support your apps to open directly the workstep. For more details contact your Namirial consultant.

Acknowledge Recipients are included in the "send finished documents to all signers"

Acknowledge recipients are included in the “send finished documents to all signers” checkbox in the eSAW UI (and it is renamed to support also acknowledge recipients).

API: download attachment directly via eSAW

If you are generating a workflow, where a recipient has to enter data and upload a file (as PDF attchment), you can now directly access the file via eSAW API. Call the getEnvelopeById function to retrieve information the attachment and the fileId for downloading.

API: Reading Task (evidence of reading the document)

It is possible to set a behavior to confirm reading of a document.

Set in the WorkstepConfiguration (for a recipient) the following Task (in workstepConfiguration\Policy\WorkstepTasks):

<Task enabled="1" completed="0" required="1" id="847a3d4a-da2c-46f4-8c8c-a9edaa06c29b" displayName="your text for this task" DocRefNumber="1" type="ConfirmReading" />

The task must be the first and required!

Then you have to create the ReadingTaskInfo (directly in the WorkstepConfiguration) with attribute AllDocuments=”1″:

<ReadingTaskInfo positionUnit="PdfUnits" positionReferenceCorner="Upper_Left">
	<ReadingTask id="847a3d4a-da2c-46f4-8c8c-a9edaa06c29b" pageNumber="1" DocRefNumber="1" AllPages="0" AllDocuments="1" />
</ReadingTaskInfo>

API: call on expired envelopes

You retrieve now also a callback, when an envelope expires.

API: getEnvelopeById has more details in it

The getEnvelopeById contains now more details about the envelope (e.g. recipient details, signing date and authentication).

Advanced Tags - offset support

Advanced Tags now support a offset, to define a relative positioning of the element. Offset is defined as number (double), in Units points and starts at the lower left position. Positive values x are moving to right and positive values y are moving up. e.g.

:offset(x=-10.5,y=50.6)

eSignAnyWhere 2.6

Date: January 2018

Language support of Audit Trail

The Audit Trail supports now different languages:

  • SignAnywhere Viewer (Signer-Interface): Audit Trail is rendered in the language of the viewer
  • eSignAnywhere UI: Audit Trail is rendered in the users UI language. Moreover it contains a language independent XML representation.
  • API: via API you can download a signed XML, containing the Audit Trail data (via GetEnvelopeById as logXmlDocumentId)

SAML 2.0 Support for Signers

You can use now SAML to authenticate signers in the SignAnywhere Viewer (Signer Interface). You configure the SAML provide and can use it via UI and API. Click here for details about the configuration for API. Contact your Namirial sales for enabling SAML support.

This feature is not available in all subscriptions.

Private SaaS/OnPremise: support of individual biometric encryption keys per organization

Only private SaaS and on premise: each organization of the instance can have their own biometric encryption key.

Delete recipient

It is possible to delete recipients of already started workflows, which did not yet signed the document. This is available in the detail view of an envelope in eSignAnywhere.

Show a reject button in the SignAnywhere Viewer (Signer Interface)

It is now possible to show a permanent reject button in the menu. This can be configured via customization with the new parameter DisplayRejectButtonInLeftBar.

Signer Authentication: add OAuth Authentication checks

With OAuth2 it is now possible to do a authentication check. So you can force that a specific userId has to authentication via OAuth2 provider.

E.g. userId=123 of provider CustomOAuthService has to authenticate. If another user authenticates it is rejected. Just user with userId=123 is accepted.

See Envelope XML Guide to see how you configure it via API.

This feature is not available in all subscriptions.

Audit Trail per document

You can now, in addition to the envelope audit trail, download for each file a specific audit trail via API (GetEnvelopeById in section completedDocuments). You can enable it in the organization settings.

Download Envelope XML for Developers

If you create an envelope within the eSAW UI, you can now download the complete envelope XML including the workstep configurations for your envelope. Therefore you have to be a “Developer”, which can be set up by a user manager in the account settings. Then you are able to download the XML at the end of the envelope-sending-process and in the envelope details page.

Default Callback URL for Organizations

You are able to set a default callback URL in the Organization settings of eSAW. So you can send out envelopes via eSAW UI and perform an integration on your side (e.g. an automatic archiving of the documents).

eSignAnyWhere 2.5


Date: September 2017

API: Custom callbacks on specific events

New types of callbacks are now available. See documentation for details.

On-Premise supports different organisations

The on premise version of eSignAnyWhere supports now different organisations with just one instance.

Full support of SIGNificant Device Driver

Full support of SIGNificant device driver. So you can use now signature pads or local certificates with eSAW as a signer.

New eSAW viewer settings

New eSAW Viewer settings are available. For example, you can define now to automatically finish a document when the last signature was applied or configure the download document dialog. See here for details.

Performance Improvements

The performance of eSAW was improved. For example is the generation of the Audit Log optimized and the envelope-postprocessing, if no email is sent, done with highest priority.

API: Additional information for GetEnvelopeById

GetEnvelopeById contains now the reason about rejection or delegation.

<recipient>
	<status>Rejected</status>
	<rejectReason>...</rejectReason>
</recipient>

<recipient>
	<status>Delegated</status>
	<delegateReason>...</delegateReason>
</recipient>

eSignAnyWhere 2.4

Date: July 2017

Designer supports now PDF Forms

We added the support of PDF form fields in the designer. So you can add textfields, radiobuttons, checkboxes, lists and many more directly in the designer by drag and drop. You can select the behavior similar to signature fields (select a recipient) and configure some properties of them. See the User Guide for more information.

New advanced tags for predefining signature and form fields

New advanced tags are supported to predefine in the documents signature fields and form fields. They are more complex than the easy to use Signature Strings (see User Guide). The advanced tags are documented in the Advanced User Guide. For the advanced tags a new API function PrepareSendEnvelopeSteps_v1 is available.

Template: replace documents

It is possible to use a template and replace the document of the template. The position of the fields (e.g. signature fields) are kept. See the User Guide for more details.

Predefined Signature for registered signers

Registered signer are able to upload picture of their signature (e.g. written on paper) and import it to eSignAnyWhere. eSAW enables an editor to modify and adopt the signature (crop, rotate, cut) to be used as signature for signing. See User-Guide for more details.

Emails are sent as attachment under 2,5 MB, otherwise they send out an link for downloading

To avoid filling up email postboxes, eSAW now sends the documents as attachments, as long as they are under 2,5 MB. If larger documents are used, just a link to the document is sent. This link is valid for 90 days to download the file.

API: Usermanagement

You can now manage the users of your organisation via API. See API Reference for more information.

API: Find envelopes

You can now use the FindEnvelopes_v2 function for advanced search via API. See the API Reference for more information.

Integration: avoid sending email for specific recipients

For complex integration it is now possible to disable sending emails for a specific recipient (e.g. in a POS scenario). See Integration for details.

Integration: add custom buttons in eSAW signing interface

You can add now custom buttons in the signing interface (the eSAW Viewer) to add custom functionality.

Customization: added settings for eSAW Viewer

We added some configurable settings, such as avoiding dialogs or settings for Batch-Signing, for the eSAW Viewer. So you can define the behavior of the signers-view. See Advanced User Documentation for more details.