1. We need to Integrate Echosign API with vTiger 5.4 as a Module
We would prefer that a module be created to accomplish this. In this regard, we can use the module in multiple other instances of vTiger that we will be utlizing.
2. From vTiger we need to send the PDF files to customers requesting a digital signature.
In vTiger, we use PDFMaker to generate PDFs for quotes, invoices, contracts..etc. The digital signature needs to be on "any" generated PDF. We will send a number of documents from vTiger to a customer "requesting" a digital signature from them.
SugarCRM has an Adobe Echosign module, that is a great example of what we need. Info can be found below about the module. You can also look at the SugarCRM demo to see it in action.
[url removed, login to view]
Echosign Documentation can be found here. [url removed, login to view]
The SugarCRM module provides a button that says "Send for Signature". In our case, when we click that button in vTiger, it should then use the PDFMaker code to generate the PDF and send it to a recipient (customer) to request the digital signatre.
PDFMaker documentation can be found here. [url removed, login to view]
3. From vTiger we need to send document out for signature through the Echosign API.
All functions of the API such as sender info and document creation info, etc. must be used. You will see all the API call and attach functions in the API documentation.
4After a document is sent, we must be able to retrieve up-to-date status of the document either by polling, or when Echosign notifies the recieving parties that the status of the document has changed.
5. When the document status is “Signed”, we want to retrieve the signed PDF document PDF via the API Call and store it in vTiger.
The document (once signed) should be routed back to out vTiger. We need to work the details out on how the document will be handled once it arrives back to vTiger. Our thoughts are that some kind of workflow could be created that would do the following;
a. Based on the Last Name/First Name and Company listed on the document, then
b. Convert to an account and attach the PDF to the new customer account.
For now, due to time constraints and costs, documents should be sent to the vTiger documents area and properly named for easy customer association and retrieval.
6. We will provide a test API key. The module should be built in such a way that it asks you to add the API information e.g.;
a. The API Key
b. All required API account information
We currently have an Echosign test account with a test API Key. Once the module has been created and successfully tested, we can then retrieve the live API key which should not be a difficult task to update the code with new API key.
IMPORTANT Additional Info: (If you cannot agree to the folowing - Please do not bid)
1. Any coder/programmer and/or company working on this will freely sign an NDA including copyright with us (this is a MUST).
2. Documentation on the module once created, e.g.; How it's built, copy of the code..etc.
We have additional work that will need to be done once this is complete so please keep that in mind when bidding. Good pricing plus good working relationship and timeliness = More Work
We are mindful that there are better ways of doing things so we are open to suggestion.
2 freelance ont fait une offre moyenne de 778 $ pour ce travail
Hi We are CRM/ERP/POS/Custom Software solution providing company So we are really interested to deliver this project. For more details please see your PM. Regards AuricleSoft
Hi, We have good experience in vTiger. We have implemented and customized various modules in vTiger. We are also providing support to companies. Please let me know how we can proceed? Regards, Manish