The form component hosts all fields. The best practice is that the form is the parent of all other components. If needed the IDE will then assign the form to the component automatically. PHsPeed has been designed to have one form per-page. Even if you use fields on header/footer or master-detail, the parent form is used. This way, on submit or ajax request all data from the form is transmitted and handed over to your application. You don't need multiple submit buttons, because you only have one form.

You can specify more forms, but it is not recommended. You need to be very careful not to make any mistakes assigning components to the right form.

Property Description Values
Action The action that is sent to the server when the user submits the formUse a relative url like: ./main.php. The default value should be ok.
Datasource The main datasource of a data-driven formLeave empty for forms that do not access a database.
Exe The default state the application should be in.(deprectated)
  • xExecute: Default value for submit
  • xInsert: Database form goes into insert mode (empty form)
  • xUpdate: Database form goes into update mode (current record is editable)
  • xDelete: Database form goes into delete mode. Current record is shown in read-only to allow deletion.
  • xInit: Hidden mode when a form is shown for the first time.
FieldFocus The field that should receive focus when the form comes upId of the component that should receive focus.
HasDetail Indicates that the form contains a master-detail relationshipread-only, needed for generating javascript
HasWysiwyg Indicates that the form contains a wysiwyg, needed for generating javascript
InitialFormMode The default form mode to be used when a form opensinit: default mode.
add: form opens in insert mode.
inputSize Size of the input fieldsdefault, large, small (see Bootstrap documentation)
method Method to use when submitting formGET / POST
orientation Deprecated
parameters Extra parameters to send with a submitdefault 'component=formname', can be extended with &

onDocumentReadyTriggers when the document is ready.

OnActivateTriggers when the form becomes active
OnCreateTriggers when the component is created
OnDestroyTriggers when the component is destroyed
OnSubmitFormTriggers when the user hits a submit button