2.1 Configuring the connector
The behavior of the Salesforce connector can be configured by a Salesforce user who has the connective-admin permission set. This chapter will highlight the configuration that may impact user experience for the end user.
If you want any of these settings adapted, reach out to your Salesforce connector sysadmin.
Are you an Salesforce administrator and do you need help configuring the connector? Contact service@connective.eu.
Schedules settings
The Schedules settings allow to define the automatic batch job for updating document statuses.
It is also possible to request a manual status update. To do so, navigate to the required document and click Refresh Status.
Name | Description |
---|---|
Number of times | The number of times per day that the batch will update the open packages. |
Activate Schedule | Enable or disable the automatic batch. |
Assign default owner | The default owner that uploads a signed document (either through the batch or manually). If left empty, the currentUser will be the default owner. |
Environment settings
The Environment settings will apply to the complete Salesforce org.
Name | Description |
---|---|
Enforce Standard Values | This parameter allows to enforce default values set within the configuration. If enforced, an initiator will not be able to adapt the default values set in the configuration. (They will be greyed out or hidden.) |
Use Automatic Signing Fields | When activated, the initiator will not need to define the signing fields to be used per signer. Following principle will be used: • Document 1 – Signer 1 --> Marker SIG01 • Document 1 – Signer 2 --> Marker SIG02 • Document 1 – Signer X --> Marker SIG0X • Document 2 – Signer 1 --> Marker SIG01 • … Please note that it is up to the initiator to ensure that the document contains the correct markers. If the required markers are not present, it will result in an error during the upload process. |
Hide Group Code Fields | Allows to disable the choice of the document group code during the upload process. |
Document group settings
The Document group settings allow to configure the user experience per document group. It is possible to provide a general setting (on Default Settings Document Group) or to define the specific parameter per document group. The standard practice is that if no Document Group Specific parameter has been set, the Default Settings Document Group apply.
Name | Description |
---|---|
Standard Mandated Signer Method | Allows to set the standard Mandated Signer Method in the upload process: • Disabled • NameAndBirthDate • MatchID For an explanation on what the mandated signer functionality does, please see Mandated Signer. |
Standard Legal Notice | Allows to set the default Legal Notice to be used in the upload process • Disabled • LegalNotice1 • LegalNotice2 • LegalNotice3 LegalNotice1 / LegalNotice2 / LegalNotice3 are legal notices that can be configured within eSignatures. LegalNotice1: Read and approved LegalNotice2: Read and approved for [AMOUNT] EUR. Signed at [PLACE] on date [DATE] LegalNotice3: Guarantor liable for an amount of [AMOUNT] EURO for [TOPIC] |
Standard Signing Sequence | Allows to set the default signing sequence to be used in the upload process: • Parallel • Sequential |
Standard Expiration Time (in days) | Allows to set the default Expiration Time to be used in the upload process. If the value is set to 10, the default Expiration Date will be today +10 days. |
RedirectUrl | Allows to set the RedirectUrl to be used. |
CallbackUrl | Allows to set the CallBackUrl to be used. |
Initiator | Allows to set the default initiator to be used when uploading a document. If no default initiator is used, the currentUser will be the initiator during the upload process. Note: the initiator has to be a registered user on the eSignatures platform. |
Hide... Field | Allows to hide fields from the initiator – to be used in combination with Standard Values. Following fields can be hidden • Mandated Signer • Expiry Date • Group Code • Legal Notice • Signing Sequence |
Manual Signing Location | Allows to define (two) default signing field definitions (when Automatic Signing Fields are not used. It is possible to define either a Marker or to define a position. |
Restrict the Signer | When activated, the initiator will only be able to see contacts that are linked to the account to which the object where the signing process is initiated is linked to. E.g. Signing flow is started from an opportunity for account ABC > You will only see contacts that are linked to account ABC when adding a signer. The restriction does not apply to receivers. |
Allowed Signing Methods | Allows to define which signing methods are available for the initiator during the upload process. For SMS: it is possible to define the default Mobile Country Code. This will be used to append to the Mobile Phone value of your contact when the country prefix is not present in the Mobile Phone field. E.g. Contact has a mobile phone number: 04xx xxx xxx > Using the Mobile Country Code parameter, the connector will automatically set the phone number to +32 4 xx xxx xxx. Note: The signing method must be active on the eSignatures platform. Check with Connective Support in case of any doubts. |