...
Section | ||||
---|---|---|---|---|
|
Section | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | |||||||
---|---|---|---|---|---|---|---|
|
Section | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | |||||||||
---|---|---|---|---|---|---|---|---|---|
|
Section | |||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | |||||||
---|---|---|---|---|---|---|---|
|
Section | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | |||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | |||||||
---|---|---|---|---|---|---|---|
|
Section | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | |||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | |||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | |||||||
---|---|---|---|---|---|---|---|
|
Section | |||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | |||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | |||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | ||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | |||||||
---|---|---|---|---|---|---|---|
|
Section | |||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | ||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | ||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | |||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | ||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | |||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | |||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Section |
Column | ||
---|---|---|
| ||
Documentation change
Date: September 2021
Expand | ||
---|---|---|
| ||
Detailed documentation about how to configure SAML authentication for user authentication and signer authentication has been updated in the following guide: SAML Guide |
Column | ||
---|---|---|
| ||
Documentation change
Date: August 2021
Expand | ||
---|---|---|
| ||
The documentation about metadata and the AdditionalClientWorkstepInformation has been updated in the following guide: Beginner Guide |
Column | ||
---|---|---|
| ||
Feature Release
eSignAnyWhere 21.27
In preparation
Date: Expected 24 August 2021
Expand | ||
---|---|---|
| ||
We improved again the performance of our solution to provide you an excellent user experience. |
Expand | ||
---|---|---|
| ||
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: |
title | SwissCom OnDemand Certificate UI |
---|
The SwissCom OnDemand Certificate is now also available in the UI. You can find the settings for the SwissCom OnDemand Certificate in Settings → Organization.
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).
After these configurations you can use the SwissCom OnDemand Certificate as signature field in the UI:
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 FieldsExpand | ||
---|---|---|
| ||
The recipient who has to view the document was renamed to "Must view" recipient instead of "Acknowledge" recipient. For example: |
Column | ||
---|---|---|
| ||
Feature Release
eSignAnyWhere 21.16
Date: April 2021
Info |
---|
Please note: For detailed information about the 21.16 features please also see this release notes document. |
Expand | ||
---|---|---|
| ||
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. |
Expand | ||
---|---|---|
| ||
Organization administrators can now customize localization (especially text translations) per organization. It enables a higher level of customization and more adjustments of the SignAnyWhere Viewer (Signer Front-End). The front-end can now be adjusted to the company’s common wording. |
Expand | ||
---|---|---|
| ||
The organization administrator can now define filters on intended-use of certificates, for envelopes containing local certificate (SmartCard) signing experience. With that filter configured, the list of selectable certificates can be restricted to the certificates relevant on a local market (e.g. if a local signature smartcard contains two or more certificates for different purposes, like signing and identification). |
Expand | ||
---|---|---|
| ||
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) 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: 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: |
Expand | ||
---|---|---|
| ||
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. |
Expand | ||
---|---|---|
| ||
A new dialog will let you choose between bulk recipients added in an envelope draft and bulk recipient list defined in a template. For example: If you add a template with a bulk to an envelope which already has a bulk included you will be asked if you want to continue with the bulk from the template or with the bulk from the envelope. This will help you with the process flow of bulk sending as you can now differentiate between the bulks of different envelopes. |
Expand | ||
---|---|---|
| ||
With custom signature rendering layout configuration (stamp imprint configuration), an organization administrator can define how the stamp imprint on the signature image looks like (e.g. fonts, elements, layout etc). The new functionality allows to set organization wide background images (e.g. company logos) or define specific fonts for text added to the stamp imprint. While it has no impact on the legal levels of signatures (in EU, defined by eIDAS), a customer specific stamp imprint representation can create higher subjective trust and contract awareness of your customers. |
Expand | ||
---|---|---|
| ||
This feature clears up ambiguities in the UI. Only those features are displayed which are actually possible with the given settings. Non-accessible features will be hidden to optimize the UI experience. |
Expand | ||
---|---|---|
| ||
The “Generic Signing Plugin” (GSP) allows implementation of custom 3rd party signature creation implementations (HSM based, web service based, etc). It is typically used to integrate external CAs into eSignAnyWhere. A GSP based implementation of a 3rd party CA is available for envelopes created via eSAW API or via eSAW WebUI. New features and improvements allow wider usage of the GSP. |
width | 150px |
---|
Column |
---|
LTS ReleaseeSignAnyWhere 20.76 ("21 LTS")Date: April 2021 LTS version based on the feature release version 20.52. |
Column | ||
---|---|---|
| ||
Feature Release
eSignAnyWhere 20.52
Date: December 2020
Expand | ||
---|---|---|
| ||
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 |
title | Force 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 | ||||
---|---|---|---|---|
| ||||
"ViewerPreferences": {
"AcceptAgreementDisabledUntilRequiredActionsDone": true,
"VisibleAreaOptions": {
"AllowedDomain": "*",
"Enabled": false
} }, |
Expand | ||
---|---|---|
| ||
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:
Organization Import There are two options for organization import:
The update process will skip updating the settings below (even if they are in the xml file) since they can affect ongoing/draft envelopes.
Note: Data such as envelopes, address book etc. are not supported with the export/import of the organization. |
Expand | ||
---|---|---|
| ||
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. |
title | New 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.
Column | ||
---|---|---|
| ||
Documentation change
Date: November2020
Expand | ||
---|---|---|
| ||
The Beginner Guide has been expanded to include the following: In the section “signatures” you can now also find an example (REST/SOAP) of a StampImprintConfiguration. |
Expand | ||
---|---|---|
| ||
The Use Case Example Template has been expanded to include the following: In the section “Override Radiobutton” you can now find an example (REST/SOAP) of how to override a radio button from a template. |
Column | ||
---|---|---|
| ||
Feature Release
eSignAnyWhere 20.42
Date: October 2020
Expand | ||
---|---|---|
| ||
This plugin provides a generic way of integrating external (remote) signatures. Please see the following supported features:
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. |
Expand | ||
---|---|---|
| ||
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:
For more information about the
|
Expand | ||
---|---|---|
| ||
You can now also use the driving license as an identification type. This new identification For more information about the disposable certificate please also have a look at the Beginner Guide. |
Expand | ||
---|---|---|
| ||
We improved again the performance of our solution to provide you an excellent user experience. |
Expand | ||
---|---|---|
| ||
We declared SOAP as deprecated and therefore SOAP will not be included in versions after 21.76 (already postponed by one year, initially the 20.76 was announced). Latest release including SOAP API for eSAW will be 21.76, released in spring 2022 and with the software maintenance on 21.76 until spring 2024. Therefore, we recommend REST technology for integration. Please see also the migration guide. |
Expand | ||
---|---|---|
| ||
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
Please see also this guide: Bulk signing assistant |
Column | ||
---|---|---|
| ||
Feature Release
eSignAnyWhere 20.28
Date: July 2020
Expand | ||
---|---|---|
| ||
We declared SOAP as deprecated and therefore SOAP will not be included in versions after 21.76 (already postponed by one year, initially the 20.76 was announced). Latest release including SOAP API for eSAW will be 21.76, released in spring 2022 and with the software maintenance on 21.76 until spring 2024. Therefore, we recommend REST technology for integration. Please see also the migration guide. |
Expand | ||
---|---|---|
| ||
In addition to the predefined roles and permissions you can now define your own roles. So, for example you can define a new role, where the user can manage and send envelopes, but not create the envelopes on their own. Or a role which can configure automatic remote signatures themselves, without being user managers. Moreover, you can also set the permissions for your roles. For more information please have a look at this page. |
title | Lock form fields |
---|
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:
Code Block | ||||
---|---|---|---|---|
| ||||
"LockFormFieldsAtEnvelopeFinish": true, |
Or in SOAP:
Code Block | ||||
---|---|---|---|---|
| ||||
<lockFormFieldsAtEnvelopeFinish>true</lockFormFieldsAtEnvelopeFinish> |
Expand | ||
---|---|---|
| ||
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
For more information please have a look at this page. |
Expand | ||
---|---|---|
| ||
You can find this feature in your organization settings in the section “Testing Phase Features”. For more information about the clipboard please have a look at this page. |
Expand | ||
---|---|---|
| ||
You can now configure a bankID signature field and a bankID authentication via api. For more information about bankID and the configuration please have a look at this page. |
Column | ||
---|---|---|
| ||
Feature Release
eSignAnyWhere 20.14
Date: April 2020
Expand | |||||||
---|---|---|---|---|---|---|---|
| |||||||
You can now define hyperlinks for your document with API. The next lines of code show you a sample configuration of one hyperlink:
For general information about the hyperlinks please have a look at: Hyperlinks |
Expand | ||
---|---|---|
| ||
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. |
Expand | ||
---|---|---|
| ||
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 |
Expand | ||
---|---|---|
| ||
We improved again the performance of our solution to provide you an excellent user experience. |
Expand | ||
---|---|---|
| ||
Links are now supported in the disclaimer dialog. For more information please have a look at: Beginner Guide |
Expand | ||
---|---|---|
| ||
We recommend REST technology for integration. However, we will offer SOAP as well and SOAP is still being maintained. When we decide to declare SOAP as deprecated in the future, we will publish further information on this page. In this case, we will grant enough time before SOAP gets discontinued. |
width | 150px |
---|
LTS Release
eSignAnyWhere 19.76 ("20 LTS")
Status: In preparation
Date: April 2021 (Release Candidate)
LTS version based on the feature release version 20.52.
Column | ||
---|---|---|
| ||
Feature Release
eSignAnyWhere 3.7
Date: January 2020
Expand | ||
---|---|---|
| ||
You can now choose between the following five configurations for a Batch signature:
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. |
Expand | ||
---|---|---|
| ||
PAdES configurations were added to the organization settings. There you can choose between the following levels:
For detailed information please have a look at Settings and Customizing There you can find all descriptions for the different levels. |
Expand | ||
---|---|---|
| ||
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. |
Expand | ||
---|---|---|
| ||
If you are using eSAW on premise or in a private SaaS and use the SIGNificant Kiosk, you can use new features now:
|
Expand | ||
---|---|---|
| ||
The API caching now returns cached results in the case the same request is executed again too fast (e.g. after just some milliseconds). |
Expand | ||
---|---|---|
| ||
We improved again the performance of our solution to provide you an excellent user experience. |
Here you can find all previous releases:
|
Section | ||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | ||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Section | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...