This section describes how Data Connections can be configured in Komment
Komment allows for three different methods to be used when saving data.
Utilizes the built-in QIX Engine API for processing the writing mechanism. Partial reload is performed by the Qlik Sense user.
Does not support Qlik Analyzer license
Kaptain is an added service that you can purchase to enhance the functionality of Komment. There are several reasons as to why Kaptain might be relevant for you:
You have a need for SQL DB storage of saved data => Kaptain enables writeback to external databases. We currently support MS SQL, MySQL, PostgreSQL, Oracle DB & MongoDB.
You have a high number of concurrent users using Komment => Kaptain can handle high concurrency cases (i.e. several users saving comments at the same time)
You will use Komment in larger Qlik applications (+200 mb) => Kaptain increase performance to near real time save and hence, better handling of large Qlik applications.
You require dynamic updates to Komment data model to be possible => Kaptain allows for dynamic updates to Komment data model without breaking with historic data structure - i.e. you can freely add new data entry fields to your existing Komment objects.
You have Analyzer licenses => Kaptain enables Analyzer users to store data using Komment
You want to be prepared for the future => Kaptain will soon make it possible to connect your Qlik Sense apps with many external services which expands the possible use cases for Komment
Just contact us if you would like to add Kaptain to your Qlik Sense writeback solution.
The setup is made in the Data Connection Settings section. The default is QIX Engine so if you don't have a plan (Standard, Pro or Premium) where Kaptain Service is included you don't have to touch this section.
- 1.Select your Connection Type
- 2.Input the URL to Kaptain service
- 1.If you have multiple environments (devl, test, prod, etc.) you can ease the setup by defining a variable that holds the URL
- 2.Then you just reference this variable in the URL field:
Test Serviceto ensure Komment and Kaptain service are connected
Be aware of the protocol, and service port, that needs to be consistent with the settings in Kaptain config file.
To setup your Komment object to work with Kaptain there are only a few steps needed. You find the Kaptain Settings Under Data Connection Settings:
Here you define where in Kaptain's internal database you want to save the data entered by the users when using Komment. A Kapsule corresponds to a collection in the database. You can think of it as a table in a SQL database.
- If you have already created a Kapsule you can select from the list
- If not, then
Create New Kapsule
- You will now be presented with the following window:
- If you want to store data in Kaptain's internal DB do the following:
- Enter a Name for your new Kapsule
- Choose KaptainDB as your database
- If you want to store data in an external DB do this:
- Enter a Name for your new Kapsule
- Choose your desired DB from the list
- If you want to use an existing table in the selected DB then choose your database table from the dropdown and press
- If you want to create a new table in your selected DB then press
Create SQL table
- Enter the name of the new table and press
- A pop-up message will be displayed indicating that the table has been created
- Select your newly created table from the dropdown
- Press outside the Komment object on the sheet and afterwards press the Komment object again
- In the Kaptain Settings menu you can now select the newly created Kapsule in the list
If you cannot find specific Kapsules in the dropdown menu, contact your admin to ensure you are setup as a Kaptain user and is member of the groups that contain the relevant Kapsules.
If you are not able to create a new Kapsule, contact your admin to ensure you are setup as a Kaptain user and has the permissions the create kapsules.
2. Use variable to select Kapsule dynamically
To be able to easily moved applications with Komment between different Qlik servers and Kaptain installations you can define the Kapsule dynamically using a variable. Here is how.
- After you have selected your Kapsule as described above, you do the following:
- Copy the Kapsule ID shown below the Kapsule you have selected
- Create a new variable using Qlik's variable editor (or define in script) and insert the copied value in the variable value
- In Kaptain settings switch on
- Input the the name of the newly created variable
Here you can create a Qlik Sense Data Connection that will ensure you can load data from Kaptain. You just choose a name and a REST connection to Kaptain will automatically be established.
- If a REST data connection to Kaptain is already created you can select this
- If not, then
- Write desired name of connection in pop-up window
OK(browser window will automatically refresh)
- Select the newly created data connection from the list
Load Full History:
Defines how much of the history data you load from Kaptain and into your Qlik Sense app on each reload (partial and full). By default only the latest record for each Komment Key field will be loaded so to get the full audit trail loaded each time toggle on this option.
When this option is enabled, Kaptain will not perform a partial reload after the user press save. This means that the stored data will only be visible in the Komment table and not any native Qlik objects. The reason is that the saved data will not be included in the Qlik data model until a full reload of the app is performed.
When to use the Skip Reload function? If you have large applications where partial reloads takes a long time. Or if you do not need to make use of the saved data in any Qlik visualizations in real time.
Reload Notification:When this option is enabled the user will see information about the partial reload status after pressing save.
When to show the Reload Notification function? If you have large applications where partial reloads takes a long time and you want to give the user an indication of the reload process.
Remember to initialize the data model again after you have finalised the Kaptain setup
Initialize Data Model
if you add new widgets or remove existing widgets in your Komment setup you need to press
Sync Kapsuleto enforce the changes to be reflected in the Kapsule.
5. Known limitations
The field names used in the Komment widgets cannot contain the following characters:
Kapsule names should begin with an underscore or a letter character, and cannot:
- contain the
- be an empty string (e.g.
- contain the null character.
- begin with the
When using Kaptain as a data connection you have a few more option in relation to the Date widget. The below settings will only affect how the dates entered in the date widget are stored in MongoDB and how they are represented in Komment.
By enabling Custom Date Format you get the possibility to set your own Date Format. Note that it is case sensitive.
If you have users in many different time zones you can also tick Ignore Time zone to ensure that the selected date will be displayed exactly the same to all users.
If you make the settings to an existing Komment object make sure to Sync Kapsule and do a full reload to make sure your changes have been applied.
Again, if you have users in different time zones then use this setting to define in which time zone the server on which Kaptain is installed resides in. This is to ensure that no date shift due to different time zones is happening when displaying dates from the date widget.
Example use case:
The server on which Kaptain is installed is in UTC -05:00 time zone.
The users are in many time zones - e.g. Europe and US.
Recommend date settings:
Ignore Timezone => Active
Server Timezone => UTC -5:00