# Widgets
## `Readonly`
**Description:** A non-editable text input that can be used to present a value directly from a Qlik Field
**Mode:** Here you define whether to show a field from your data model or use an expression to show a calculation.
**Options:**
* If your selected field is the association between your data model and write-back data then check the `Komment Key Field`.
{% hint style="warning" %}
We recommend to place the widget holding the Komment Key Field as the first widget
{% endhint %}
{% hint style="warning" %}
To be sure not to have any conflicts with Qlik's data load, try to avoid special characters such as '/' or '<>' in your Komment Key Fields
{% endhint %}
**Expression:**
When using an Expression you just use normal Qlik syntax. However, be sure to remove the equal sign before the expression. Otherwise Komment won't be able to evaluate it correctly.
It is possible to use the Expression to show a **field from another table** in your data model. You need to make a small tweek but it is actually quite easy:
Write Field name in Qlik Expression => Switch to Field Mode
**Total row:**
You can enable the table to show a Total row for your expressions. Here you also define which aggregation that should be used:
**Display as URL:**
For Readonly widgets it is possible to choose to display the content as a clickable URL.
In the Komment table the user will be able to click on the URL which will open up in a new tab:
## `Field`
**Description:** Works like a hidden Readonly widget but the data contained in the Field value is saved.
**Use cases:**
* Use it when you want to save additional data together with the editable widgets.
* Could be key fields you want to store with the rest of the created data but that should not be visible to the end user.
## `Text`
**Description:** Plain text input, mainly for free text.
**Options:**
* Choose between a single line or multiple line display
* Ability to limit the maximum number of characters a user can write
## **`Date`**
**Description:** A date picker to easily select a date from a calendar view
**Options:**
* Select via a calendar view
* Type date directly in widget
* Define the format in which the date should be displayed
## `Dropdown`
**Description**: A drop-down menu with configurable options as input data
**Options**:
* Define possible values manually
* Load possible values from Qlik data field or variable (e.g. use the **concat** function like this in the Options field: `Concat(distinct [First Name],';')` )
* Enable a search option for the users
* Enable users to add their own options in case the possible ones are not sufficient
* Allow for the selection of multiple values
## `Group`
**Description**: Similar to the Select option but renders the options as grouped buttons
**Options**:
* Define possible values manually
* Load possible values from Qlik data field or variable (e.g. use the **concat** function like this in the Options field: `Concat(distinct [First Name],';')` )
* Define colors for each button
## `Number`
**Description**: A numeric input field formatted as a number
**Options**:
* Define **Number Type**. Can be set to either Number or Percentage
* Define number of D**ecimals** to be included
* Enter number directly in input field
* Toggle number up and down directly in widget
## `Check`
**Description**: Works as a check box to easily indicate e.g. completion of a task
## `Variable`
**Description**: This widget is not visible through UI. It’s used to pass a hard coded/calculated value to the back-end when saving comments. It is mainly used for meta info to control customized saving procedure during data reload.
**Options**:
* Define either a hard-coded or calculated value that is passed to a variable
{% hint style="info" %}
Remember to define the variable name in the variable editor or in the data load editor
{% endhint %}
## `Validation`
**Description**: Use this for any conditional checks before saving the input. A validation expression is required here to check if the input data is fulfilling requirements and limits. Check the other widgets’ content by evaluating the binding variables in each widget.
**Options**:
* Define exact expression to be used for a given validation step - e.g. only allow for 1 record to be saved each time.
* Define the desired message the user should be presented with when the validation expression is not met.
{% hint style="warning" %}
The validation widget is not valid to use in Table mode.
{% endhint %}
## `Container`
**Description**: This widget is only relevant to use when Komment is in `Form`or `Popup` mode. The Container widget is used to group the other widgets. It is possible to give each widget a custom label that is visible to the end user:
**Grouping:** The widgets to be grouped together are simply arranged below each container widget that. i.e. you can have multiple Container widgets included in each Form.
**Display:** You can use the settings for Column and Row span for each Container widget to define how they are displayed within the Form.
In the example above with the three Container widgets the settings for each of them are as follows:
* **Container 1:** Column (12) | Row (1)
* **Container 2:** Column (8) | Row (1)
* **Container 3:** Column (4) | Row (1)
## `Notification`
**Description**: This widget is to be used when you want to allow users to save data that can be used to send notifications to other users via mail or messenger apps.
**Current scope:**
* The widget is setup to save data that can be passed on to other systems or services out side Qlik Sense and Komment. e.g. you need to use for instance a trigger in your MS SQL DB to pass on the information that is saved in the notification widget. However, it should also be possible to rely only on Qlik scripting if you follow this tutorial:
* Currently it is only possible to select one user to which the notification can be sent to
**Options:**
* Define the Field name in the Fact table which should hold the saved data
* Define the user names, user initials, emails etc. which can be selected
* Define the name of the button shown to the end user
**Display:**
The user can select:
1. The user who should receive a notification
2. The field in the Fact table they should pay attention to
3. A free text message
**Output:**
The input from the user is stored as a string value in the chosen Field. In addition the URL to the Qlik Sense app and sheet is stored as well which makes it easy to get the notification recipients to go directly to the place where you want them to take action.
Example of the output:
```
lam|Country|Message about USA|https://qliksense22.s-cubed.local/sense/app/8c807dee-1391-4fc7-93cd-4454a7d14e0a/sheet/e905116a-f41d-4568-846d-5ff558b1e20d/state/analysis
```
1. User = lam
2. Field of interest = Country
3. Message = Message about USA
4. URL to sheet in app =
###
