Follow

Setting AssureSign Configuration Settings

Last updated 2017-01-09 15:51:25 UTC

AssureSign for Salesforce installs a tab that allows you to customize the default behavior of the AssureSign component within Salesforce. Some of the settings will come from your AssureSign account while others are based upon organizational preference. To access this tab:

  • Click the All Tabs arrow to bring up the list of available tabs (or "+" brings up all tabs on Lightning display)
  • Click the tab labeled AssureSign Setup
  • Click on the Configuration Settings sub-tab

You must un-check Use demo mode configuration settings in order to enter production configuration settings specific to your AssureSign account.

NOTE: Changes made to these configuration settings will affect all users of the AssureSign for Salesforce component within your organization.

Configuration Settings Terms

  • Context Identifier – The Context Identifier is an AssureSign account-specific string used in communicating with the AssureSign DocumentNOW service. This identifier can be found when logged into the AssureSign environment using an administrative user in the settings section.
  • Site URL – The web address of your AssureSign environment. See here for the URL.  This should match the URL where you log into AssureSign.
  • Choose Default Expiration - Offers the ability to use the Default Expiration setting in the AssureSign environment or override it. When AssureSign Default Expiration is selected, the default expiration is set by the AssureSign environment setting. Selecting Salesforce Default Expiration overrides the setting with the value set in theSalesforce Default Expiration box. The default expiration can always be overridden on the New Document page.
  • Salesforce Default Expiration - The default number of days after document creation that an unsigned/incomplete document will remain active/available for signing. Each user can override this setting in the New Document page of the AssureSign for Salesforce component when submitting documents to AssureSign.
  • Document Storage Location - The default location where completed documents should be stored if AssureSign is configured to deposit them back into Salesforce upon document completion. The options are to store completed documents as 1) an attachment to the related Salesforce object from which a document was launched, or 2) as a Salesforce document
  • Default Document Type - The default document selection to be selected when a new document submission is started on a Salesforce object within the AssureSign tool. The options are: 1) AssureSign Document – do not send a document to AssureSign, use the default document assigned to the Template stored on the AssureSign site, 2)Salesforce Document – look for a document to pass in the Document library within your Salesforce environment, and 3) Salesforce Attachment – look for a document to pass that is currently attached to a specific Salesforce entity (such as an account or contact).

NOTE: The “Default Document Type” setting will merely pre-select the selection when a new document submission is started, and is meant to be a time saver based on your organization‟s work practices. Users of the control will still be able to select the other options.

  • Allow Immediate Presentment – The Immediate Presentment option is used to specify whether documents can be immediately presented to a signer upon creation from the submitter‟s desktop. Immediately after a document is created it can be signed by navigating to Existing Documents, selecting a document by clicking on the document name and then clicking the Sign Document button. The signer must be selected from a list.

NOTE: If the AssureSign Template used as a basis for the signing session contains multiple signing steps, only signers assigned to the currently active step will be presented. You may want to disable immediate presentment if your document signers are not physically present with the document signer.

  • Document Contains Dynamic JotBlocks – The option to specify that the document contains dynamically defined JotBlocks allows you to make use of an advanced feature of AssureSign whereby sections may be embedded in a document that define new signature areas or alter the properties (such as location) of predefined signature areas in the template. For more information on how to embed Dynamic JotBlocks in documents, refer to the DocumentNOW interface guide available from the AssureSign reference guides list (this feature is available in version 2 and later interfaces). If your documents will not contain dynamic JotBlocks, then you should set this toNo. If a user selects Yes then documents are opened and parsed on submission to detect for the delimiting characters that define these areas; mistakenly selecting Yes will not cause issues.
  • Use demo mode configuration settings – Turning on demo mode will default some settings to access an AssureSign demonstration account. This mode allows you to use a limited version of AssureSign for Salesforce in order to try out the features against a sample template; you will not be able to submit documents matching your production AssureSign Templates, and no DocumentTRAK services will communicate with your system.

Users

Each of your Salesforce users that will use the AssureSign tool for Salesforce must have an AssureSign user account (an email address) that matches their Salesforce user email address.  At runtime, API calls to AssureSign are executed in the context of each user.  For example, each user will see only the AssureSign templates that they have access to.  And configurations that allow the sender of emails to be configured with the sender's user information require that each user have a unique AssureSign user account.

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.