I already understand that the best practice is to use one field per line, unless it has a direct relation, for example: Address and phone number. Reference.
But I work on a system that in many fields, whether they are mandatory or not depending on the company that uses it, this will be customizable.
An internal resistance is usually to complain about using this model, the form is too long, needing to scroll, and putting several fields side by side, impairs the reading and faces the old delphi system, and applications that use here internally has that face, ie for the company are examples of good interfaces, which I do not agree.
In a query screen, this would also be bad, since the query screen is usually the same sign-up screen, with the input filled, so that the user can edit information (in this case I'm thinking of changing the appearance of the screen query for something less expensive form.
I'm searching on but have not found anything. Does anyone have system references that use many fields, but can I use these good practices?
PS: I've also thought about step-to-step screens, but there's also this resistance.