Tabs for form navigation?
My crews are finding navigating between forms and subforms is cumbersome. They have made the suggestion that having tabs at the top where you can pop back to the parent page or other page would be useful. They would like to be able to have more than one subform open at the same time so they can navigate back and forth between the two. I am not sure if this would be useful for other people but for us it would improve the usability significantly. We are collecting data from humans who do not always give us the information we need in the order in which we need it at a high pace.
-
Hi Lea, we have tackled similar challenges in the past by building custom interfaces on top of the core platform to cater to a certain style of collection.
We have found that trying to tackle this in a universal fashion usually gets close but never quite achieves the desired workflow. If you would like to explore in more detail please drop us an email and we can help take a closer look with you.
-
Hello, can I suggest collapsible frames within the form. This would allow multiple pseudo 'subforms' to be held within the same form. It would result in a form that presents multiple sub headings that when clicked would expand to expose the required data fields. At present this could be done without the 'collapsible frames' but leads to a long form that becomes difficult to navigate. It does result in a flatter record ( and longer record ) too but if the work flow justifies it and it supports a logical data structure then I could see it being of great benefit. We too get feedback about the time it takes to navigate in and out of subforms to collect hierarchical asset information and it would help us be more efficient during the data collection process.
I would see it as being a new Widget ( Collapsible Container ) that gets dragged onto the form. Then entry widgets could be placed within this container as per usual, the only difference being that when rendered in the application the user only sees the heading of the Container and has to tap the heading to expand the contents. I don't think it would change much in the way iForms works with it's current data structures, rather a small change in the the logical design of how iforms presents the widgets.
Anyway , that's my two cents, be interested in your thoughts.
Please sign in to leave a comment.
Comments
3 comments