When dealing with a complex form, rules take a considerable amount of time to run and complete. Then when a form gets opened, an action is made and a form is saved/submitted again and all of that is done in a short time - rules will not finish, resulting in a broken form (e.g. fields not set correctly etc.) See two examples below that are a cause of a submit/save button not being disabled when the form is processing data.

1. With a new List item being created, if the OK button is clicked more than once then it will result in a duplication or triplication of the new item. Each of the duplicates / triplicates will have the same date and time created.
2. When an existing List item is modified and the OK button is click to save when the Rules are still running, the rules will not complete. Only the modification made by the user will be saved, not including any changes that should be made by running Rules.

In InfoPath I have used multiple views of a form in combination with Form Load Rules to present a separate form for users on the same list depending on a rule. One example was a separate form for the initial add item and then another view when editing. The rule would just look at a required field and see if it is empty. Another example one form was used when adding and editing the initial record. The form had a field for adding additional lines and I used Nintex workflow to add these with a different value in one field than that first record. Then when you edited any of those rows you got a different form.
I'm just wondering if this can be done in Nintex Forms for SharePoint on-prem.

Thanks - Rick

Hi,

The biggest problem with radio buttons/choice controls on Nintex Mobile is that it defaults to the native behaviour of displaying all values in a list, such that selecting the control it "pushes" the list to a new window on the stack and the only screen you see IS the list. Users then select a value(s) and the user then "pops" the window off the stack returning the user to the page with the option choices value(s) shown.

There is an alternative behaviour that can be implemented, and I have done this as an iOS developer, and the behaviour I speak of is displaying the options as a pop up rather than a stack.

The benefits are that the underlying page is still visible, and the list displayed can be minimized to the list content. This would work on both iPads AND mobiles. It's a lot more user friendly, especially when you have many choice questions, as users aren't constantly switching screens.

Could I request this change?

Regards

Chad

It would be great to give the Nintex form the ability to auto-save when the end -users are filling in their forms. Currently we have the "Save and continue" option as well as the ability to do some Javascript that can save but those approaches still do a server call; which refreshes the page, slows down the data entry, can go out of focus and gives a very unfriendly user experience. We would like to give the user the same experience when working on MS Office 365 where their entries are auto-saved every X-Minutes/seconds and add a line on top to say that your entries has been auto-saved, without doing a server call or refreshing the page.. Pretty please...

The reason also why this is so important is because some forms can be so long to fill in, developers can handle saving so often.. but the end-users won't tolerate loss of data with forms that are long or require quiet a bit of information/long text typing.

Please and Thank you! :)

We need to get details from external Oracle database using BCS connection and show them on Nintex form.
We have created external content type which has one primary column and 4 secondary columns.
And created SharePoint column using that external content type.
On Nintex, we are able to add newly created SharePoint column but with primary column only.
How can we add other 4 secondary columns on Nintex form?
Because we can’t see other 4 columns on available SharePoint columns window in Nintex Forms.

Note : BCS connection working fine because when we save Nintex form with external SharePoint column data, we can see other 4 secondary columns data in SharePoint list view.