Post

27 followers Follow
15
Avatar

Dividers or Grouping needed in App item screens

Some of our app items are 2 or more screens long. That's a lot of fields and I personally find this makes the forms more confusing than they need to be. I'm sure I'm not the only one.

Usually there are some logical groupings that would help break up the page... but I can't see any practical way to do this.

Could you please make some basic elements available to us to divide the forms up a little?

At the simplest level this could be resolved with simple "Horizontal Rules" ie HR tags... And maybe a "Heading" element... each of which are standard html elements and should be pretty simple to add in a new field group.

<HR>

Perhaps in a later release, you could look at a more advanced solution of "Groups" which could be added to the page (html DIVs) that have a heading and perhaps user selectable colours...

Glenn Huther

Please sign in to leave a comment.

33 comments

-3
Avatar

Hi Glenn,

Thank you for sharing this feedback.

As you know app templates are open to be modified as you please, and you could for example make a general rule for a max number of fields to be added to an app. Maybe it will be more relevant to have several apps with relationship fields to link to each other instead of few apps with a large number of fields?

We will monitor this thread for more feedback.

/Mette
-Podio

Mette Frøkjær Hansen -3 votes
2
Avatar

I agree with Glenn. Some basic headers would go a long way in organizing an app template. For example:

We have a work request app that has fields that need to be filled out at the beginning and end of the process. Being able to separate these by a header would make it more clear to our users which fields need to be filled out at each point. Ideally, we would like to group these fields together and make them collapsible.

I agree some of these issues can be solved by splitting up a large app but there are definitely cases out there where having everything in one app makes the most sense.

Christopher Abalos 2 votes
0
Avatar

Hi Mette

What we have is a booking enquiry form that contains 20+ fields. They are all necessary and splitting them out into multiple apps would create unnecessary complication for the users.

I think adding some simple horizontal lines (and headings ideally) would be a very simple request to accommodate and would make a great deal of difference to usability on a daily basis.

Thanks for your ongoing consideration.

Glenn Huther 0 votes
0
Avatar

Hi Glenn,

Thank you for clarifying this.

Changing the UI is a larger project that affect overall layout, so we will need careful consideration when going into a project like you're describing.

We will keep monitoring the space here to get a feeling of the demands out there.

/Mette
- Podio

Mette Frøkjær Hansen 0 votes
0
Avatar

Dittto Ditto ... so many many companies are focussing on making information simpler .. we need to be able to split up an item view into 'bitesize' bits of information .. all too often another field is added to an app and no one seems to think about how much scrolling up and down needs to be done, the suggestion to make more apps just does not work always.

Saracens BOT 0 votes
3
Avatar

Glenn,

I'm not sure if this will help you or not but I figured out that you can insert headers and line breaks by using a calculation field and markdown. A calculation field has to reference another field but you can just stick it in a variable and output markdown text. Here's some examples:

Header Text Example

var blank = @Name Of A Random Field
'Header Text === \n'

Line Break Example

var blank = @Name Of A Random Field
'---\n'

Christopher Abalos 3 votes
3
Avatar

Just realized my header text example was wrong.

Header Text Example
var blank = @Name Of A Random Field
'Header Text\n=== \n'

Christopher Abalos 3 votes
3
Avatar

Christopher, Thank you!

I ended up merging your suggestions as follows:

var blank = @somevariable
'Booking Details\n===\n---\n'

So I ended up with a heading AND a horizontal rule.

You are a legend.

(Podio, this will do as a workaround... but my request stands. I don't think we should have to work around this.)

Glenn Huther 3 votes
0
Avatar

Very cool that you were able to do this Christopher, and thanks for sharing the insight Glenn.

It is noted that this is still a feature request:-)

/Mette
- Podio

Mette Frøkjær Hansen 0 votes
0
Avatar

Glenn,

You're welcome! I agree this is good workaround but something that should be native to Podio. There just needs to be two more "field types" that you can drag over, one for HR and one for headers. This wouldn't require any change in the Podio UI and would be extremely easy to implement. They could even just be a wrapper for a calculation field that adds the markdown for you.

Christopher Abalos 0 votes
0
Avatar

True... although I think it'd be best not to use the calculation field as (at least for me) the header and horizontal rule aren't visible when adding a new entry, not until it's saved.

Fortunately given that the devs can add dragable form elements that have to be updated, verified, linked to other fields (for calculations) and stored in databases... then a header and horizontal rule should be pretty simple for them :)

Glenn Huther 0 votes
0
Avatar

Hi Glenn and Christopher,

Many thanks for working out the calculation bit and your right would be so easy for Podio to add this,

Can you tell me why the divider only shows up once you save it ?

Justin Dean 0 votes
0
Avatar

The desperation for this grows as my forms start to grow longer ... I appreciate its not a simple fix and Podio team needs to think this over ... Trust me it will be met with great applause.

Monir Mohammed 0 votes
1
Avatar

I concur, Podio is powerful but the interface is awkward. Groupings, HR's, headings, colors, all urgently needed. I would also suggest being able to put more than one field on a line, and control over the amount of vertical space between lines. Currently I would say there should be about double the number of fields vertically per page to avoid so much scrolling.

Gary & Lilla 1 vote
0
Avatar

Hi @Gary,

Thank you for your input and vote on these tweaks! Please keep your feedback coming, we love it!

/Charlie - Podio

Charlie Lindstrom 0 votes
0
Avatar

@Charlie thanks for acknowledging this post. My question for you is given this request was posted 11 months ago, why haven't we seen even a simple solution?

Although I don't know the Podio code specifically, as an ex web developer with 15 years experience it seems to me that adding a Horizontal Rule or Basic Heading option to the list of selectable "Fields" would be EXTREMELY simple for your brilliant developers. A heading might be the best option, as it could be filled with characters to appear as a divider eg "--------HEADING---------"

Could this request PLEASE be considered as a two part request?
1) ASAP Implement simple Horizontal Rule or Heading as a divider to the "Fields" lists
2) Implement something more advanced as per the other suggestions within this thread.

Thanks, Glenn

Glenn Huther 0 votes
0
Avatar

This is not a huge development this is without a doubt someone's dislike for headers and page breaks because I am mind blown this doesn't exist. Don't expect this feature any time soon I came from zoho crm 3 years ago and this was the first feature I noticed was absent. Great system thanks for everything but this genuinely could not be a more basic request

CJ 0 votes
0
Avatar

I'd like to add my vote! 

In my case I have 6 or 7 sets of three inputs. A simple horizontal rule would group them intuitively and unobtrusively.

<hr> - thanks!

Steve Weeks 0 votes
0
Avatar

Yes, I need this.  I would like the employees to see "Sections" of an App.  Everything runs together and some apps are long and detailed.  Page breaks, sections or "Headings" would be huge!

 

Please do this.

Dennis Scovazzo 0 votes
0
Avatar

+1 for me too, so simple to implement, surprising the functionality isn't there yet

Tyler Thompson 0 votes
0
Avatar

Note: it's easy to insert a divider by making a calculation field that generates a literal value of a straight line. The name of the field can be capitalised to increase the effect of a "header", while labelling the section. The only advantage of a "Horizontal Rule" feature would be to save you copying and pasting the JavaScript, and possibly a more compact layout.
Search this forum,.. It's in here!

Steve Weeks 0 votes
3
Avatar

@Steve Yes that's the workaround I use also... but there's a significant weakness with that method - those calculation fields are not visible when creating a NEW entry.

Anyway, in case it helps @Tyler though, this is the header code I've been using.

   var blank = @select_a_field_from_your_form
   'Booking Details\n===\n---\n'

In that example, the words "Booking Details" shows as a nice bold heading.

The field names for my separator calculations are simply (1), (2), (3) etc going down the page so they are distinct but not too visually distracting - see below.

Glenn Huther 3 votes
0
Avatar

Hi Fady,

This is still something we are considering, but as we looked into it, it is (surprise!) more complicated to build than it initially seems. If there are any updates we will be sure to let everyone know here.

/Jacquelyn - Podio

Jacquelyn May 0 votes
0
Avatar

I'd like to echo the hundreds of other people I've seen request this feature on this and other threads, sites, blogs etc.  Such a simple thing that would make such a difference.

My use case for this is that I want to be able to create a call script app for my team to work from when handling customers.  I could break the script into sections and also leave instructions at various points for people to follow.  Obviously the instructions would need to be pre-populated on any new items created which is why the current workarounds don't work.

You're actually already 90% of the way to delivering this.  Have a look at the image below, which shows an excerpt from my call script app with a made-up example:

The "Script Guidelines" section is just a multi-line text field, something that anyone can add to an existing app item and style however they want.

In other words, pretty much all you need to do is make it possible to pre-populate text fields in the app template.  Add a "pre-populate" option to your text field type and allow people to enter whatever value they want on the app template so it appears on every new item.  This would solve my use case and every other mentioned in this thread as far as I can see.

Adam Williams 0 votes
0
Avatar

Thanks to @Glenn for the graphic inspiration here - nice. We extended with jump-to links at the page top to make the form easier to navigate:

a) Insert a calculation field at the top of your form, for navigation (eg 'Jump To')
b) Use this calculation formula (note the links must be lower case for some reason, even if the destinations are title or upper case  - took us a while to figure that out):

waste=@Name;
"[1 Contract](#contract) | [2 Needs](#needs) | [3 Solution](#solution) | [4 Finances](#finances) | [5 Schedule](#schedule)";

c) Then add the matching anchor / title fields

1)
waste=@Name;
"# Contract\n---\n";

2)
waste=@Name;
'# Needs\n---\n';

3)
waste=@Name;
"# Solution\n---\n";

4)
waste=@Name;
"# Finances\n---\n";

5)
waste=@Name;
"# Schedule\n---\n";

We still have an unresolved problem - how to add a 'return to top' option - when we added these into the calculation fields, it broke the link for some reason.

Tim Cumming 0 votes
1
Avatar

3 Years on this thread and 4 years on another thread and still doing work-arounds instead of having this functionality built in? Obviously the product manager just doesn't want to do this. Which is always a great way to prioritize your features! If you're using a Kano model to evaluate your features, this would probably be in your Basic Features group. Wufoo can do it. As a person who does UX, this is pretty important for good UX. 

I'm about to create form with about 100 fields or so. They are all grouped up into sections (20) right now on a spreadsheet. I'm going to need to implement that with a work around that is then going to pollute our API requests with data that won't need to be there.

Also, ideally on an API call, the values would be contained within a section attribute as well but I'll settle for just the improvements to the forms and UI! 

 

It's not like we are asking for branch logic! 

 

Aaron Shapiro 1 vote