Developer forum

Hi Nuno,

I'm not quite sure exactly what you're trying to do. It seems to me that you're trying to do something like DocuSign to verify the identity of the submitter, but I'm not entirely confident.

Could you share some additional information?

- Jeppe

Hi Jeppe,

I did not want to constrain the answer to DocuSign, but that's exactly what the customer asked for.

TL;DR;

The requirement is multi-step "Create Account Form" (built for Forms for Editors) with 60+ fields integrated with DocuSign. We're looking into converting a paper-process into a digital one, so for that reason the customer wanted to have Digital Signatures in forms.

The form

Currently the prospect customer has 4 or 5 pages of information their customers have to fill manually and sign at the end, submit via fax or email and someone needs to type them. The goal is to convert as much as possible/reasonable to digital format.

We'll have to do something custom for sure, because we can have dozens of addresses and we're still trying to figure out if it's best to use "dummy" DW users OR customize Forms for Editors - it will depend on the balance between ease of development AND flexiblilty for configuration (emails, actions, conflicts/compromises with other customizations).

Ultimately we'll have a scheduled task to integrate the data with some NAV entities (completely custom). The customer is happy to have dummy Customer cards and/or Contacts and/or ShipTos... 

What we need

We need to offer some options and rough order of magnitude for a quote. Not knowing how an integration with DocuSignw would work, it's hard to say :P

Does that provide the information you were looking for?

Nuno Aguiar

Hi Nuno,

DocuSign is not something I'm too familiar with but they do appears to have a fairly well-documented API.

To solve the issue, you need to interface with DocuSign manually, which you already determined. I'm not sure if the form needs to be created in DocuSign or if their REST API is sufficient to just sign. If it is, then you only need a field to store the identifier of the signee. Otherwise, you need a notification subscriber that can sync the form with DocuSign. I don't think there is a notification for FormSaved in backend, so if it's required, we would need to add it first.

I don't think you need to create a user at the time of submit since you don't know if the prospect actually becomes a customer, but that depends on the workflow you expect to build around this functionality, I guess.

Other than that, I don't think I can provide much insight that you don't already have.

- Jeppe

Hi Jeppe,

Thanks for the insight. I'll see what we can get from the customer. Hopefully this is not what "makes or breaks" the project, meaning we should have some time to figure out the right solution.

In terms of notifications, the best one we've found (and worked on in the past) is onAfterSubmitSave. There are a few others, but less relevant https://www.screencast.com/t/1S9Md7LF

Worst case scenario we just need to delete the submitForm data if any custom development determines it should not have saved it in the first place. These situations do not come in very frequently, so I am not too concerned about this workaround, but thank you for proposing it anyway.

Thanks for your help,

Nuno Aguiar