Commit 32f0413a authored by Carsten  Rose's avatar Carsten Rose
Browse files

Update Multiform doc

parent 5aee0e86
Pipeline #2465 passed with stages
in 2 minutes and 49 seconds
...@@ -4353,32 +4353,40 @@ Action ...@@ -4353,32 +4353,40 @@ Action
Multi Form Multi Form
---------- ----------
`Multi Forms` are like a regular with the difference that the shown FormElements are repeated for each selected record `Multi Forms` are like a regular form with the difference that the shown FormElements are repeated for *each* selected record
(defined by 'multiformSql'). (defined by `multiformSql`).
The Form is shown as a table. The Form is shown as a HTML table.
* multiFormSql: Selects the primary record where the defined FormElements will work on. * `multiFormSql`: Selects the records where the defined FormElements will work on each.
* A uniq column 'id' or '_id' (not shown) is mandatory and has to reflect an existing record id in table `primary table`. * A uniq column 'id' or '_id' (not shown) is mandatory and has to reflect an existing record id in table `primary table`.
* Additional columns, defined in multiFormSql, will be shown in the same line, before the FormElements. * Additional columns, defined in `multiFormSql`, will be shown on the form in the same line, before the FormElements.
`
Simple Simple
====== ======
* The FormElement.name represents a column of the given primary table. General:
* It's not possible to create new records.
* Only existing records can be selected and edited in this mode. * It's not possible to create new records in simple mode, only existing records can be used.
* Per multiFormSql row, the STORE_RECORD is filled with the whole record of the primary table, defined by `multiFormSql.id`.
Form:
* Per row, the STORE_RECORD is filled with the whole record of the primary table, referenced
by `multiFormSql.id`.
FormElement:
* The FormElement.name represents a column of the defined primary table.
* The existing values of such FormElements are automatically loaded. * The existing values of such FormElements are automatically loaded.
* No further definition is required. * No further definition is required.
Advanced Advanced
======== ========
* The FormElement.name is not a column of the primary table. * The FormElement.name do not have to be a column of the primary table.
* The insert/update/delete of each non-primary table record has to be manually defined. * The insert/update/delete SQL statement (of each non-primary table column) has to be individually defined.
.. _multiple-languages: .. _multiple-languages:
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment