<< Click to display table of contents >>
Figure 15: Custom area settings
Path: <area><settings><customareasettings> Contains references to the SQL scripts that are run when retrieving or saving data for the area. Note! The child elements of <retrievesql> and <savesql> are identical so they are described in the following only once. |
Path: <customareasettings><retrievesql> Defines the settings for data retrieval. This parameter is not needed if no data needs to be retrieved to the template when the template is opened. If you define EXECUTE type SQL clauses for opening a template, you cannot refer to the column IDs in the same way as in saving sheets. |
Path: <customareasettings><savesql> Defines the SQL clauses that are run. Several SQL clauses can be used, and the SQL clauses can be divided into several transactions. Each transaction can contain one or more references to an SQL clause. The transactions are run according to the order defined with the <transactionorder> element. |
Path: <customareasettings><retrievesql>/<savesql><transactions> Several SQL clauses can be used, and the SQL clauses can be divided into several transactions. Each transaction can contain one or more references to an SQL clause (which are defined document-specifically with the <sql> element). The transactions are run according to the order defined with the <transactionorder> element. |
Path: <customareasettings><retrievesql>/<savesql><transactions><transactionorder> Lists the transaction IDs in the order in which they will be run. |
Path: <customareasettings><retrievesql>/<savesql><transactions><transactionorder><listitem> |
Path: <customareasettings><retrievesql>/<savesql><transactions><transaction> Attributes id: Transaction ID |
Path: <customareasettings><retrievesql>/<savesql><transactions><transaction><sqlorder> Lists the SQL clause IDs in the order in which they will be run within the transaction. |
Path: <customareasettings><retrievesql>/<savesql><transactions><transaction><sqlorder><listitem> |