Nested form
Let's take another look at our first form.
A form input field named "field", in which several values could be entered (list below), was created from our source structure field "field".
What we did not mention before is that this was due to the source structure node attribute "Maximum" of the node named "node" that had the value "99999". So a value > 1 creates a data list. The effect of the "Minimum" attribute is described in section Defining selection values, mandatory fields and default values .
Nested form
We now want to make our form a little bit more complex. We would like a form, in which you can enter exactly one order number and any number of item numbers.
Therefore we create the following source structure.
The value for attribute "Maximum" of node "order" is "1" here and the one of node "items" is "99999".
The form page
Our new profile generates the following form.
As you can see, the input field "order_number" no longer has a data list.
Entering data into the form
Let's enter some simple data again. As you can see, you can enter exactly one order number in the input field " order_number" .
Note: Accordingly, the data will be nested in the JSON input file of the profile job. You already know how to get there .
Example profile
To save you the work and for verification, here is the described profile to import. After importing the profile, do not forget to set it active. Also, you need to create your own Web Monitor user, if you haven't already, and select it (or the role it has) in phase 1.