Show last authors
1 {{content/}}
2
3 {{figure image="designer_properties_base_en.png" clear="h1"}}
4 User interface for changing basic properties of a form field, such as its name or its width.
5 {{/figure}}
6
7 {{figure image="designer_properties_base_repeatable_elements_en.png" clear="h1"}}
8 Elements can be repeated. In this example, the user can enter one or more email addresses.
9 {{/figure}}
10
11 {{figure image="designer_properties_base_repeat_trigger_en.png" clear="h1"}}
12 The number of repetitions can also be set automatically, depending on the value of another element. In this example the fieldset with the data of a single child is repeated. There are always as many fieldsets as the number of children the user selected.
13 {{/figure}}
14
15 The base properties //name//, //width// and //hidden// can be set for each form field.
16
17 == Base properties ==
18
19 {{table dataTypeAlpha="0" fullwidth="false" colWidth="-500"}}
20 |=Name|=Description
21 |element|{{version major="6" minor="3" /}}Element type of the form field. The element type can be changed by selecting another element type in the dropdown menu. The element types an element can be transformed into depend on the original type. [[Containers>>doc:Formcycle.FormDesigner.FormElements.Container]] and [[fieldsets>>doc:Formcycle.FormDesigner.FormElements.Fieldset]] can only be transformed into the respective other element type. All other element types can be transformed into any other type, except for containers and fieldsets.
22 |name|Name of the form field. Only letters and numbers may be used.
23 |alias|An alternative name for the form element, which may contain any characters. See below.
24 |width|Width of the form, relative to the width of other form fields on the same row. For example, when placing two form fields next to each, giving both a width of 2 means that both will take 50% of the available width. Setting the width of the first form field to 1, and the width of the second one to 3 results in the first one taking 25% of the available width, and the second one taking 75%.
25 |hidden|When checked, the form field will be hidden initially. To show it again, the option [[visible if>>doc:Constraints]] can be used, or a Javascript function such as {{jsdoc name="visible" page="jquery"/}}.
26 |disabled|When checked, the content of the form field cannot be edited.
27 |Repeat{{id name="repeat"/}}|When this option is activated, the user can freely create any number of copies (repetitions) of this form element. For example, this can be used to let the user enter one or multiple email addresses. Please note that you cannot nest repeated elements: if a container is marked as repeated, none of its containing elements can be repeated.
28 |Min. repeat|Minimum number of allowed repetitions. When this limit is reached, the user cannot delete any more repeated elements. This is also the inital number of repetitions when the form is opened.
29 |Max. repeat|Maximum number of allowed repetitions. When this limit is reached, the user cannot add any more repeated elements.
30 |Repeat trigger|When an element is selected here: The number of repeated elements is automatically set to the value of the selected element. For example: Assume there is a [[select element>>doc:Formcycle.FormDesigner.FormElements.Selection]] or [[input element>>doc:Formcycle.FormDesigner.FormElements.Input]] that lets the user enter number of children in their household. Also assume there is a [[fieldset>>doc:Formcycle.FormDesigner.FormElements.Fieldset]] for entering some data of these children. The fieldset is marked as repeated, and the select or input element is set as the repetition trigger. Now when the user enters how many children they have got, fieldsets are removed or created automatically so that there is always one fieldset for each child.
31 |Hide buttons|{{version major="6" minor="2" /}} Available only when an element was selected for //Repeat trigger//. Enable this option to hide the plus and minus buttons for adding and removing repeated elements. Use this option when the number of repeated elements should be controlled only by trigger.
32 {{/table}}
33
34 == Alias ==
35
36 When a form is submitted, key-value pairs are sent with the name of the form being the key and the entered text being the value. Within workflow actions or templates, you can access the values of submitted form elements with [[variables>>doc:Formcycle.UserInterface.Variables]]. The name of a form element cannot contain special characters such as accented characters (é or ô). When sending data to web services or when integrating third party systems, it may become neccessary to make use of special characters. In this case, you can set an alias for a form element. This alias does not have any restrictions on which characters you can use.
Copyright 2000-2024