...
Self | A recipient with the sender himself as signer is configured. |
Automatic | See chapter “Automatic Sealing” |
Bulk | Sends Ref to chapter “Bulk Sending” |
Personal message and Language Settings
Via the Icon (
), the personal message and language settings area can be expanded. In this area, the sender can define for each recipient in which language the recipient specific notifications should be sent, and which text should be inserted in the signer invitation as "personal message" in case the personal-message placeholder was used in the text.
All active languages as defined in Settings-Localization can be selected as recipient language. See Localization Settings for more details. But note that a recipient's configured language in the account settings is considered, in case the recipient has a user account on the same instance (not necessarily within the same organization). The configured recipient language will be ignored in this case.
Details for Authentication
Additional Details
Parameters for Digital Remote Signature
Parameters for Disposable Certificate
| Info |
|---|
The screen shows the field "Document Issuing Country", which is available as input field when the mode for disposable certificate was configured to use the "Lean Disposable Certificate", which is our recommendation. Note that the value "Nationality" will be requested, when using the (deprecated) classic disposable type instead. |
Parameters for SMS-OTP Signature
Similar as for the SMS Authentication or the mobile phone number in the parameters for the Disposable Certificate, the phone number is automatically kept in sync with the recipient's primary phone number by default. When a different phone number should be used, select the toggle button labeled as "custom", and define a specific phone number for late authentication via SMS-OTP when performing an SMS-OTP signature.
The value can be kept empty (via recipient's primary phone number, or by setting a custom number and deleting the value). In this case, the signer is asked to enter his own phone number; still with the evicence of used phone number in the audit trail.
Parameters for Swisscom On-Demand Certificate
Document Visibility Section
...
Please also see the next table which contains all available placeholders for the message section:
| Placeholder | Description |
|---|---|
| #ContactUrl# | The URL refers to the company’s contact info, which is defined in the organization settings. |
| #EnvelopeMessage# | The message which is defined for the envelope. It may contain the personal message defined per recipient. |
| #EnvelopeName# | The name of the envelope. If not specified differently, it is by default the file name of the first PDF document. |
| #ExpirationDate# | The expiration date of an envelope. The date format is defined in the user account settings. |
| #PersonalMessage# | The personal message for a recipient. It may be included in the general envelope message if it was defined before. |
| #RecipientEmail# | Email address of the envelope recipient. |
| #RecipientFirstName# | First name (given name) of the envelope recipient. |
| #RecipientLastName# | Last name (surname) of the envelope recipient. |
| #SenderFirstName# | First name (given name) of the envelope sender. |
| #SenderLastName# | Last name (surname) of the envelope sender. |
| #SupportUrl# | The URL refers to the company’s support website, which is defined in the organization settings. |
| #Url# | The context specific URL used in a link button to execute an action (e.g. URL for Login, URL to open an envelope, URL to download documents, etc.). |
| #UrlAndroid# | The URL to open a signing request in the Significant App Client Signature Capture for Android. |
| #UrlIos# | The URL to open a signing request in the Significant App Client Signature Capture for iOS. |
| #UrlWindows# | The URL to open a signing request in the Significant App Client Signature Capture for Windows-Store. |
| #UserFirstName# | First name (given name) of a user, who is either the web UI user or the envelope sender(depending on the context). |
| #UserLastName# | Last name (surname) of a user, who is either the web UI user or the envelope sender(depending on the context). |
Meta Data Section
The metadata section allows to set meta data in free-text format, which are accessible for an integration e.g. in a Callback Handler. We recommend (but do not enforce) to fill the data with a valid XML structure.
...