This would be very helpful. We have some complex forms that for different process reason need to be printed. The print view is very different from the actual form.

is it possible to have different CSS-Classes for IsEditMode IsDisplayMode and IsNewMode?

It will help me a lot with this posibility :-)

Allowing multiple forms per list
Allowing edit either from within the form or without the form over a given list.

Different views in a form open many possibilities like having a tabbed interface within the form itself without having to resort to code. This is been one of the nicest features in InfoPath that has won the approval of my clients. Without this feature, I can't see a benefit to using a power user or end user solution that limits you to only having such capability if you know javascript.

In InfoPath I open the form in the main form view when the form is being initially created. After that, I open in a different view that asks the user what they want to do - and based on that selection they are directed to the proper view.

I do some error checking that is more than "required/not required" and use views to display an intelligent message about why they cannot submit the form without fixing the error.

Lots of reasons to maintain multiple views - it is extremely useful.

Also, this is good when the purpose the user has for the form changes from the New state to the Edit state. In the new state, maybe it is a customer submitting information and it makes more sense to have the fields in a certain order and to ask questions to get fields populated. But once the purpose who is going to fufilll the form's request gets it, a completely different structure is more efficient to actually complete the work that needs to be done. Also, they may have fields that they fill out that the customer never sees and it would be better to move those fields to the top.

Use a formatting Rule and create a formula that hides the monetary column when the Form is in Display mode. It's actually really easy. The more I use the single for for multiple New/Edit/Disp on a single form solution, the more I get where Nintex is coming from. However, I still would like the option to suppress on print for a "print" view.

I have an instance where there is a monetary column on the account that should only be visible on a new and edit form. The display form should not show the monetary amount. I couldn't figure out how to apply the "visible" setting to multiple views.

Hello that is a good idea for different layouts.
I Need that also, like, the user have no rights to add oder edit some items.
the user must see only a pice of that Information.
the user who Need to add or edit, need some for to Input. for a workflow, or on my Situation for a Intranet-Shop item.

A couple of more days into Nintex forms now. I figured out how to suppress controls when the form is in different modes. This get's me part of the way there. However, there are some things I haven't been able to figure out like how to "collapse" the form height and visible controls when the hidden ones are suppressed. With separate New/Edit/Disp forms, I would have that control. Maybe there's a way to accomplish this using the single form?

I agree having the ability to create different views would be helpful. This goes with both the New/Edit/View but also having the ability to create different pages instead of just panels. A thought on that would be having a print view option to customize as most forms if pretty enough may be printed also.

Brand new to Nintex - less than a day under my belt. But this enhancement request caught my attention because it mentioned a print optimized view. That's something we'd be very interested in if it's not possible currently.

Also, customer that are "converting" from InfoPath are simply used to this functionality and missing it... ;-)

Hello Daniel.

Some examples: The "New" and "Edit" forms sometimes differ when our customers want to enable fast and simple input in a first step and more information in a second editing step.

While we can use rules and JavaScript to enable such behaviour, it makes using the form editor difficult and the form gets harder to overlook / understand. In the "View" mode, we often want to enable a more compact view, which results in the same problems.

I think it is only very little additional work and that it is worth it, because you would get a better maintainability of the form.