{{item.Title}} ( Token: {{item.BoundName}}, FieldType: {{fieldDefs[item.InputTypeStr].Title}} ) {{item.BoundName}} ({{fieldDefs[item.InputTypeStr].Title}}) This field is configured through Plant an App. Obsolete Duplicate ID ID field must not be empty ID field must only contain latin characters and numbers ID field must start with a latin character Conditions Bindings OnChange/OnClick Custom CSS Validators
Copied FileId to clipboard

This field is controlled by Plant an App.

Displayed on front-end, if you use tokens the ID must be set manually.

ID field cannot be empty

ID field must only contain latin characters and numbers

ID field must start with a latin character

Used to reference fields using [ID] syntax. This field supports Tokens.

This boolean expression is used to determine if this field will be used in the form. Note that this is not the same as hiding it visually. This is evaluated both initially and after submit. It supports C# syntax. A common example is [SomeField] == "Some Value" or [SomeField].IndexOf("something") == 0. This field supports Tokens.

This boolean expression is used to determine if this field will be enabled (accepting input) in the form. If specified, this field overrides the Enabled flag below. It supports C# syntax. A common example [SomeField] == "Some Value" or [SomeField].IndexOf("something") == 0.. This field supports Tokens.

This is a tooltip or placeholder that helps users fill the form. Supports Tokens

These attributes are inserted onto the field's html tag (input,select,etc) and can be used by javascript libraries or CSS.

These expressions run on the client side to dynamically control fields. Reference fields by their token syntax, for example [FirstName].
Only client side tokens are supported. Examples of these include simple field tokens like [<fieldname>] for a Text or Dropdown field.
You may not use server side tokens. Examples of these include tokens generated on submit like [<fieldname>:Text] or [<fieldname>:Value] for a Dropdown field.
You may not use tokens defined in Configuration/Tokens.
You may not use tokens generated by actions during form Events (On Page Load, On PreInit, On Init).
If you want to evaluate your tokens against a boolean value, for example [TextBox]=="True", please take into consideration the fact that the values inside the token will be replaced with the JavaScript boolean values. Because of this, the correct syntax to evaluate against a boolean value is [TextBox]==true / [TextBox]==false.

Dynamically show or hide this field. This must be a boolean expression. Use standard javascript boolean operators (==, !=, <,> , !). For example, use [PaymentMethod] == 'CreditCard' to show the credit card field only when the Payment Method is set accordingly.

Dynamically enable or disable this field. This must be a boolean expression. Use standard javascript boolean operators (==, !=, <,> , !). For example, use [PaymentMethod] == 'CreditCard' to enable the credit card field only when the Payment Method is set accordingly.

Dynamically compute the value of this field. So when other fields change this fields updates automatically. Use standard javascript operators where needed (+, -, *, /). For example, use [FirstName] + ' ' + [LastName] to automatically fill the Display Name field. Note that once the value is edited manually, the automatic synchronization stops.

Bind some javascript code to execute when the value in this field changes or when a button is clicked. Access the form fields by using syntax [FieldId] which maps to the js object form.fields.FieldId.value. For buttons, you can "return false;" to prevent the form from submitting.

Supports Tokens

Additional CSS styles. Supports Tokens

Supports Tokens

Additional CSS styles. Supports Tokens

This boolean expression is used to determine if this field validation will execute. It supports C# syntax. A common example is [SomeField] == "Some Value" or [SomeField].IndexOf("something") == 0. This field supports Tokens.