| Setting | Data Type | Description | If Not Set | Can be set on Interact Form_Settings Level | Can be Set for a View |
| form_file | STRING | Defines path to the form file that should be opened and used for interaction. If you use the InteractCurrentForm() function, the form_file setting will be ignored. | If this is not set, Lycia will use the currently opened / focused form. | Yes | |
| id | STRING | If the form has more than one collection of settings (View), id is the identifier for a certain collection. You can define the id with the value “ “ (one blank symbol) to prevent LyciaLowCode from merging settings from the form file, LyciaLowCode will ignore settings in the form file. | If the id property is not defined in .4gl file, LyciaLowCode will merge settings with the first setting from the form file (if it exists). | Yes | |
| log_file | STRING | Enables the errors output to the log file in addition to the on-screen output, and contains the path to the error log file. | If this is not set, the errors will be displayed on the screen only. |
Yes |
|
| translations | HASHMAP OF STRING | This setting is a map of translations for built-in LowCode messages. | Yes | ||
| views | HASHMAP of View | This setting is the mapping for settings for interaction with the specific database table. At usage, it has to reference the name of the database table. | If the form file doesn’t have definition of the property interactSettings, then qxcompat tool will implicitly add this property during the compilation of the form file. |
Yes |
|
| actions | HASHMAP OF HASHMAP | Defines a list of custom actions that should be added to the interaction. | Yes | Yes | |
| actions_on_done | HASHMAP OF HASHMAP | Custom actions "Sub-Interaction - Action - Function", which will be added to the subdialog of the defined View (or the whole program if there is only one View in the program), and will be executed after LyciaLowCode executes the built-in events. | Yes | Yes | |
| view_attributes | HASHMAP OF HASHMAP | Defines a list of custom attributes that should be applied to the main dialog or to the subinteraction. You can use any of the DIALOG, INPUT, DISPLAY ARRAY, INPUT ARRAY or CONSTRUCT attribute clauses. | Yes | Yes | |
| paged_mode | INT | Activates the paged / buffered mode of the on-screen output (in this case it will take less time to start the interaction). If set to 1, then DISPLAY ARRAY or INPUT ARRAY will be in paged / buffered mode and will use the ON BUFFER block. | If this is not set, the entire table data will be loaded at the program runtime. | Yes | Yes |
| input_mode | INT | If set to 1, adds the INPUT ARRAY interaction. | By default, LyciaLowCode makes DISPLAY ARRAY interaction with Insert, Update, and Delete actions. | Yes | Yes |
| pessimistic_locking | INT | If set to any positive integer, will enable processing the database row updates using pessimistic row locking. | If this is not set, LyciaLowCode will use optimistic row locking. | Yes | Yes |
| confirm_accept | INT | If set to positive integer, adds the Accept changes confirmation dialog box the program will display after the user clicks the Accept button during INPUT. It is a Button dialog box, asking to confirm the changes (Save / Cancel / Continue actions). | This dialog box is disabled by default (default value is -1). Set to 1 or any other positive value to enable. | Yes | Yes |
| confirm_cancel | INT | If set to positive integer, adds the Cancel changes confirmation dialog box the program will display after the user clicks the Cancel button during INPUT. It is a Button dialog box, asking to confirm the changes (Save / Cancel / Continue actions). | This dialog box is enabled by default (default value is 1). Set to -1 or other negative value to disable. | Yes | Yes |
| screen_record | STRING | Mandatory property. Defines the screen record that should be used for interaction. It should be defined in .4gl file or in the .fm2 form file. After merging 4gl-defined and form file-defined settings at runtime, LyciaLowCode should have this property, otherwise it will raise an error. | If this is not set, LyciaLowCode will search for the screen record with the $primary$ prefix (if you had one), use that screen record for interaction, and add the interactSettings property implicitly with the appropriate view definition. | Yes | |
| not_update_fields | DYNAMIC ARRAY OF STRING | Defines the list of fields that should not be activated on user clicking the built-in Edit toolbar button. | Yes | ||
| sql_where_search | STRING | Defines a WHERE clause that will be used from the beginning. Can be modified at runtime with clicking the Filter button on the toolbar. | If this is not set, data filtering is managed by database settings. | Yes | |
| sql_where | STRING | Defines aWHERE clause of the main query that can not be overwritten by the user at runtime. sql_where is concatenated with sql_where_search; can’t be modified by the program user. | If this is not set, data filtering is managed by database settings. | Yes | |
| sql_order_by | STRING | Sorts data in ascending or descending order (using ORDER BY). | If this is not set, data sorting is managed by database settings. | Yes | |
| sql_top | INT | Defines the number of rows to limit the on-screen output using the SQL SELECT TOP clause (supported databases: Informix, MS SQL Server, Oracle and MySQL). | If this is not set, the entire table data will be loaded at the program runtime. | Yes | |
| comboboxes | HASHMAP OF Combobox | This setting is a map of field names and their ComboBox widgets, SQL queries, and SQL WHERE clause. For details please see the full reference page. | Yes | ||
| lookups | HASHMAP OF STRING | It’s a map of field names and their SQL WHERE clause. | Yes | ||
| navigation_status | STRING | Displays the program user's location in the table (table row number used in the interaction) in relation to the total table row number. | Yes | ||
| zooms | HASHMAP OF Zoom | This is a map of function field names and definitions of form for selecting the value. | Yes |