Configuring the DocuSign Web Import Service

You must configure the DocuSign import web service before DocuSign Connect can successfully save documents in your Laserfiche repository.

Note: The DocuSign integration is only used with the Laserfiche web client. It is not supported with the Laserfiche Windows client.

  1. Browse to C:\Program Files\Laserfiche\Web Import Services\DocuSignConnectService\Config and open Config.xml with a text editor.

    2. Tip: With an XML editor, you can point to the Config.xsd schema file for name suggestions to aid in editing Config.xml.

  2. Next to <LaserficheServer>, specify your Laserfiche server host name.
  3. Next to <LaserficheRepository>, specify your Laserfiche repository name.
  4. Next to <LaserficheUserName> and <LaserfichePassword>, specify authentication information. The DocuSign import web service logs in to the repository using this Laserfiche account and password. Leave these values blank to log in with Windows authentication using the identity of the DocuSignConnectServiceAppPool application pool in IIS.
  5. Configure the <Events> section to map DocuSign information to Laserfiche fields. The <Events> section contains 3 subsections which correspond to the events on the DocuSign Connect Settings page. The import web service supports the following event types:
    • <OnSignedEvent>: When a DocuSign envelope is completed.
    • <OnDeclinedEvent>: When a DocuSign envelope is declined.
    • <OnVoidedEvent>: When a DocuSign envelope is voided.

    In each subsection, add <FieldValue> elements to map DocuSign event values to specific Laserfiche fields. For example, if under <OnSignedEvent>, <FieldValue name="DocuSign Envelope Status">Envelope Signed</FieldValue> configures the integration to assign the DocuSign Envelope Status field to the document and sets the value to "Envelope Signed." In this example, the value is a static value, but you can use DocuSign tokens for dynamic information associated with the signed document. For a quick reference on available tokens,see DocuSign Tokens.

    Note: The import web service will not automatically create field definitions. Please make sure that any specified Laserfiche fields are already created in the Laserfiche repository.

    You can also configure a default Laserfiche folder to store received DocuSign documents. Next to<DefaultFolder>,specify the desired Laserfiche folder. You can specify a static folder, or use tokens to specify a dynamic path. For example, <DefaultFolder>\*Signing Completed\%(UserName)</DefaultFolder> configures the integration to retrieve user name that sent the signing request and creates a subfolder in the *Signing Completed folder.

    Note: The default folder only affects documents that did not originate from within the Laserfiche web client (e.g., using the Send option on the DocuSign website).

  6. Optional: In the <Features> section, next to <EnableApplicationLogging>, specify true if you want to log information in the Windows Event Log. <NotificationLevel> controls the amount of information you want logged in the Windows Event Log; valid options are:
    • Error: Only log major errors.
    • Warning: In addition to major errors, the integration also logs minor issues (e.g., field mismatch errors).
    • Information: Verbose logging.
    • None: No information is logged.
  7. Optional: In the <Features> section, next to <EnableAutomaticRetry>, specify true if you want the integration to automatically retry saving to Laserfiche if the initial attempt is unsuccessful. If the integration is unable to save to Laserfiche, the received DocuSign data is saved to disk in the FailedRequests subfolder of the DocuSign import web service installation folder.
  8. Optional: In the <ErrorNotifications> section, you can configure an email server. The import web service can send out email notifications when it is unable to complete importing DocuSign documents into Laserfiche. Set Enabled to true to enable email notifications.
    1. Similar to the <EnableApplicationLogging> element, you can control which level of errors will trigger an email notification. Modify the <NotificationLevel> element to one of the following options:
      • Error: Only notify on major errors.
      • Warning: In addition to major errors, the integration also sends email notifications on minor issues (e.g., field mismatch errors).
      • Information: In addition to errors and warnings, the integration also sends email notifications on retry attempts.
    2. Next to <EmailHost>, specify the name of your email server.
    3. By default, the integration can send a summary of errors every 15 minutes. Modify the <EmailInterval> value (in seconds) to control how often you want to receive error notifications.
    4. Next to <EmailUserName> and <EmailPassword>, specify how to log in to your email server. Leave the values blank to log in using the identity of the DocuSignConnectServiceAppPool application pool.
    5. In the <Recipients> section, add email addresses for error notifications.
  9. Optional: You can choose to encrypt the <LaserfichePassword> and <EmailPassword> values using the DocuSignConfigEncryptionToggle utility. This utility is installed in the same location as the Config.xml file. Run the utility from an administrator command prompt. Run the utility again to decrypt the value in order to modify the password values.
  10. Save your changes and close Config.xml.

ClosedSample DocuSign import web service Config.xml

Related Links