Node Attributes for Portal

(1) Value _hAlign_, for example, has the effect that the fields of this node in the form are not shown one below the other, but side by side. For a complete list see section Values for Attribute 'Portal control'.

(2) If a different label is to be used in the form instead of the name of the node, a key name for the label must be entered here (freely assignable, here Head). The same applies to fields. The key is then used to assign the localised name. For details see section Localisation.

(3) For each source structure node, you can specify a profile that dynamically fills the fields of this node. See section Dynamically Filling Form Fields.

Field Attributes for Portal

(1) If set to Yes, this field will be shown in lists of the Portal form. This setting has no influence on how the field itself is displayed. Use value _hidden_ in (3) for that.

(2) If multiple values, separated by semicolons, are specified, a selection list will automatically be created in the form. Insert values A;B;C. Those values can also be localised. See section Localisation. You can also use a regular expression with prefix regex: to specify/check allowed values (this will not create a selection list though).

(3) For a complete list see section Values for Attribute 'Portal control'.

(4) If there can be several instances of the node of this field (node attribute Maximum > 1), a list will be created in the form. This list will not be created for Maximum = 1. Attribute Minimum has no effect. See list field Text and input field Text in the portal view.

Note: If you want to evaluate which records (rows) in a list have been created, changed or deleted, you can create an additional field named row_change_kind with value _hidden_ for the field attribute Portal control. This field then automatically receives one of the values created, updated or deleted in the profile. Important note: If you use multiple row_change_kind fields, they get a field name suffix in Lobster_data (e.g. row_change_kind-1), because field names must be unique. In this case, please use a match code with condition Equals and the value row_change_kind on all these fields.

Note: If the type Blob is used for a profile field, the input field in the form is a multi-line text field (see field Free_text).

Note: For numeric types, a template without a thousand separator must be specified. A decimal separator (.) may be used if necessary. The browser will output the appropriate decimal separator depending on the language setting, so a comma (,) for German and a dot (.) for English. So if one of the types BigDecimal, Float or Double is used, you could use the template ####0.00 or if the types Integer or BigInteger are used, you could use template ####0 instead.

Note: A form field can be made mandatory by setting the source structure field attribute Minimum in the main profile to 1. The form field is then displayed with a red asterisk. The attribute Maximum has no effect.

Note: For this example, you can simply create the destination structure with the button 1:1. In this example, we will not use the destination structure and the Response Routes of the Portal main profile.