The Recipients Page is used to define the general data of the envelope, and the signature workflow.
...
Additionally it is possible to configure the sealing certificate for the envelope. For more information please see Custom Sealing Certificate (since 23.49)
The agreement configuration is controlling if (and which) agreement texts are presented to signers and PKCS7 signers, after authentication in case an authentication method is configured. Please consider that agreement configurations are valid for signer activities only. In case of other activity types such as "Copy Recipient" or "Must View" activities, the acknowledge dialog is not displayed.
Please note: You can either use the organization agreement settings or configure a new agreement configuration for an envelope. Read Agreements Configuration about how to configure agreement texts on organization level.
...
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. Note: The user's interface language will be used (configured in account settings).
Personal Message
The text must be provided already in the language selected as "recipient language", otherwise the recipient will likely receive an email with some language mixture.
...
| Info |
|---|
The meta data section is available only when its usage is allowed in Organization Settings (Section "Recipient Settings", Flag "Allow to set envelope meta data"). In addition, the Meta Data section will be hidden when a "Default redirect url before sending a draft" is defined in Settings-Organization. A custom page before sending is a customer specific integration, which can e.g. implement a dialog asking for metadata in a specific format showing a convenient UI, instead of just expecting the sender to define a free-hand XML or other desired specific format. |
...
https://##domain##/AgentRedirect/index?draftid=##draftid##
iFrame
...
The allowed URL for iFrame integration should only contain a specific base URL without any route. Sample:
| Tip |
|---|
Valid URL: "http://www.example.com" |
| Warning |
|---|
Invalid URL: "http://www.example.com/additional_route" |
...