Skip to content

Text Input: values, types and events

Reference · Advanced · App Connect

Collect one text-based value and bind it into the page.

Collect one text-based value and bind it into the page.

  • An App Connect page; a named form when the values will be submitted.

Use Text Input for single-line text, email, numeric, date/time and similar browser controls. Choose Checkbox, Radio, File Input or Select for their distinct value models.

Select the input in App Structure.

Control or value Meaning and use
ID / NameID identifies the component in expressions; Name identifies the field in the submitted request. Use titleInput and title when those are the intended page and server names.
TypeSelect text, hidden, color, date, datetime-local, time, email, month, number, password, search, tel, url, week or range. Browser presentation varies; choose a type for the actual data and validate it at the server. Hidden is not private or trusted.
PlaceholderA short input hint. Keep a separate visible label; placeholder text disappears when a value is entered.
Static Value / dynamic ValueStatic Value supplies initial text. Bind dynamic Value for a record field, knowing later source changes can overwrite the current input and its reset default.
Required / Disabled / Read OnlyValidation and editing/submission behavior. Required does not make a disabled field submit.
Shared dynamic attributesThe inspector may list attributes shared with other form controls. Rows/Cols concern textareas; image-resize attributes concern File Input. They do not give a text input those capabilities.

Form-control data is directly under its component name, for example titleInput.value. It is not titleInput.data.value.

Control or value Meaning and use
Set ValueChanges the current control value. A later change to its bound Value can replace it and also change the form-reset default. Set Value emits Updated when the value changes; it does not simulate a user Changed event.
DisablePass true to disable and false to enable. Disabled controls are omitted from normal form submission. Read Only, where the input type supports it, prevents editing while leaving the value eligible for submission.
FocusMoves keyboard focus to the control. Give the field a visible label and a useful place in the form’s focus order.
ValidateInvokes the App Connect validation helper. Load the validation extension for this action; client validation does not replace the endpoint’s validation.
value / disabled / focusedCurrent value and UI state. Text-based controls expose strings, including most number-input reads. Convert intentionally before arithmetic.
invalid / validationMessageClient validation state/message. Render a useful field error when invalid, and handle server field errors on the form too.
Changed / UpdatedChanged accompanies user input/change handling when the value changes. Updated also accompanies programmatic value updates. Do not make an Updated handler unconditionally write a different value back into the same field.

Add titleInput with Name title and Type text. Bind a separate label to titleInput.value. Type Notebook and verify the label updates. Set Value to Pencil and verify Updated behavior. To display numeric zero through the installed Set Value path, use the string ‘0’: the underlying setter uses value || ”, so numeric 0 and false become empty text.

For an edit form, load the record before the user starts typing or apply a deliberate reset/restore action. A field bound continuously to a changing source is not an independent draft. Never bind a password or hidden input as proof that a server operation succeeded.

Use the related workflow to connect these controls to data and a verified submit result.

You can configure the control, use its actual value shape and verify the example without confusing page state with a submitted or saved value.