Search for officials, multi-forms or single form?

0

I'm developing an app that should be made available to employees of a particular company, so that coworkers themselves can evaluate one (two, three, etc.) work friends by answering questions (several of them, quantity configured too by the rh sector) registered by the rh sector.

I had the following question, I do everything in a single form and use javascript to go showing one question at a time, or I do several form, one for each question?

The employee should be able to partially process the process and resume where it left off.

    
asked by anonymous 11.03.2017 / 01:24

1 answer

2
  

I had the following doubt, I do everything in a single form and use   javascript to go showing one question at a time, or do several form,   one for each question?

In principle it must be very bad for usability to have multiple forms. It will be tiring (and unnecessarily useless) from the user's point of view, having to click "Submit" to each-maledeta-question. It only makes sense to separate questions on different subjects into different forms. If it's all about the same subject, use one form only. It does, however, make a little more sense to separate out different questionnaires for every other employee being evaluated.

Show one question at a time is not necessarily a problem, if you use another way to provide progress feedback . The user needs to know how many questions he has answered and how many are missing to respond. The most direct and clear way to do this is to simply put all the questions to him at once.

If the form has many questions, you can use scrollbars or paging. It does not change the fact that it will be perceived as a single form. Anyway, I mean that organization and implementation are different things.

  

The employee should be able to partially process and resume   where did you stop.

This is really important, especially if there are many questions to be answered. But that's another implementation issue. Suppose, for example, that you have a single form presented with scroll bars. Nothing prevents you from saving what has already been typed to resubmit again if the user closes and comes back later. Now, note that regardless of whether you choose to use one or more forms, the user needs feedback from what has already been filled up.

If your implementation has many questions, you should already place the questionnaire in the first unanswered question when the user logs in again; and, above all, needs to include some clear indication of where the questions are missing. You can use color, you can use a gutter (type the side mini-map that some text editors use to represent the code overview ), you may even have the option to filter only the unanswered questions. The important thing is to provide this facility to the user.

I know that these are very general tips, but that's what you can do for an equally abstract question. If you have a more concrete example, then you can do a more detailed analysis.

    
11.03.2017 / 02:57