I've been on DocuSign, google, and SO and can't find a combination of search terms to tell me what I want. Working in the API, is there a way to attach a couple of pieces of information to a recipient that would then belong to that recipient and be included in API callbacks?
For instance, I'm sending out four envelopes: signer, co-signer, dealer, salesperson. I'd like to attach a field to the recipient like "our_recipient_type" equal to one of those four values. That way, when DocuSign does a callback after someone signs, I get that piece of information in the JSON so I can easily close the loop on our side.
Note, I'm not talking about text tabs, not something the signer fills out. I'm talking about a piece of background information as a property of the object.
A simple solution would be to use text fields and have them with white font so they don't show in the document, but their values can be set/retrieved using the API.
A more advanced solution would involved custom fields (https://support.docusign.com/en/guides/ndse-user-guide-custom-fields) that can have more robust rules and can also be used to manage meta-data.
There are also envelope-level custom fields (text fields) that by definition do not show in the envelope and are meta-data for the entire envelope, not a specific recipient, but they can be used for this purpose as well if you want.
Related
I am building a send/receive message system. The messages may be created, replied and forwarded. The same blade file is used for all of them. For creation, every field title, body, recipient, attachment is empty but for reply, the recipient is the sender of the message. In forward recipient field is empty. Different situations for fields may happen based on the action.
This is my question, Should I create different blade files for every action or based on the action, I should put if else statement in the blade file and create the corresponding field?
Both approaches have its own drawbacks. for different blade files, It is difficult to maintain the web site. for example changing a color or something in UI, requires changing in every blade file.
thanks in advance.
I am working on an mobile application which allows user to post product to the server. I am getting user user id, zip, product info, price, condition and images. I could able to get the information of zip, price and condition by the following format and it works.
http://www.myproduct.com/products.php?user_id=10311&zip=77072&price=$13&condition=3
However it allows only 1024 characters. Therefore I am stuck how to send product info and images in that format. Any suggestions?
That's what I was searching today.
This might help you.
On a side note : POST method is a better way.
Try using hidden element to pass data between different pages.
Refer:
http://www.html-form-guide.com/php-form/php-form-variables.html
URL parameters are normally used to do gets instead of POST. Try using POST and put the name value pairs you wish to post into the body of the request. The body is not limited to the 1024 like the URL string is. Depending on the back end service the body can be an HTML form, and XML string, or JSON.
I have a database of different stores.
When a user clicks on a store name, I want an Ajax function to run displaying information about the store in a different div.
Information categories for all stores wll be the same: products carried, location, general information, etc.
I could easily make it so that each different store uses a different file name as an argument to the ajax function, and all files would have the same layout/format but with different data.
However i feel like this is bad form. How can i make it so that i have one fixed template and all that changes is the information specifics imputed into the template?
Please note that the store information display pages will also need to be able to have clickable links of their own (i.e. click on location and a google map pops up).
Is it something to do with XML? I dont know much about it.
Instead of returning a template, return the data.
So it says getstore.php?id=2 which returns a json string
{"name":"my store", "info" :"blah"}
Then you use java script to insert a new div, populated with that data.
I am creating a mobile guest list for a party that I'm having in a few months. All of the invites that I am handing out will have a custom QR Code on them, embedding their first and last name. When they get to the party, they check in with me, I scan their QR Code and throw them into a database.
I have the core elements working where the custom QR Code with the embedded query strings for first and last names pre-populate a set of text inputs for the first and last names, you fill in some other information, click submit and BANG, you're in the database.
I would like to add some extra functionality that checks the database that someone has already checked in, to prevent party crashers.
What code would I need to write to allow, onWindowLoad, the first and last name query strings to be checked against the database to see if entries containing those already exist?
Thanks in advance
Ajax call with a select. Make it easy on yourself, use jQuery. Here are some examples:
Ajax Examples with jQuery
I built a site using Drupal 6 recently that allows for users to submit information to the site owner in three different ways. They are:
Webform A: Quick Contact - this just collects name, email, phone and a message.
Webform B: Free PDF Book by Email Webform - this collects info similar to above, and then sends the user an email with a PDF attachment which is a book written by the site owner.
Node Create: Case Evaluation - this form is a Node Creation page using the Multi-Step module, CCK and a lot of conditional fields. Anonymous users can fill out this form and the node data is emailed to the site owner based on a Rule I created.
All three of these forms work perfectly in terms of doing what they are supposed to do for the site. The webform submissions are easily accessed from the webform node by the owner, and I set up a table view to manage the node submissions.
Even though the forms are gathering slightly different data, at the end of the day, the most important data is the personal contact information (each one collects name, email and/or phone), and each form submission (from any of the forms) is considered a lead by the owner and followed up on.
I would like to centralize these various form submissions (2 webforms + 1 node) into one Content Type (leads) so they could be managed from one page, rather than three, and so the owner doesn't have to reference/compare submissions from two other forms when working with data from one to prevent double-contacting potential clients if they filled out two forms on the site.
Is there an obvious solution for this scenario that could be implemented using some combination of existing modules and Rules. Or, any solution that would at least not stray too far from good Drupal practices?
What about converting the webforms to CCK too, and using a Views Bulk Operations scenario for aggregate/sort/filter capabilities?
I'm not convinced about your desire to consolidate to one content type. You should use one content type only when the forms are similar in structure and purpose. Webform A, Webform B and Case Evaluation seem to be satisfying totally different needs. They are not good candidates for consolidation.
Another alternative is to force people to register (i.e. become logged in users) before they access any webforms and CCK forms. Using the User profile (bundled with Drupal core) module you can collect standard data when people register that you now need to collect anyway for the three forms. It will consolidate your leads data in one place. The registration procedure can be made unobtrusive and simple.
I would also recommend that you use Webforms in general. They are user friendly and are excellent for making questionnaires and contact forms. Use CCK content types for more fundamental aspects of your sites like article content types and where you need views integration.
There is a very useful module called http://drupal.org/project/inline_registration . It allows you to register just before you create a node. I would guess it doesn't work with webform (unfortunately) but please check.
Another option which I feel might might be viable would be to have user fill out 2 forms. One quick webform which captures their basic details and the other webform/node create where they get to do their specific work like request a PDF etc. This way all your lead data gets captured into one webform for which you can get excel file exports.
Before signing off -- another point occurred to me...assume you have 3 webforms (Case Evaluation is turned into a webform). You just make sure that the initial data consists of standard fields like Name, Email address etc. You will get 3 excel sheets (one from each webform). It will be very easy to take the first 3 or 4 columns that you are interested from each sheet for leads data and then combine the data together in one "leads" excel sheet. This quick and dirty method will save you a lot of effort and to my mind will be a "good enough" solution.