Journeys - Allow for fields to be side by side
Mike Emery
Hello Voters!
It's now possible to create tables in journeys with a range of data types and we're working to add date fields into tables now to make the list of data types even longer. But the million dollar question is whether tables remove the need for "side by side" fields or whether you need more. There's a view that single column forms are easier to use than multi-column forms but maybe that's not the problem. Is your challenge on-screen or when you export to PDF or print? Is it about the operator, customer or the environment?
We'd love to know what you think about the current tables feature and where it doesn't give you what you need.
C
Chris Jones
I've mocked something up that might work for us, of course not every user case would be the same - but this would be a good way to organise a view and maximise the real estate available, without having to scroll up and down too much or through different sections/pages. Especially keeping the relationally fields together to save scrolling. Whether the columns are 4, 5 or 6 doesn't really matter, but I think 3 or less might be too less to make use of the space.
Karen Barker
Chris Jones: Hi Chris, thanks for mocking this up. It's really useful to see exactly what you're looking for.
C
Chris Jones
Hi Guys, the new Table functionality is really good, thanks. For the most part I think this helps with the viewable elements and getting fields spread nicely across the page view.
The option in the field/"data type" for 'Text, Decimal, Integer and Currency" is great - but would it be possible to add a dropdown as a "data type" - or even possibly radio buttons, so the user can pre-select from a few choices rather than type the whole thing. I think this would produce a brilliant option for those fields that often have the same answers.
Thanks
Mike Emery
Chris Jones: Thanks. Selection/drop-down in a table is a great idea. We had it logged in our development backlog already as we thought it might be useful.
C
Chris Jones
Mike Emery: Yay! Thanks
Mike Emery
Chris Jones: Table selections/drop-downs are now available in Journeys :-) . Let us know what you think.
C
Chris Jones
For our use, up to 6 or more 'columns' in 'rows' would be ideal - we have data that is sometimes just lots of double/triple digit numbers that are then calculated later. So having lots of columns of short digit answers in a row would be perfect - although not many people would have this exact use case.
Karen Barker
Hi Jamie Hubbard thanks for this idea. How many columns idealy would you be looking for here just 2 or would it sometimes be more? Would you envisage a whole journey being multi-column or just certain sections of it?
A
Alex Cleanthi
Karen Barker: Hi,
For us only two really, although it may be useful to have the functionality to add in more.
We would vary when it is 1 or 2 columns, changing it section to section.
J
Jamie Hubbard
Karen Barker: Hi, I think it largely depends on what information is being captured. However I do agree with Alex I think two for the most part would be sufficient with the ability to add further if and when required
Karen Barker
Thanks Alex and Jamie :)
Sarah Palombo
Completely agree !