How do I edit submissions on a form with pages which conditionally skip?

  • Profile Image
    SVLL
    Asked on January 16, 2012 at 03:01 AM

    We built a form and broke it down into several pages.  We have one of the pages only visible if the form URL contains a querystring with a special code.  The way we accomplished this was to follow the examples in this forum which utilize a text field, then using CSS injection we "hide" that field from the form, but it is populated by using the aforementioned querystring.  

    When we are in the JotForm "Edit submission" UI, there isnt a way to get to that hidden page, since we could not edit the form using a querystring.

     

    Is it possible to edit a submission and pass that value in?  Any other means by which we can get to those pages?  As the admin, I expect that we could see every page irrespective of the state just like when we are in "form edit" mode.  

     

    Eagerly hoping there is a solution here.

     

    Thanks!

    /Ty

  • Profile Image
    fxr
    Answered on January 16, 2012 at 09:44 AM

    Hello Ty,

    I can see what your trying to do here, unfortunately, because your 'admin' field is empty when it is being submitted by non-admin users, then when you go to the edit link, this is its' value, even adding &admin=passcode to the end of the edit URL will mean its repopulated by the 'old' i.e empty value.

    I have thought about potential workarounds and I just cant come up with anything that will mimic exactly how you have described you want the form to work.

    You need to have that 'admin' field on the form, so that admins can type in their passcode and access the 'hidden' section of the form. 

    The best I can come up with is to use some CSS and try and hide that field as much as possible, so that only people who know where it is will be able to find it:

    For example, have a look at this clone of your form:

    http://form.jotform.com/form/20154050128

    I made the size of the field smaller and added the following CSS:

    #label_71 {display:none;}

    #input_71 {background-color:snow !important; border: 1px dashed snow !important;}

     

     

    I know, this isnt quite what you are looking for but its the best I can come up with the tools that are currently available to us. 

  • Profile Image
    SVLL
    Answered on January 17, 2012 at 07:28 PM

    Thanks for looking into this.  Your workaround should do for this season. 

    Some general feedback from a 1-month customer (on a 1-year subscription)..

    It may be good to consider adding additional capabilites around the dynamic nature of forms and how data-driven fields can impact them.  I think there are a number of administrative scenarios necessary for supporting form submissions.  The workarounds we applied using style sheets, conditional page skips, and now this semi-hidden field are all attempts to address a more fundamental issue - When forms are "live", the data on Jotform is authoritative; the administrative actions cannot happen downstream of the form otherwise the data integrity is suspect.  I think Jotform is on to a potentially large market by attracting a user base with little technical experience who wish to acquire inputs in a simple, safe, and managable way. 

    It is possible that I could setup a data feed downstream; build a primary key by concatenating the IPaddress and timestamp of an entry; and then manipulate offline.  If I was to do that, then my team would naturally ask the question "why not build the enture form in-house and be done with it?"  At some point, Jotform customers will cross a tipping point of complexity which meets or exceeds the technical bar for a Web-Developer-1.  Your business model must be based on satisfying the scenario needs of the customer while staying as far away from that bar as possible. 

    Thanks again; I will transfer this modifications to our form so that we are unblocked.