• It is now allowed to have multiple identity providers in use for a single recipient. Please note that this is only allowed if the providers have a completely identical set of update rules.
• Nested JSON in JWT are now also accepted by the OAuth2 checks.
• The separation is now more visible between the OAuth2 Authorization Providers and the OAuth2 Identity Providers. In detail:
  • In the OAuth2 Authorization Providers list you will now only find OAuth2 providers with just validation rules
  • In the OAuth2 Identity Providers list you will now only find OAuth2 providers with at least one update rule
• Stabilization of OAuth2
  
  • Stabilization of the OAuth2 provider authentication via api.
  • The template which was created from an envelope with OAuth2 configuration now also includes the OAuth2 configuration from the original envelope.

For more information about the OAuth2 configuration please have a look at the OAuth2 guide and for samples please also see the OAuth2 sample guide.

• Additionally to the hash of the finished envelope you can now also find the hash of the initial document in the audit trail
• The audit trail now also contains the eSAW version information
• The audit trail sealing now considers PAdES signature level.
• Stabilization of the audit trail
  • You can now find information about the OAuth2 authentication in the audit trail.
  • Timezone formatting issue fixed.
  • Chinese characters are now supported to be displayed correctly in the audit trail.

For more information about the audit trail please see the electronic signature guide.

There will no longer appear exceptions if a document is uploaded with predefined syntax which do not meet the requirements. Instead you will get the following warning:

Image Modified

You can either proceed with the uploaded document or cancel the upload.

For more information about the field markup handling in general please see the following guide: Field markup

You can now also configure JWT for the OAuth2 authentication for user authentication and signer authentication. For more information please see the How to configure OAuth2 authentication. For OAuth2 samples please see this guide. In this guide is also a ID Austria sample with JWT documented.

Document browsing is now also supported for the devices listed above. Please note that the feature is disabled per default but can be configured either in the SAW viewer global.xml or in the customization service.

global.xml:

 <!-- Defines whether or not to enable document view on some specific compatible signature pads (e.g Wacom STU 520/530/540, NT5010 or some StepOver devices)
           'useDocViewMonitor': defines whether or not to use a 'doc view monitor' upon using specific compatible devices (e.g. Wacom STU 520/530/540, NT5010) -->
      <DocViewModeEnabled useDocViewMonitor="1">0</DocViewModeEnabled>

Customization Service:

  <!--Defines whether or not to enable document view on some specific compatible signature pads (e.g Wacom STU 520/530/540, NT5010 or some StepOver devices)-->

   <variable category="global/SignificantDriverConfiguration" comment="Defines whether or not to enable document view on some specific compatible signature pads (e.g Wacom STU 520/530/540, NT5010 or some StepOver devices)" value="0" name="DocViewModeEnabled"/>

   <!--For 'DocViewModeEnabled': defines whether or not to use a 'doc view monitor' upon using specific compatible devices (e.g. Wacom STU 520/530/540, NT5010)-->

   <variable category="global/SignificantDriverConfiguration" comment="For 'DocViewModeEnabled': defines whether or not to use a 'doc view monitor' upon using specific compatible devices (e.g. Wacom STU 520/530/540, NT5010)" value="1" name="UseDocViewMonitor"/>

</significantdriverconfiguration>

This feature allows signers to upload their picture (custom signature picture) and add it as additional graphics to the stamp imprint. Furthermore signers can store the signature image within a gallery for later usage. For more information please see the following documentation: Use external signature image

All dialogs support now keyboard usability.

"ESC" keypress

• closes the dialog
• stops additional tasks if required

"Enter" keypress

• activates the primary button, when no other action is required in the dialog
  • e.g. "Finish" dialog

"Tab" keypress

• to navigate to the next element

For more information about the keyboard usability and about other aspects of the accessibility please see this guide.

The generic signing plugin is now also available for short time certificates (one time, one shot,  disposable etc.).

For more information about the generic signing plugin please see the release notes 21.16. For detailed information about the REST configuration of the generic signing plugin please see this guide.

With eSAW 21.31 we introduced, as part of a bugfix, a more strict phone number validation. For example: SMS-OTP authentication, the phone number must be provided in international format (+xxyyyyyyyyyyy) where +xx is the country prefix, and yyyy is the phone number inclusive carrier prefix (different length of country prefix and phone number are supported). The  use of phone numbers without country prefix - which did not return an error via REST Api, but did not lead to successful delivery in many cases - cannot be supported any longer as it was not determined which country is used.

We improved again the performance of our solution to provide you an excellent user experience.

The identity settings providers moved to a separate configuration page. Those settings can now be found in Settings → Identity Providers. Please also see the next figure:

Image Modified

The SwissCom OnDemand Certificate is now also available in the UI. You can find the settings for the SwissCom OnDemand Certificate in Settings → Organization.

Image Modified

The settings for the recipient can be found on the create envelope page. There you have to fill in the mobile phone number, the country of residence and the organization (optional).

Image Modified

After these configurations you can use the SwissCom OnDemand Certificate as signature field in the UI:

Image Modified

Moreover, you can create a SwissCom OnDemand certificate signature field with Advanced Document Tags.

Just add the following code to your document to place a SwissCom OnDemand certificate signature:

[[!sigField1:signer1:signature(sigType="SwissComOnDemandCertificate"):label("some label"):size(width=150,height=60)]]

For general information about the advanced document tags please see: Use Text Placeholders to insert Form Elements or Signature Fields

The recipient who has to view the document was renamed to "Must view" recipient instead of "Acknowledge" recipient. For example:

Image Modified

Please note: For detailed information about the 21.16 features please also see this release notes document.

The feature implementation change of envelope expiry allows to specify absolute expiration timestamps (date and time), beside relative expiration date. For the relative expiration date, it allows specifying days, hours and minutes instead of just days. An expiration of less than one day is now supported. This enables senders of an envelope to set the exact expiration timestamp of an envelope, e.g. for offers valid just till an exact time like midnight.

With release 20.14 a year ago, the REST API Versions /v1 and /v2 have been marked as obsolete/deprecated and a migration guide has been published. With the 21.16 release, those versions have been removed:

• /api/v1 (also accessible via /api/v1.0)
• /api/v2 (also accessible via /api/v2.0)

The REST migration guide, which contains also some more information about the different API versions and in particular about the differences from version 1.0 or 2.0 to newer versions, is available here:

Migration Guide

Please mind that the guide describes the migration to v4, but similar functionality will also be applicable for a migration to /v5. The swagger documentation, which is our REST API reference documentation, is available here:

https://demo.esignanywhere.net/Api/swagger/ui/index

When storing signed documents in a document management system (DMS), a tagging of the document(s) is common and mandatory to find the document again. While eSignAnyWhere already supported providing metadata in API integrations, older versions allowed the sender via WebUI to specify just one free-text metadata field with the recommendation to put an XML structure into it. Since 20.52, it is possible to integrate custom tagging implementations, which consider structures and allowed values predefined in a DMS. It allows organization admins to define a custom page, being presented to the sender before sending an envelope for signing.

The UI of a metadata tagging form (or other before-send redirect page) can be aligned to the eSAW UI look and feel, or be aligned e.g. with your DMS. Consequently, the new change now allows defining metadata in templates. This can be used to set defaults, which are considered in a custom tagging page when a template was used to create the draft. Beside DMS tagging, metadata can be used also to define other values necessary for post-processing by a callback handler. Any additional information/description can be added into the metadata section of an envelope.

You can now configure the following viewer preference: AcceptAgreementDisabledUntilRequiredActionsDone

Note: You can configure the viewer preference in the UI in the section organization->design of the document viewer. Download the design template or your current design and set the variable AcceptAgreementDisabledUntilRequiredActionsDone to 0,

to disable this preference or to 1, to enable this preference. You can also configure this viewer preference via API. Therefore, just add the following variable in the section viewer preferences like it is shown in the next sample:

"ViewerPreferences": {
          "AcceptAgreementDisabledUntilRequiredActionsDone": true,
          "VisibleAreaOptions": {
            "AllowedDomain": "*",
            "Enabled": false
          }         },

Please also make sure that the "Allow Electronic Record and Signature Disclosure" is enabled:

If the preference is set to true and the agreement configuration is enabled the signer will then see the following interface before accessing the document:

On-premise only.

Organization Export

Allows you to export an organization’s settings and use it to create/update other organizations. Organizations can be exported, created and updated using the DB Manager or Admin Web. The result of the export operation is a Zip file that holds 3 files as follows:

• Logo – The organization logo. (If the organization has no logo, then this file will be missing from the Zip file)
• CustomizationZip.zip – Customization file of the organization. (If customization is not allowed for the organization, then this file will be missing from the Zip file)
• ExportedSettings.xml -The actual settings of the organization in XML format.

Organization Import

There are two options for organization import:

• Create new organization using the exported data of other organization.
• Update an existing organization with the exported data of other organization.

The update process will skip updating the settings below (even if they are in the xml file) since they can affect ongoing/draft envelopes.

• OAuth settings
• Saml settings
• Bank Id settings
• SwissCom settings
• Disposable certificate settings

Note: Data such as envelopes, address book etc. are not supported with the export/import of the organization.

If you use lean disposable via API, you have to provide the document issuing country instead of the country of residence. Therefore, we introduced the DocumentIssuingCountry via API. For compatibility with existing implementations, we allow to use the field CountryOfResidence but for legal reasons you also have to provide here (when using lean disposable) the country which issued the identification document.

If you do not use lean disposable (but consider that the “traditional” non-lean disposable should be used only in exceptional cases), you have to continue using the field CountryOfResidence as in the past.

This plugin provides a generic way of integrating external (remote) signatures. Please see the following supported features:

• Signing types (defined by the plugin implementation)
  • User signing
  • Batch signing
  • Automatic signing
• Authentication
  • Using dynamic data fields
    • Types: Text, Phone number, Number, List (dropdown), Email, Password
  • Using external system (redirection to external URI)
  • Using external app (e.g. push notification) + callback receiver
• Signing method
  • Hash signing only via the plugin
  • Hash signing only via the default SSP integration

For more information about the configuration in the UI please have a look at the Electronic Signature Guide, the Signer Guide and the User Guide.
For more information about the configuration with REST API please have a look at the Beginner Guide. There you can find a sample configuration.

Previously the API authorization consisted of two parameters (OrganizationKey and UserLoginName). This has been reduced to a single parameter; an API Token. This token is individual for each user and can be created/updated/disabled/deleted on a new Page (ApiToken/Index->My Tokens). A user can have multiple API Tokens that allow a more granular usage of them. For example one token for integration A and another token for integration B.

Note: If a token is deleted it can not be recreated with the same token value.

Two possibilities for authentication:

1. Using the new API Token header (REST) or the API Token XML node (SOAP). Here
   only the API token is a valid value.
2. Use the OrganizationKey and the userLoginName for the authentication

For more information about the

• configuration in REST please have a look at Postman Guide
• configuration in SOAP please have a look at Hello World Guide
• generation  of a new Api token please have a look at Setting/User Guide

You can now also use the driving license as an identification type. This new identification
type is available in the UI as well as in the API.

For more information about the disposable certificate please also have a look at the Beginner Guide.

The bulk signing assistant is a feature that allows you to sign multiple documents with one click.

Note: The bulk signing assistant (eBSA) currently does not support the full set of features of eSignAnyWhere envelopes and signature methods. It is limited to

• Envelopes without authentication
• Envelopes that use Click2Sign as the only signature variant
• Only envelopes that do not require confirming an agreements dialog (Terms&Conditions) first

Please see also this guide: Bulk signing assistant

You can now find the setting in your organization to lock form fields. If you prevent editing form fields after the envelope is finished the form fields in the PDF are all read only. Therefore, after locking the form fields (after the final workstep), the form fields are not editable any more with other PDF tools.
For more information please have a look at this page.

You can also lock form fields with the API. Therefore, just add the following before the node “steps” in REST:

"LockFormFieldsAtEnvelopeFinish": true,

Or in SOAP:

<lockFormFieldsAtEnvelopeFinish>true</lockFormFieldsAtEnvelopeFinish>

In your organization settings you can now select required authentication methods. You can either select any or a specific authentication.

Moreover you can set the following

• Force input of the phone number when using SMS-OTP authentication
• Allow skipping forced authentication upon using biometric signatures
• Allow skipping forced authentication upon using disposable certificate, remote certificate or local certificate

For more information please have a look at this page.

You can find this feature in your organization settings in the section “Testing Phase Features”.
There you can allow to copy the viewer link from the envelope details page. If the user signs the envelope via the copy viewer link, then this information is also shown in the audit trail.

For more information about the clipboard please have a look at this page.

You can now define hyperlinks for your document with API. The next lines of code show you a sample configuration of one hyperlink:

"HyperLinks": [
		{
		 "Id": "c238bd01-78ca-4958-a6dc-957fed629aa0",
		 "DocRefNumber": 1,
		 "PositionPage": 1,
	         "Uri": "https://www.esignanywhere.net/",
			"Position": {
				"PositionX": 346.0,
				"PositionY": 707.0
				    },
			 "Size": {
				"Height": 15.0,
				"Width": 152.0
				 }
		}
	      ]

For general information about the hyperlinks please have a look at: Hyperlinks

The email template configuration in the product changed. Also some new placeholders were added. For more information please have a look at: Settings and Customizing

or in the product in the following section: Settings->Email Templates, there you will find a new section with all possible placeholders for each template. You can copy the placeholders and past it in your template.

The sender of an envelope can define wether the recipient of the envelope has access again after finishing and closing the envelope. For more information about the process of opening documents and finishing them please have a look at: Signer Guide

Links are now supported in the disclaimer dialog. For  more information please have a look at: Beginner Guide

You can now choose between the following five configurations for a Batch signature:

• Simple Batch
• Signature List (unselected)
• Signature List (preselected)
• Signature List (selected, required mandatory)
• Signature List (unselected, required mandatory)

We added the last two modes for mandatory fields (selected and unselected). This makes it possible to distinguish between mandatory and voluntary fields.

Therefore, the selected means that the user can select/deselect only signatures which are not required. All signatures are initially selected. The unselected means that the user can select/deselect only signatures which are not required. All non required signatures are initially deselected.

For more information please have a look at Signer Guide

PAdES configurations were added to the organization settings. There you can choose between the following levels:

• B
• T
• LT
• LTA

For detailed information please have a look at Settings and Customizing

There you can find all descriptions for the different levels.

You can now configure an A-TRUST signature in your workstep configuration. For more information please have a look at the Beginner Guide

In this guide you can also find a sample configuration for an A-TRUST signature.

If you are using eSAW on premise or in a private SaaS and use the SIGNificant Kiosk, you can use new features now:

• Combobox
• Listbox

The API caching now returns cached results in the case the same request is executed again too fast (e.g. after just some milliseconds).

The viewer supports new batch signature options, where the signer gets a list of the batch signature, either preselected or deselected. The original batch signature dialog is still available.

The new license management allows you to set warning notifications if the license or the envelope limit expires. You can even set a callback for an envelope limit warning.

If you are using eSAW on premise or in a private SaaS and use the SIGNificant Kiosk, you can use new features: SMS-OTP, Disposable and a PushTan integration.

You can easily change now holder information and validate the information in advance.

If you are using callbacks for your integration, you can set now basic authentication for your callbacks. Moreover, you define a pattern to define different callback-authentications.

The SAW Viewer allows now a local certificate verification.

We improved again the performance of our solution to provide you an excellent user experience.

We redesigned the SAW Viewer to enhance the usability and user experience. For more details check the special SignAnyWhere Viewer 2019 page.

We optimized the usage of the disposable certificate and how it is integrated.

We reworked the team feature, due some customer feedback. We optimized the sharing between teams, to prevent the sharing of all documents of two (or more) teams with a shared team-member. Moreover a hierarchy is now possible: (1) see all documents up & down or (2) see documents only down (“team lead”, but not seeing sent documents of my manager).

You can now view and export your organization’s statistics in the license section of the settings (accessible for user managers).

You can now access the license data via API. For SOAP we have the GetLicenseState_v1 and for REST V4+ V4/license. The response will be the type of the license, expiration date, status about the documents and users.

We added a new API call to unlock a parallel recipient to be opened by others again. Older versions only allowed it manually via UI, now you can integrate or automate it yourself. SOAP is called UnlockEnvelope_v1 and REST is called V4/envelope/{envelopeId}/unlock.

We added a new SAW Viewer Policy AutoStartGuiding, which allows you to start automatically the integrated guiding. This enables a use case, where the document loads and directly jumps to the first signature field.

We improved the UI of eSAW to allow a better user experience (e.g. license page).

We changed the default email template to a new one. For existing organizations, the set template will not be changed, just for new organizations or if you reset the template.

We integrated the Swedish BankID for authentication. Please contact us if you want to know more about it.

We improved the overall systems performance (database optimization, document processing, data management).

You can now optionally attach the document to the audit trail. So you have the final & signed document as PDF attachment in the audit trail. Note: this will increase the size of the audit trail.

This feature is only available via API in the <envelope> section, per default it is disabled (0).

<attachSignedDocumentsToEnvelopeLog>1</attachSignedDocumentsToEnvelopeLog>

You are able to overwrite the signature disclosure (set up via eSAW UI in the organization settings) via API. So you can define unique information per envelope or recipient (e.g. for internal users disable the signature disclosure).

This is configured via API in the <step> section of the envelope.

<step>
  ...
  <useDefaultAgreements>true</useDefaultAgreements>
  ...
</step>

useDefaultAgreements – true (default value): use the default signature disclosure of the organization (the configuration in the workstepConfiguration is ignored)

useDefaultAgreements – false: use the setting of the workstepConfiguration (overwrite). If the config is empty, no signature disclosure is set for the recipient.

Optimization of the on-premise setup of eSignAnyWhere.

Improvements of SAW Viewer

• Optimized mobile OTP forms
• BankID support
• Added check for enabled cookies
• Added disposable certificate disclaimer text (FR/PT)
• New languages: Polish, Chinese
• Security enhancement
• Fixed QR code for SoP (had some issues with some browsers)
• Optimized tablet view of the menu
• Optimized image generation for Click2Sign, Draw2Sign and Type2Sign

via Hotfix

• Reject message can be empty
• FinishAction also for Reject and Delegate
• fixed Translation issues

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

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.

Improvements 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.

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.

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

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

• Security Improvements (CSS, Input Validation, brute-force PIN prevention)
• Visual optimization of the disposable certificate form
• New Language: Bulgarian
• New viewer preference: PhoneNumberInputSettings
• Technical: switched to XLIF format for language support
• fixed some UI bugs

via Hotfix:

• fixed Draw2Sign & Type2Sign placement
• fixed QR code for SoP for some browsers

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 Beginner Guide.

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.

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.

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

Automatic Delegation is an advanced feature, which allows the user to define an 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.

• UI optimized resizing of window behavior
• Open source information added in the SAW Viewer
• Fixed biometric signature under certain use cases
• Optimized UI for authentication
• Error handling of uploading attachments improved
• Improved error messages
• Device Driver UI optimized
• bugfix for batch signature

via Hotfix:

• fixed some translations
• fixed navigation bar, when maximizing window
• fixed rejecting of document for specific use cases

Bulk envelopes allow 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 letting 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 Bulk Use Case.

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 Beginner Guide.

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

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

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

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.

• form field validation
• added undo option
• added languages: Spanish, Portugese
• updated translations
• improvements for local certificate signing
• allow configuration of date format for picture signature types
• fixed UI issues for some devices (mobile, tablet or browsers)
• fixed device driver issues
• fixed attachment with hidden documents
• fixed Finish button visibility after finished document
• fixed error for some specific policies
• fixed the guiding for disabled elements
• fixed local time issue

via Hotfix:

• fixed a finish document issue
• fix batch signature with OTP issue
• optimized Device Driver integration

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.

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.

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” checkbox in the eSAW UI (and it is renamed to support also acknowledge recipients).

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

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

Set in the WorkstepConfiguration (for a recipient) the following Task (in workstepConfigurationPolicyWorkstepTasks):

<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>

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

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

Advanced document tags now support an 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 the right and positive values y are moving up. e.g.

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

• support of hidden documents
• support for confirm reading
• reworked rendering of some signature types (local certificate, remote signature, disposable signature)
• fixed OTP signature issue with wrong OTP
• reworked zoom handling
• fixed a delegation issue (delege to yourself)
• optimized UI for devices (mobile, tablet, browsers)

via Hotfix:

• fixed translations
• reworked visual appearence of attachments
• added new viewer policies for customization
• fixed UI in landscape for mobile devices
• fixed OTP handling & errors
• fixed OAuth/SAML with a port in configuration
• upgraded Device Driver protocol level
• fixed a batch disposable certificate issue
• enhancements for debug mode
• client server communcation optimization (e.g. retry for calls)

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)

You can use SAML to authenticate signers in the SignAnywhere Viewer (Signer Interface). You configure the SAML provider 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.

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

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

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

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

E.g. userId=123 of provider CustomOAuthService has to authenticate. If another user authenticates it is rejected. Just a 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.

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.

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.

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

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

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 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.

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.

GetEnvelopeById contains the reason about rejection or delegation.

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

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