Skip to main content
Nintex Community Menu Bar

So you think you know form controls? Challenge #2

  • June 2, 2017
  • 10 replies
  • 20 views

Forum|alt.badge.img+17

Hopefully, you've already completed challenge #1. But if you're like most eager people, you'd probably stumbled upon this to see what was in it. Well, let's get started.

The challenge, should you accept it will be to build out two forms for two lists. The list will be identical and will contain the same fields. What we want to test is how easy is it to create a form using all the form controls available. That is all you have to do.

One thing I discovered when attempting this, was the little nuances with using certain controls and trying to make them fit in a nice way on a form. Nothing fancy, just some things that I ran into. I'm curious as to what you may encounter. Please share your thoughts or ideas below.

Cheers, a guuuuddddd luck!

Eric

10 replies

Forum|alt.badge.img+11
  • Nintex Partner
  • June 6, 2017

Hi,

here again my comments:

  • Sometimes with pixel perfect forms, it happened that, after resizing a control, its height was too small to render it correctly and it has things like scrollbar or similar, with responsive forms this is not possible so every control will have its proper height
  • Validation error messages: one great improvement will be to move each validation error next to the control, so it's easier for an user to understand which control is not valid and why
  • People control: while in designer/preview, it renders as a flattened box, while in the real form it renders correctly with the box like the other controls, is it possible to make it well-rendered also in designer/preview?

  • Managed Metadata control: as I've already written to Eric, at the moment there are no term set with terms and my user has no rights to manage the term store, so I've not tested it..just a quick note: this control isn't mentioned in the current state of the preview, nor in the available controls, nor in the coming soon ones..is it already developed (I haven't found it in the designer)?
  • Button control: it still allows for javascript but we don't have anymore the capability to write javascript or to reference an external javascript file so I think this option needs to be removed..
  • Attachment control: it doesn't have the Title property, while it would be great to give a label to that control like for the others, instead of adding a specific label for it

Giacomo


EuanGamble
Nintex Employee
Forum|alt.badge.img+13
  • Nintex Employee
  • June 7, 2017

Awesome feedback ‌. I will chat to engineering and hoping we can get another build soon.


Forum|alt.badge.img+11
  • Nintex Partner
  • June 7, 2017

Hi,

just a small addition: SQL and Web Request controls are missing, I hope they will be present in a future build happy.png


EuanGamble
Nintex Employee
Forum|alt.badge.img+13
  • Nintex Employee
  • June 7, 2017

Hi Giacomo Gelosi

The FAQ details on the front page here have all the controls we support or will support. However, I just realised I didnt include SQL and Web request for SharePoint which I will update now.

Cheers,

Euan


Forum|alt.badge.img+8

I was not clear one what this challenge intended... regarding this instruction: "build out two forms for two lists. The list will be identical and will contain the same fields", I did not understand which fields the two lists should contain.  So I created one list with no columns, and created a form with at least one of each control in a disconnected state to my form.  I made sure to test different flavors of each control type as well (Choice field  - drop down, List, checkboxes, radio option buttons, Date field with time and without time)

This test went well.  I concur generally with feedback from Giacomo Gelosi‌.  However, I was able to map a Managed Metadata control to the existing "Job Title" term set.  The control rendered properly, but since this Term Set does not have any terms and my account doesn't have permission to add any terms, I wasn't able to test it completely. 

I will also note that having support in the Managed Metadata control to add new items to a Term Set would also be a valuable feature.  But in the meantime, can you populate some of the term sets with sample data or create some new terms sets.

At one point I did encounter a "Failed to Load Viewstate" error message.  But this happened just once.


Forum|alt.badge.img+17
  • Author
  • June 21, 2017

Let me see what I can do to add some terms for this...


Forum|alt.badge.img+8

I'm curious about the plan for the Page Viewer control.  This control was not listed in the notes for Controls that are supported, will be supported or not going to be supported.  I understand its not supported now.  But will this be supported in the future?

I understand if it can't be supported since external content might break the "responsiveness" of the form.  But I do like this control for certain things.  Would be great if it can be supported in the future.


EuanGamble
Nintex Employee
Forum|alt.badge.img+13
  • Nintex Employee
  • June 22, 2017

Good suggestion on the Page Viewer control ‌. Ill look into it for you.

Cheers,

Euan


Forum|alt.badge.img+7
  • Nintex Partner
  • June 22, 2017

Responsive -

- The border control is missing, and can be nice to add some visible line breaks.

-  list look up control - could not select a site using the Browse button. It opened the selector, but when I click on my name nothing happens.

Could not copy/paste in either as I got "Loading the available lists failed. Please check the URL you have your provided is a valid URL within the current site collection"

this is nice if you have some main lists of data and that might be on a top level site.

https://nintexresponsiveforms.sharepoint.com/sites/vTE/BS

Overall everything worked pretty well and as expected. I Didn't set any rules or anything on this form I just added controls and configured them.


Forum|alt.badge.img+16

Don't know if it's just me being silly but no matter how I change the horizontal and vertical width of buttons on responsive nothing changes?

Also another weird thing.  I created two lists - one for responsive and one for pixel perfect.  I named them as such.  I had them open in two different windows.  I went to forms designer.  For responsive list I selected responsive, and for pixel perfect I selected (bet you can't guess) Pixel Perfect.  Worked on them both (same as Tom I didn't really know what I was supposed to be doing on this challenge) and published.  However, the forms switched.  Responsive form is on my pixel perfect list and vice versa.  Now, it is entirely possible after a late night in London at SharePoint Saturday that I didn't do what I have just described, but I remember checking which list I was in and I am 99% sure I chose the right one.

Now is this an issue?  Probably not.  Would I repeat?  Probably not.  But thought I would mention.