_editOnly_

Input fields displayed: Yes.

Input of new list data possible: No.

Data profile can load list data: Yes.

The list data loaded by the data profile can be modified: Yes.

_exclude_

[ Setting is not relevant for forms. Applies only to web services .]

_exportable_

The data list generated by the node in the form can be exported as CSV file.

_hAlign_

The fields of this node are displayed side by side in the form instead of one below the other.

_noDelete_

Suppresses the option "Delete entry" in forms.

_readOnly_

Input fields displayed: No. Note: The only difference to " _viewOnly_".

Input of new list data possible: No.

Data profile can load list data: Yes.

The list data loaded by the data profile can be modified: No.

_subNodesAsTab_

Subnodes of this node are displayed as tabs.

_viewOnly_

Input fields displayed: Yes. Note: The only difference to "_readOnly_" in nodes .

Input of new list data possible: No.

Data profile can load list data: Yes.

The list data loaded by the data profile can be modified: No.

_align:left_

Field contents are displayed left-aligned in a data list.

_align:center_

Field contents are displayed centered in a data list.

_align:right_

Field contents are displayed right-aligned in a data list.

_exclude_

[ Setting is not relevant for forms. Applies only to web services .]

_fileUpload_

Allows you to upload a file into a form field. The field content uploaded to the form profile is " <File name>:<File content BASE64-encoded>" . For example, if you have uploaded a file " test.txt" with content " 777" , this would be " test.txt:Nzc3" . You can restore the original file content in the form profile by first removing the prefix " test.tst:" with the function substring-after() , for example, and then by applying the function decode Base64() to the Base64 string " Nzc3" .

To avoid an OutOfMemoryException with very large files, you can configure a lazy upload. For this purpose, the following must be entered in the configuration file ./etc/startup.xml for the WebMonitor.

<!-- lazy upload handling; define a local directory and a path for external access -->
<Call name="setLazyUploadDir">
<Arg>./tmp/LazyUpload</Arg>
<Arg>/home/develop/IS/tmp/LazyUpload</Arg>
</Call>

Example output of a lazy upload: "statistics.json:/home/develop/IS/tmp/LazyUpload/lazyUpload_909422245663980803.dat@localhost"

In a mapping the file can be fetched with function copy file() or copy file by sftp().

Note: See section Blacklist and whitelists for file extensions.

_hidden_

The field is not displayed as input field on the form page and also not in the data list (even if "Show in list" is set), but it is sent to the form profile and data profiles .

_htmlContent_

If this value is set, HTML code can be entered in the field (but only in the profile), which is then displayed formatted in the form. No entry can be made in the form field. Note: If you want to allow entry in the field, you have to set the system property "-Dhub.datawizard.htmlInputAllowed" to "true" (Default: "false"). However, the HTML code may be cleaned up before output to prevent cross-site scripting. If the system property "-Dhub.datawizard.htmlOutputAllowed" is also set to "true" (Default: "false"), this cleanup is not performed.

_keepInSession_

The input field is transferred to a called data profile and can be used there no matter where it is located in the form profile. See section Dynamic form for an example.

_readOnly_

Input fields displayed: Yes.

Input of new list data possible: No.

Data profile can load list data: Yes.

The list data loaded by the data profile can be modified: No.

_submitButton_

Starts the assigned data profile , see section Dynamic Form.

_width:<number>px_

This allows you to specify the width of the field. For example, " _width:100px_" would define a width of 100 pixels. Note: This specifies the minimum width for fields in lists. If there is more space in the list, the field is also assigned a greater width.

_height:<number>px_

This allows you to specify the height of the field. For example, "_height:100px_" would define a height of 100 pixels . Note: Only has an effect if the data type " Blob" is used for the profile field.