Configurable List Widget: The option to make it dynamic so conditional logic is possible for input types

  • Profile Image
    GXH
    Asked on September 13, 2019 at 04:54 PM

    I'm not very experienced with coding yet... does anything dynamic have to be in a widget? Would it be possible to make "duplicate section" a standard form element instead? 

    I even thought of creating 10 or so copies of the section I want repeated, and using conditional logic to show each one as required. But that can only be done with a Yes/No radio button, which is just a bit inelegant for my liking (a clickable "add" button makes more sense, but I can't see any configurable buttons in the menu).

    Not to mention that method would take lot of work - I have other sections that would require the same treatment, so in the end I'd have to set up several dozen conditions.

    Is there a feature requests page I should move this to?

  • Profile Image
    Welvin
    Answered on September 13, 2019 at 05:38 PM

    I understand your concern about the dynamic contents. I have seen features like this around the web, so it is likely possible with Jotform in the future.

    Yes, adding multiple configurable list widget and conditionally show each by a radio button selection is a bit tedious process. It also defeats the purpose of the widget to add rows dynamically. 

    I have now gone ahead and submitted this thread to our backend team as a feature request - to allow conditions in the widget. Unfortunately, we cannot provide you an ETA for the ticket,  but as soon as we have an update, you will be notified in this thread.

  • Profile Image
    GXH
    Answered on September 14, 2019 at 04:00 PM

    Thanks Welvin. Just a few more comments based on my recent experience struggling with the widget...

    Along with conditional logic not being supported, other limitations of the current widget include:

    - the labels don't inherit the styling you've applied to the rest of the form (not major but a nuisance)

    - the widget is (for some reason) designed to run horizontally across the page. This is massively inconvenient when your layout calls for vertical flow instead. I would highly recommend adding an option to toggle the orientation (I have seen others online with the same problem, and the workarounds are painful). 

    All of the above issues would be solved by a different approach, as mentioned in this comment from my previous thread:

    "If [conditional logic] is beyond the widget's scope, I'd really recommend creating a new widget [or form element] that allows you to bundle any combination of normal fields together in a wrapper and then dynamically copy them as many times as the user needed. This would also aid consistency throughout the form, and remove some of the limitations of the current widget."

    I'm not experienced with coding so I don't know if I'm suggesting something impossible, but my idea is something like the section collapse element that bookends a collection of fields, but instead of collapsing the section there would be a button that would duplicate that section. 

    If that's a ridiculous idea that can't work in the real world, then at least updating the current widget to support both vertical stacking and conditional logic would be amazing.

  • Profile Image
    Welvin
    Answered on September 14, 2019 at 05:15 PM

    You're welcome.

    To answer your comments:

    For the labels: What styling do you mean here? The Custom CSS codes of the form itself and the separate custom CSS codes for the widget? We have a custom CSS codes for each widget since most of them are placed in an iframe that the form's custom CSS block can't change. 

    For the widget positioning: I understand this. So, instead of the custom CSS, this part should be an option so tiny forms with a long list of items in the configurable list widget will automatically wrap up when toggled. I will create a new ticket for this in the following thread: https://www.jotform.com/answers/1964380


    I can't tell either, but with available resources online, I believe it is possible to do the widget as a regular field. It is just the time and maybe a few more things to consider such as how the backend would dynamically apply conditions when it is already available. I'm really sorry, but that is the only thing we can offer right now :) 

  • Profile Image
    Gyanwati
    Answered on September 14, 2019 at 05:33 PM

    मैं पैसा और नाम कामना चहाती हु मेरे साथ देने 

    वाला कोई नहीं है मे कुछ हाशिल करना चाहती हु sorry  में आप के Question ka Ans. Nhi de pai

  • Profile Image
    John
    Answered on September 14, 2019 at 06:01 PM

    Hi @Gyanwati,

    I have moved your concern to a separate thread so we could assist you better on that topic.

    I will be posting my response shortly on this thread below:

    https://www.jotform.com/answers/1964413



  • Profile Image
    GXH
    Answered on September 14, 2019 at 07:30 PM

    Hi Welvin, 

    Yes, since the widget sits inside an iframe it doesn't inherit styling from the Form Designer (which in my case I've done without having to use CSS). It's not a huge issue, just a nuisance since you end up having to apply CSS after all just to match what you did without CSS. It probably can't be changed so long as this remains a widget, but my "duplicate section" wrapper idea wouldn't have this problem since the fields inside would be standard ones and would inherit the form's styling and retain all the same functionality as usual. 

    Thanks for creating a ticket for the vertical version of the ticket - yes that is the issue I'm having. Incidentally I don't think my form is that tiny, it's based on the default theme. Particularly if you have text area fields, allowing them to be wider would be helpful rather than cramming them all side by side. In my case I have multiple text areas and vertical stacking is much more user friendly. I'm actually surprised this isn't the default to be honest but I guess every use case is different.

    No worries about the timeline, as long as a ticket is open I'm happy. I can use workarounds for my form but this way at least the next person will benefit. :)