1 Usage of a Form EndPoint
As Forms are used to insert or update data from database, both fields
Catalogued SQL and
Catalogued transaction are needed. They are not required by database, but non-transactional forms are non-sense.
2 Form Endpoint example
In this section, we will define a complete example of a Form Endpoint.
As it was said before, to define an Endpoint, Application code, type and label fields are required. To make a complete and usable form, fiels such as Catalogued SQL and Catalogued transaction are required.
As we can see in the images below, these codes are defined in
SQL Statements and
SQL Transactions tables
2.1 SQL Statement
As defined in SQL Catalog section, this is used to define which data is printed in the view. In this example, we want to create a Form to insert a new terminal in apps_pos_terminal table. As we know that each terminal belongs to a user, we fix the user in the form getting its code from users table. The other fields need to be void to allow the user to complete data before saving it.
In this case, the SQL Output is very simple. We only have to list every field from the table to insert (apps_pos_terminal). Every field listed will be displayed as an input in the form. The input type will depend on the column type from the table.
2.2 SQL Transaction
SQL Transaction field allow de user to make the form transactions. If there is no Transaction code the form will only have readonly input fields.
As usual, the transaction code has to be define with a type and table.
The result of this endpoint parameterization is shown in the image below.
We can see at the right-side of the toolbar a
register button. Clicking on it, a transaction over the table defined in the sql transaction will be done and input data will be saved.