One more problem arise after changed the type of email to "control_textbox" on the Canvas Integration

  • Profile Image
    horizoncore
    Asked on May 05, 2014 at 09:49 AM
    One more problem arise after changed the type of email to "control_textbox".

    If I keep the type of email field to control_textbox, it keeps the options of "control_textbox" in matched dropdown and if I keep the type control_email, it keeps the option of "control_email".

    I found that some ready-made templates have email field with type "control_email" and some has "control_textbox". eg.

     "16": {
                "confirmation": "No",
                "confirmationHint": "Confirm Email",
                "disallowFree": "No",
                "hint": "ex: myname@example.com",
                "labelAlign": "Auto",
                "name": "yourEmail16",
                "order": "3",
                "qid": "16",
                "readonly": "No",
                "required": "No",
                "size": "32",
                "text": "Your E-mail Address",
                "type": "control_email",
                "validation": "Email"
            }

     

     "3": {
                "hint": " ",
                "labelAlign": "Auto",
                "name": "email",
                "order": "3",
                "qid": "3",
                "readonly": "No",
                "required": "Yes",
                "size": "40",
                "text": "E-mail",
                "type": "control_textbox",
                "validation": "Email"
            },

     

    How our system could work for both type? I meant match dropdown of email field should get the list of control_textbox or control_email. Please help us!

  • Profile Image
    TitusN
    Answered on May 05, 2014 at 09:55 AM

    Hello,

    I have alerted our developers about this, and we shall update you on this thread.

    Thank you for your patience.

  • Profile Image
    cettox
    Answered on May 05, 2014 at 10:17 AM

    I think it is time we should introduce a specific keyword such as "any", to let a field to match any Jotform field. And also comma seperated lists would be helpful. What do you think?

  • Profile Image
    horizoncore
    Answered on May 05, 2014 at 10:31 AM

    Yes, both options are fine and useful.

    For some fields, it requires to match with specific type and some for any.

    Do you have plan to update the js file?

  • Profile Image
    cettox
    Answered on May 05, 2014 at 10:38 AM

    Yes, we plan to add functionality in a day or so. I'll post updates on this thread. Thank you!

  • Profile Image
    cettox
    Answered on May 06, 2014 at 04:03 AM

    Hello,

    the functionality we talked about is now implemented and working. I updated the Question Mapper documentation to reflect recent changes.

     

    Simply use "any" to let it match against all fields regardless of their type.

    Use comma seperated lists to specify which field types you want it to match:

    type : "control_textbox,control_email,control_textarea".

     

    We also added a nearly complete list of field types you can use on Question Mapper:

    http://developers.jotform.com/tools#jotformQuestionTypes

     

    Should you ever have problems on integrations, please do not hesitate to contact us again.

     

    Thanks.

  • Profile Image
    horizoncore
    Answered on May 06, 2014 at 09:39 AM

    Hi cettox,

    Thanks for quick update.

    I'm getting following error with field raw after use latest JotFormIntegrate.min.js and JotForm.min.js and type >>
    type : "control_textbox,control_email,control_textarea"

    Please add control_textbox,control_email,control_textarea type of field to your form!

    Could you please check it?

  • Profile Image
    EliezerN
    Answered on May 06, 2014 at 11:56 AM

    @horizoncore

    Our developer has received your last message. Once he will update you via this thread one he is avialble.

    Thanks

  • Profile Image
    cettox
    Answered on May 08, 2014 at 04:12 AM

    Hi horizoncore,

    Can you try again. Thanks.

  • Profile Image
    horizoncore
    Answered on May 08, 2014 at 04:59 AM

    It shows following error in error log now.

    ReferenceError: tfType is not defined

  • Profile Image
    jedcadorna
    Answered on May 08, 2014 at 06:24 AM

    @horizoncore,

    You'll be updated by our developer once he is available. Thank you for your patience.

  • Profile Image
    horizoncore
    Answered on May 09, 2014 at 04:00 AM

    Hi,

    I've solved the 2 issues of variable names in JotFormIntegrate.js file.

    They are realted to case sensative. Here are details of them.

    1) Line no: 341

        wrong syntax: var tfArray = tfType.split(',');

        correct syntax: var tfArray = tftype.split(',');

     

    2) Line no : 356

        wrong syntax: if(ffType == tftype || tfType == "any" ||Â matchedSubTypes){

        correct syntax: if(ffType == tftype || tftype == "any" || matchedSubTypes){

     

    Now, a script works without any error but all required jotform fields are not displaying in dropdowp when target field has type either "control_textbox,control_email" or "any"

     

    So I investigated more and found that value of type is wrong at 2 position.

    Line no 243 and 255 >> var qType = self.getQuestionById(dataKey).type;

    The type should be of Target record instead of Jotform record.

    Could you please look this urgently?

  • Profile Image
    jonathan
    Answered on May 09, 2014 at 08:46 AM

    @ horizoncore

    Hi,

    Thank you for the detailed information. Our support developer assigned to tis was notified also of your latest update. 

    You will be notified when they have new response here.

    Thanks.

  • Profile Image
    horizoncore
    Answered on May 14, 2014 at 01:24 AM

    Hi,

    Is there any updates in JotFormIntegrate.js file regards to field types issue?

  • Profile Image
    ashwin_d
    Answered on May 14, 2014 at 04:19 AM

    Hello horizoncore,

    Your message has reached to the developer assigned for this ticket. He will get back to you as soon as he has any update for you.

    Thank you!

  • Profile Image
    cettox
    Answered on May 15, 2014 at 08:02 PM

    Hi, the errors was fixed. Sorry for late response. Have a nice day!

  • Profile Image
    horizoncore
    Answered on May 17, 2014 at 01:58 AM

    Hi,

    Thanks for updates.

    Errors are resolved but required jotform fields are not displaying in dropdowp when target field has type either "control_textbox,control_email" or "any"

    I found that value of type is wrong at 2 position.

    Line no 243 and 255 >> var qType = self.getQuestionById(dataKey).type;

    The type should be of Target field instead of Jotform field.

    Could you please look this urgently?

     

  • Profile Image
    horizoncore
    Answered on May 20, 2014 at 01:45 AM

    Hi,

    It has been 15+ days and errors of jotform-fields in dropdown in matching area selection are not resolved yet. Could you please look this urgently?

  • Profile Image
    cettox
    Answered on May 23, 2014 at 10:47 AM

    Hi,

    For required fields problem I was unable to replicate it. What do you mean by "required"? Is it JotForm question's required property or Question Mapper's?

     

    For the other problem, you are correct. Thanks for noticing the problem and locating exact line causing it. We'll fix it in short time.

     

    Thank you!

  • Profile Image
    cettox
    Answered on May 23, 2014 at 11:00 AM

    Multi type and "any" selector bug is now fixed. Thanks again for noticing it.