This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
versago3:from_control [2022/10/31 12:51] dlee created |
versago3:from_control [2024/05/17 12:26] (current) dlee [Check Box] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Control Types ===== | ===== Control Types ===== | ||
| + | {{ : | ||
| ==== Section Title ==== | ==== Section Title ==== | ||
| - | |||
| The **Section Title** control is used as a divider between logical sections of a form. The use of section titles is not required but they can help the user focus on groups of associated elements. | The **Section Title** control is used as a divider between logical sections of a form. The use of section titles is not required but they can help the user focus on groups of associated elements. | ||
| Line 11: | Line 11: | ||
| ==== Detail Section ==== | ==== Detail Section ==== | ||
| - | |||
| The **Detail Section** control is used to introduce a multi-record grid into a form. | The **Detail Section** control is used to introduce a multi-record grid into a form. | ||
| This control is only displayed when the underlying data table structure is Header/ | This control is only displayed when the underlying data table structure is Header/ | ||
| - | |||
| * A Form Detail Section control is always added to a form manually. The control can be used in any column in the form. | * A Form Detail Section control is always added to a form manually. The control can be used in any column in the form. | ||
| * When the control is added you are prompted to enter the number of columns to be included in the detail row. | * When the control is added you are prompted to enter the number of columns to be included in the detail row. | ||
| * Only one Form Detail Section control can be used in a form. | * Only one Form Detail Section control can be used in a form. | ||
| + | |||
| ==== Text Box ==== | ==== Text Box ==== | ||
| - | |||
| - | {{:: | ||
| The **Text Box** control is used for capturing data that is alphanumeric (letters, numbers, and special characters). | The **Text Box** control is used for capturing data that is alphanumeric (letters, numbers, and special characters). | ||
| - | |||
| * Text Box controls can be used in any column of a form. | * Text Box controls can be used in any column of a form. | ||
| - | |||
| * Text Box controls are typically created when a database element of this type is added to a form. | * Text Box controls are typically created when a database element of this type is added to a form. | ||
| - | ==== Drop-down List (DDL) ==== | + | ==== Numeric |
| - | {{:: | + | The **Numeric** control is used for capturing data that is numeric (numbers). |
| - | The **Drop-down List** (or DDL) control is used to present users with a fixed list of choices for selection. A typical use of the DDL is to allow the user to choose “Yes” or “No” as a response. | + | |
| + | * Numeric controls are typically created when a database element | ||
| - | Drop-down List controls can be used in any column of a form. | + | ==== Select Menu (Drop-down List) ==== |
| - | Drop-down List controls are typically created manually using a property setting on a Text Box control | + | The **Select Menu** |
| - | {{::versago: | + | - **Menu Only**: the user is restricted to select one of the presented values |
| + | - **Combo Box**: will cause the system to accept any value entered by a user and add it to the list of valid values. Keep in mind that using this option will save incorrectly typed entries to become valid selection options | ||
| - | There are two types of Drop-down Lists available. | + | There are two types of Drop-down Lists available. |
| - | + | ||
| - | {{:: | + | |
| **Static** drop-down lists are the most common. In this case the report administrator manually defines the acceptable values for the list. This approach is shown below. | **Static** drop-down lists are the most common. In this case the report administrator manually defines the acceptable values for the list. This approach is shown below. | ||
| - | - Set the Control Type as **Drop-down List**. | ||
| - | - Select **Static** as the Lookup List type. A new text box is displayed. \\ {{:: | ||
| - Enter the list of valid values. | - Enter the list of valid values. | ||
| - Each value is separated by a comma. | - Each value is separated by a comma. | ||
| - The selections are presented to the user in the order of the list as it is entered. | - The selections are presented to the user in the order of the list as it is entered. | ||
| - | - The “Allow New Values” option will cause the system to accept any value entered by a user and add it to the list of valid values. Keep in mind that using this option will save incorrectly typed entries to become valid selection options. | ||
| - | {{:: | + | **Dynamic** drop-down lists are less common but are acceptable in some cases. |
| - | + | The values can be represented by a single value or by a label/value pair where the label is presented to the user and the value is saved to the database | |
| - | **Dynamic** drop-down lists are less common but are acceptable in some cases. | + | |
| - | + | ||
| - | ==== File Upload ==== | + | |
| - | + | ||
| - | {{:: | + | |
| - | + | ||
| - | The **File Upload** control is used to allow a user to upload external files into the SQL database as binary data. | + | |
| - | + | ||
| - | File Upload controls should | + | |
| - | + | ||
| - | {{:: | + | |
| - | + | ||
| - | File Upload controls are always added to a form manually as part of the form layout process. They are not associated with a predefined database column. All uploaded data is captured in a single database table named TWBS_VGO_FormAttachments. This table is in the database | + | |
| - | + | ||
| - | <WRAP center round info> | + | |
| - | Generally, a form should have only one File Upload control. | + | |
| - | </ | + | |
| Line 78: | Line 53: | ||
| “Date” and “Time” fields in Versago are always created as a datatype Date/Time. The Date Picker and Time Picker controls are then used to format the data capture presentation in the form. | “Date” and “Time” fields in Versago are always created as a datatype Date/Time. The Date Picker and Time Picker controls are then used to format the data capture presentation in the form. | ||
| - | |||
| - | {{:: | ||
| * The **Date Picker** control is used when you wish to capture either a date only or both date & time. | * The **Date Picker** control is used when you wish to capture either a date only or both date & time. | ||
| Line 89: | Line 62: | ||
| * Time Picker controls are typically created when a database element of DateTime is added to a form. The control type is then changed to Time Picker | * Time Picker controls are typically created when a database element of DateTime is added to a form. The control type is then changed to Time Picker | ||
| - | ==== Numeric Text Box ==== | ||
| - | {{:: | + | ==== Button ==== |
| - | The **Numeric** **Text Box** control is used for capturing data that is numeric (numbers). | + | The **Button** control is used to add action buttons to a form. Actions can include calling another Versago form, initiating a Bizweaver workflow, or opening a web page. |
| - | * Numeric Text Box controls | + | Button |
| - | * Numeric Text Box controls | + | |
| - | ==== Signature ==== | + | See **Button** for additional information. |
| - | {{:: | ||
| - | The **Signature** control is used to allow a user to capture a written value via a touch sensitive screen or mouse pointer and store it in the database as binary data. | + | ==== Check Box ==== |
| - | {{:: | + | The **Check Box** control is used for capturing true or false data. |
| + | * Check Box controls can be used in any column of a form. | ||
| + | * The underlying table field must be of datatype nvarchar | ||
| - | * Signature controls can only be associated with a varchar(max) database column type. | + | ==== File Upload ==== |
| - | * A Signature control should be placed in a column that is least three (3) columns wide (see row configuration) to allow adequate room for the user to “write” the information. | + | |
| - | * Set the **Control Type** to Signature. | + | |
| - | * Enter the desired **Row Span** value. This is the vertical height of the signature column. It should typically be a minimum of two (2) rows. | + | |
| - | ==== Button ==== | + | The **File Upload** control is used to allow a user to upload external files into the SQL database as binary data. |
| - | {{:: | + | <WRAP center round important 80%> |
| + | File Upload controls are not associated with a predefined database column. All uploaded data is captured in a single database table named TWBS_VGO_FormAttachments. This table is in the database where the form data is stored. | ||
| + | </ | ||
| - | The **Button** control is used to add action buttons to a form. Actions can include calling another Versago form, initiating a Bizweaver workflow, or opening a web page. | ||
| - | Button controls are always added to a form manually. They are not associated with a predefined database column. They only execute the actions included in them. | ||
| - | See **// | + | ==== Signature ==== |
| + | The **Signature** control is used to allow a user to capture a written value via a touch sensitive screen or mouse pointer and store it in the database as binary data. | ||
| + | |||
| + | * Signature controls can only be associated with a varchar(max) database column type. | ||
| + | * A Signature control should be placed in a column that is least three (3) columns wide (see row configuration) to allow adequate room for the user to “write” the information. | ||
| + | * Set the **Control Type** to Signature. | ||
| + | * Enter the desired **Row Span** value. This is the vertical height of the signature column. It should typically be a minimum of two (2) rows. | ||
| ====Image==== | ====Image==== | ||
| - | |||
| - | {{: | ||
| The **Image** control is used to display an image that has previously been uploaded into the Versago database. | The **Image** control is used to display an image that has previously been uploaded into the Versago database. | ||
| - | See **//[[versago:images_in_reports|Using Images in Versago Reports and Forms]]//** for details on using images in reports and forms. | + | ---- |
| + | **[[versago3:forms# | ||
| + | **[[versago3: | ||