eSignature API > Stories > The New Car

eSignature eSignAnywhere - Use Case Example: The New Car

The Story

Alice and Frank want to buy a new car. So they are going to the local car dealer to look and check the models to buy one. The car dealer is using eSignAnywhere for digital signing. You find a list of available stories here.

Use Case

  1. The contract is prepared via salesman on his computer. He enters the data, discount, payment methods and additional data
  2. The salesman opens the contract on the tablet pc via
    1. Option (1): Email – an email with the link to the document is sent to the tablet. The salesman clicks on the link to open the document in the SIGnificant app for signing.
    2. Option (2): QR Code – a QR code is shown on the computer of the salesman and scans it via tablet to open the document in the SIGNificant app
    3. Option (3): a company notification system is used to push the link for the document directly to the tablet
  3. Alice and Frank are signing in the native app on the tablet (in this example via biometric signature)
  4. The document is finished and synchronized with the server (via salesman)
  5. The computer of the salesman shows the finished document and Frank receives a copy of the contract via Email. Optionally the salesman can now print a carbon copy for Alice and Frank
Information

This example uses the native SIGNificant App (for Android and iOS) and requires an eSignAnywhere Instance with an open Workstep Controller Process interface. This is available at http://demo.xyzmo.com, so it is recommended to create an free account at http://demo.xyzmo.com for testing this example or use your own on-premise or private-SaaS eSignAnyhwere instance.

Note: Due the security limitations, this example will not work on http://significant.com. Please use http://demo.xyzmo.com instead. The following example and description uses the endpoints of http://demo.xyzmo.com.

Integration

The integration of this use case requires eSignAnywhere and the SIGNificant App on the tablet. Due the integration of the native App, this integration is a little bit different from eSignAnywhere-only integrations.

The creation of the workflow is similar, except that in one step (so one recipient) two persons are signing at once (“hosted meeting”). This is done via the use of the native SIGNificant App. Therefore no authentication is required. Moreover, this scenario is perfect for biometric signatures (advanced electronic signatures) and due the biometric signatures it doesn’t require any authentication.

To bring the document to the tablet there are some options available:

  1. Email: a email is sent to the tablet and opened by the salesman. The email contains a link, which opens automatically the app and the document for signing.
  2. QR Code: on the computer of the salesman is a QR code shown, after the creation of the workflow. The salesman is opening the SIGNificant App and scans the QR code. The app opens automatically the document for signing. In this option there is no email sent in the first signing step.
  3. Custom Notification: a custom notification is used to push the link to the tablet. In that case an even deeper integration (via SIGNificant App SDK) can be used. This means on the tablet is specific car dealership app installed, which has integrated the SIGNificant App SDK for signing. This specific car dealership has integrated the notification service and gets the information for signing task and automatically opens the document for signing.

This example shows two integration for option 1 (Email) and option 2 (QR Code).

Example with Option (1) Email

The workflow is the following:

  1. Create the PDF based on the data provided by the salesman in the car dealerships CRM
  2. Upload the PDF to eSignAnywhere via UploadTemporarySspFile
  3. Prepare the envelope XML and set CC recipient
  4. Send Envelope via SendEnvelope
  5. Open the tablets email inbox and click on the link of the eSignAnywhere email
  6. Frank and Alice are signing & finishing the document in the App
  7. Frank recieves and copy of the document via Email
  8. The callback is used to update the car dealerships CRM
Download - Option 1: Email

Download Files for Example Option 1 - Email: CarContract.pdf, SOAP UploadTemporarySspFile, SOAP SendEnvelope

Example with Option (2) QR Code

Workflow:

  1. Create the PDF based on the data provided by the salesman in the car dealerships CRM
  2. Upload the PDF to eSignAnywhere via UploadTemporarySspFile
  3. Prepare the envelope XML and set CC recipient
  4. Send Envelope via SendEnvelope (with disableEmail=true for first recipient)
  5. The returned envelopeID is used to call GetEnvelopeById to retrieve the envelope status. The first recipient contains the workstepRedirectionURL for the signing task. This URL forwards to a HTTP forward to the SignAnywhere Viewer (Web-Client), but we need the workstepId for the App. Therefore you have to add to the WorkstepRedirectionUrl an addional parameter to get it directly (&responseType=returnWorkstepId).
  6. The car dealership CRM shows the QR Code for the signing task. The salesman scans the QR Code from the display via SIGNificant App to open the document
  7. Frank and Alice are signing & finishing the document in the App
  8. Frank recieves and copy of the document via Email
  9. The callback is used to update the car dealerships CRM

Retrieve WorkstepID and generate the QR Code

The first recipient in this example is the tablet. The SIGNificant App requires the workstepId for signing the document. After you created the envelope (SendEnvelope) you do the following:

  1. Call GetEnvelopeByID(envelopeId) to retrieve the status of the envelope
  2. The response contains the workstepRedirectionUrl in envelopeStatus > bulkRecipients > bulkRecipient > recipients > recipient > workstepRedirectionUrl. This URL is the link to the SignAnywhere Viewer (Web-Client), which forwards to the eSAW redirector and delivers a link with a workstepId parameter. With the additional parameter&responseType=returnWorkstepId you directly receive the workstepId:
    https://demo.xyzmo.com/workstepredirector/sign?identifier=8WNDxmUVr5V/aV1AAN49xjKuVsHMQEIQVuM/ktLNw1jOfWgaovF2mDg3uW9JJbp5Q/k7Yz92eoo=&responseType=returnWorkstepId
  3. Extract the workstepID from the response.
  4. Prepare Data for QR Code: the QR Code contains a link to the server and the workstepId (Signing-Task). So you have to use the extraced workstepId to build a link (replace ##WORKSTEPID##):
    http://launch.xyzmo.com/SignificantAndroidAppLauncher.aspx?WorkstepId=##WORKSTEPID##&server=demo.xyzmo.com/WSCProcess&protocol=https
  5. Generate a QR Code with that link (e.g. with a proper QR Code library, as example you may use a offline QR Code Generator [https://sites.google.com/site/qrcodeforwn/home/qr-code-generator-for-wireless-networks]).
  6. Show the QR Code and scan it with the SIGNificant App (Button lower left above settings  symbol)
Download - Option 2: QR Code

Download Files for Example Option 2 - QR Code: CarContract.pdf, SOAP UploadTemporarySspFile, SOAP SendEnvelope, SOAP GetEnvelopeById, Info.txt