Versions Compared

Old Version 43

changes.mady.by.user Unknown User (gierlinger)

Saved on

compared with

New Version 44

changes.mady.by.user Unknown User (gierlinger)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Section


Column
width150px



Column

Feature Release

eSignAnyWhere 20.52

Date: December 2020

Expand
titleDraft API calls for addtitional integration scenarios
You can now create, update and send a draft via API. Therefore, with the new API calls you can prepare an envelope and send it at any time. Before sending you can also update the draft if some configuration should be changed.
For more information about how to create and send a draft via API please have a look at the following guide: Use Case Example Draft


Expand
titleForce Download/Print electronic agreement

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:

Code Block
languagejava
themeEclipse
"ViewerPreferences": {
          "AcceptAgreementDisabledUntilRequiredActionsDone": true,
          "VisibleAreaOptions": {
            "AllowedDomain": "*",
            "Enabled": false
          }         },

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

Image Added

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:


Expand
titleExport/Import organization

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.


Expand
titleAnonymized log files
eSignAnyWhere and SSP from now on separates between an “anonymized” and a “full” log file. On-Premise customers can share with us e.g. for analysis purposes the anonymized log file. Whereas offering SaaS, where anyhow a data processing agreement should exist, Namirial still has access to both log files but it allows sharing the non-anonymized log file with more people inside Namirial while the logs which contain personnel information will still be accessible only for a very restricted number of employees.Note that messages in log files and the error text returned e.g. in API calls (but not the error codes) will change in order to be more data privacy friendly.


Expand
titleNew entry (disposable)

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.









...