Vizlib Server Changelog

Vizlib Server did not respect the Custom Computer Name set in Writeback Table. Currently, the multi-node environment Custom Computer Name feature in Vizlib Server and Writeback Table works properly.

See changelog for Vizlib Server 4.20.2.

Vizlib Server did not respect the Custom Computer Name set in Writeback Table. Currently, the multi-node environment Custom Computer Name feature in Vizlib Server and Writeback Table works properly. This version is no longer available as the sessions opened both on the specified nodes and on the central node. The issue has been fixed in version 4.20.3.

MySQL integrations did not work in Vizlib Server 4.20.0. In Server 4.20.1 MySQL integrations work properly.

Updated Vizlib Server to include the newest recommended HTTP security headers.

See changelog for Vizlib Server 4.19.1.

Vizlib Server did not respect the Computer Name set in Writeback Table. Currently, the multi-node environment Computer Name feature in Vizlib Server and Writeback Table works properly. This version is no longer available as the sessions opened both on the specified nodes and on the central node. The issue has been fixed in version 4.19.2.

The software performs the SSL certiciate validation and informs you whether the certificate you provided is valid. For more information, see SSL Certificates.

The following improvements have been introduced to Logs Browser:

• Added the Reset to default button.
• Added the x icon to remove individual inputs in the Logs Browser.
• The To field of the Custom interval changed from mandatory to optional.
• Added the badge in the Operation column with a number of operations performed.

For more information, see Logs Browser.

When you installed fresh backend on the Cloud, the CSP button in Vizlib Management Console (VMC) was incorrectly displayed in the red color suggesting that CSP was not defined. When you selected the Autofix option, the button became green, but after refreshing the color was changing back to red. Currently, the button works properly.

When you wanted to check the comments made for Vizlib Teamwork and Vizlib Finance in the Comments browser & archiving view in VMC, the App Name and Sheet Name fields were empty. After the fix, the fields are filled with proper values.

insightsoftware introduced a number of fixes to Snowflake integration form, including Key Pairs handling.

Some owner searches in the VMC in SaaS environment were returning the \[object Object]\ result. Currently, the owner names are properly displayed.

In this release, the following improvements have been implemented:

• general improvements

• error handling improvements

• changes for compatibility with extensions

The notification badge did not show the message about user mentions in the Teamwork extension.

Sharing messages through Slack or e-mail did not work in the Teamwork extension.

[Qlik Cloud] Writeback button was grayed out for some users when they were using space access security rules.

Pagination has been introduced to the following views inside the Vizlib Management Console (VMC) to facilitate navigation across the software:

• VMC > Security Rules

• VMC > System Settings > Integrations

• VMC > Teamwork Settings > Streams & Security > Teamwork Streams

• VMC > Teamwork Settings > Workspaces > Teamwork Workspaces

• VMC > Teamwork Settings > Workflows

• VMC > Writeback Settings > Destinations

• VMC > Writeback Settings > Lock Groups

• VMC > Writeback Settings > Loop & Reduce Tasks

• VMC > Finance Settings > Streams & Security > Finance Streams

• VMC > Finance Settings > Workspaces > Finance Workspaces

• VMC > Finance Settings > Finance Report Scheduler > Finance Report Schedules

Pagination enables you to sort the content by using filters. The first filter available at every view with pagination implemented helps you identify the content, for example, by name or title. Depending on the view you’re at, you can use the following filters:

Description: VMC > Security Rules

ID:

• VMC > System Settings > Integrations
• VMC > Writeback Settings > Destinations

Name

• VMC > Teamwork Settings > Streams & Security > Teamwork Streams
• VMC > Teamwork Settings > Workspaces > Teamwork Workspaces
• VMC > Finance Settings > Workspaces > Finance Workspaces
• VMC > Finance Settings > Streams & Security > Finance Streams

Title

• VMC > Writeback Settings > Loop & Reduce Tasks
• VMC > Finance Settings > Finance Report Scheduler > Finance Report Schedules

The following filters are common for the views with pagination implemented:

• Owner – text field you can use to filter the content by its owner.

• Sort by – a dropdown you can use to sort the content by edited or created items.

• Sort order – a dropdown you can use to sort the content in an ascending or descending order.

• Type – a dropdown you can use to filter the content by type, like email or slack. Available only in VMC > System Settings > Integrations and VMC > Writeback Settings > Destinations.

• Status – a dropdown you can use to filter the content by status, like in progress or pending. Available in VMC > Writeback Settings > Loop & Reduce Tasks and VMC > Finance Settings > Finance Report Scheduler > Finance Report Schedules.

The following buttons are additionally available on the UI:

• Clear Filters - changes the order to default.

• Reload- reloads the current view, maintaining filters and sort order.

  If you choose the Load More option and then Reload, the view comes back to 20 items per page.

  Note: The view is reloaded every time you make a change on the list, for example by adding or removing items, or applying or clearing the filters.

The notification badge did not show the message about user mentions in the Teamwork extension.

Sharing messages through Slack or e-mail did not work in the Teamwork extension.

[Qlik Cloud] Writeback button was grayed out for some users when they were using space access security rules.

You can navigate across Writeback Table using the following key combinations:

• Tab - move to the cell on the right.

• Shift + Tab - move to the cell on the left.

• Enter - move to the cell below.

Note: If you're editing text or numeric input, the first Enter accepts the input and the next Enter moves you up or down.

• Shift + Enter - move to the cell above.

If you focus on the slider, Enter or Shift + Enter moves you to the next row with focus on the slider. For the chips component, Enter or Shift + Enter moves you to the next row only if you have empty input.

Note: Enter or Shift + Enter combination isn't supported for Form View and Form. Instead, use Tab or Shift + Tab. The combination can't be used also in Text Area and for icon button.

When the customer used Writeback Table, the Reload fail window was randomly displayed with the following message: Not connected.

When the customer used Vizlib Server versions 4.13.2 and upgraded to 4.14.0, they could not access VMC and the 503 error message was displayed in the browser. When checking the logs, the following message was displayed: Downloading and Installing Required Dependencies. Upgrading to version 4.15.0 did not resolve the issue.

When the customer attempted to sign in to Vizlib Server for Qlik cloud using proxy setup, the Timeout error message was displayed.

Vizlib Server for Qlik Cloud went down and the following error from VMC/Qlik Cloud was displayed: Redirect uri is missing from OAuth Client

When the customer attempted to install Vizlib Server 4.16.0 on a standalone server running Windows 2016, the following error was displayed: Database connection token was not found or is corrupted. Please make sure it exists and check Vizlib Server logs.

Context menu 'Reset Column' value option causes memory leak.Logs Browser can be exposed to some potentially dangerous vulnerabilities and HTML tags can be passed after a part of the destination tag APPID, which later can be visible and clickable in the Logs Browser.

Disable OCSP check in Snowflake integration

You can disable OCSP check in Snowflake integration. Disabling OCSP enables for creation of insecure connections to Snowflake. To disable OCSP, use a dedicated check box in the VMC (Vizlib Management Control) screen.

Support for full and basic user entitlement

Vizlib Server API considers the basic and full entitlements of Qlik users.

Support of connection to Qlik Cloud over the proxy

You can connect to Qlik Cloud over the proxy. To establish the connection, go to VMC > System settings > Qlik Cloud and enable the Use proxy option. Then, define the following settings:

• Proxy protocol

• Proxy Host

• Proxy Port

• Proxy user (optional)

• Proxy password (optional)

Confirm the settings by clicking the Save changes button.

Vizlib Server Logs Improvements

The operation id parameter has been introduced to Vizlib Server Logs. You can identify logs in an operation by searching for operation id. operation id is visible in logs browser for auto-generated logs. To further narrow down the operations records, you can use the Search option in VMC.

Note: For some operations, you may not receive all the logs related to a performed action. If this happens, insightsoftware recommends you use the Select interval option and define the time frame of the operation you want to display logs for.

Error while upgrading Vizlib Server. When the customer tried to upgrade Vizlib Server versions v4.13.2 until v4.15.0, a 503 error appeared and the log is stuck at “Downloading and Installing Required Dependencies“.

Node 18 upgrade (ACTION MAY BE REQUIRED!)

The update to 4.14.0 comes with a potentially breaking change (security update) for users to be aware of - the update of the underlying runtime to Node version 18. Node version 18 comes bundled with a modern OpenSSL version which forces Node to use newer, more secure SSL certificate cipher suites.

This means that using an older SSL certificate, possibly encrypted with an older, currently insecure encryption algorithm might cause the VizlibServer to not be able to initiate a secure HTTPS server. To combat this issue, we included a one- time, additional flow of certificate verification that is being conducted during the installation process:

• During the installation, the installer will include an additional form for the user to input an existing SSL certificate (PFX or PEM formats).

• The user-provided certificate will be verified for compatibility with new Vizlib Server version.

• Hopefully, the validation completes with no errors and the user can proceed with the installation as usual.

• If the validation fails, take a look at the steps below, describing how to update the existing certificate to be supported by Vizlib Server.

Step 1 (optional, in case there is no standalone OpenSSL version installed on the system)

Install OpenSSL on server (https://www.openssl.org) - this will be used the system terminal to adjust certificate to meet Node 18 security requirements.

Step 2

Open the terminal in the location you saved the certificate you want to update in. This will also be the output location of the updated certificate.

Step 3

Run the following openssl command in terminal (replace oldfPfxFile.pfx with current certificate) openssl pkcs12 -in oldPfxFile.pfx -nodes -out decryptedPfxFile.tmp

If this results in an error stating 'unable to load provider legacy', you might need to first set the variable, so run this command:

SET OPENSSL_MODULES=C:\Program Files\OpenSSL-Win64\bin and try again.

If you installed in a different location than C:\Program Files, change the command accordingly.

Step 4

Run the following openssl command in terminal (replace newPfxFile.pfx with desired certificate name)

openssl pkcs12 -certpbe aes-256-ecb -in decryptedPfxFile.tmp -export -out newPfxFile.pfx

Step 5 (optional, only if issue still persists)

• Run the following openssl command in terminal (newPfxFile.pfx is certificate that will be checked - to see encryption methods used)

  openssl pkcs12 -info -in newPfxFile.pfx -noout

Step 6

Delete the decrypted file either manually or by running:

For Windows:

del decryptedPfxFile.tmp

For Linux:

rm decryptedPfxFile.tmp (edited)

Server crash with MSSQL integration with Windows Authentication. Windows Authentication on a MSSQL integration could cause a crash.

Connection error after changing destination details. When changing some destination details in Writeback table it could cause a connection error.

Incorrect Slack integration cannot be deleted if any integration is the stream. When using multiple Slack integrations and one is used for Teamwork, the other one could not be deleted until every Teamwork stream has an empty Slack integration.

Cannot get table names error after switch snowflake to QVD results. Changing destination types could cause issues in some situations.

Writeback destination with snowflake integration is not validated. The validation for Snowflake destinations were not properly validated.

Vizlib Server Cloud - Using space access to build security rules. There is now a new option for security rules that allows the use of space access. This should make administration considerably easier for some of our Cloud customers.

Vizlib Server - Unable to log into VMC using Virtual Proxy. In configurations with a virtual proxy setup it was not possible to log in to the VMC.

Possibility to disable VMC admin login option from not whitelisted IP addresses. This feature might be useful whenever Vizlib Server needs to be exposed for external access to enable users from outside of your infrastructure to use writeback functionality. Check our documentation for more details.

[Vizlib Server for Qlik Cloud] Performance improvements when executing application reloads. We modified mechanism which is used to conduct reloads, when app reload is configured in a destination. This change will improve performance as reloads should no longer be queued. This change does not affect automation-based destinations.

Error "Socket has been disconnected" when writeback large data sets. On larger data sets we would experience disconnections. This is now fixed.

Vizlib Management Console - Logs Browser - Audit Logs.We introduced new type of logs that are collected by Vizlib Server called Audit Logs. Those logs are created every time something is changing in Vizlib Server's configuration. In addition they capture events like signing in or out, password change, server restart etc. Root admin access level is required to be able to see the logs.

Vizlib Server - Logs Browser Improvements. To allow swifter troubleshooting, we enhanced the capabilities of the Logs Browser screen. It now also allows filtering logs by providing a custom time interval. Apart from that, the current search can be exported to CSV file, which may be helpful when sharing logs with our support or doing internal trouble-shooting across teams.

Vizlib Server for Qlik SaaS on Windows.Until this point, in order to run Vizlib Server with Qlik SaaS, the tenant had to be configured with a docker container. Starting from this version we also provide a Windows installer, which might be more convenient for customers who are more accustomed to Windows environments. The new option to download is available from our User Portal.

Vizlib Management Console - Shared access to security rules with VMC Admin level. With this feature Content Admins are allowed to share edit permission to security rules that grants VMC Admin level access to other Content Admins. It might be very handy when distributing responsibilities from individuals to whole teams.

Vizlib Server for Qlik Cloud - Writeback Table gets stuck after app reload since version 4.12.1. Issue affected tenants with large users volume, it took a very long time for the table to refresh and unlock.

Postgres upgrade to version 14.8.The PostgreSQL version has been updated to be more up to date.

Improved license management for collaboration / finance in Vizlib Management Console. Besides available filtering options for both Enterprise and Qlik SaaS editions, we have added a possibility to deallocate licenses for all users that are inactive, or have been removed in Qlik Sense.

New Vizlib Management Console DashboardWe gave this screen a new look and also improved it's loading time.

Vizlib Server for Qlik Cloud - Error when executing writeback. In version 4.11.1 there was a bug that could occur when executing writeback in context of Qlik SaaS. Enterprise Customers were not affected by it.

With Vizlib 4.11.1 you can configure Vizlib Server in such a way that it performs app reloads on rim nodes instead of Qlik central node. Fore information, see App Reloads On Rim Nodes.

Important: This change requires Writeback Table and Input Form version 4.11.1.

Add option to deactivate vmc_admin account. We added new possibility to disable inbuild login access to Vizlib Management Console. In order to do that, modify setup.xml file located in C:\Program Files\VizlibServer directory. You will need to add new environment variable entry -<env name="VIZLIB_VMC_USER_DISABLED" value="true" /> - to disable this setting, service restart will also be required. This change has no effect on logging by using Qlik's sessions.

Writeback Destinations - Limiting apps and sheets. When editing destinations they can be setup to only be accessible when connecting from published sheets. If a user tries to connect to it by duplicating a sheet, they will face connection error and Writeback Table / Input Form will be blocked. It is also possible to specify whitelist of applications that are allowed to connect. Applications that are not white-listed will be rejected when connecting to the destination.

Improved Permission checks in Vizlib Management Console. When accessing destinations screen users will immediately see error indicators with detailed information. This change applies for both Vizlib Server for Qlik Cloud and for the on-premise version.

Improved Vizlib Management Console Dashboard. An additional panel with Extensions information has been added. It allows users with root admin role to inspect and fix issues with particular extensions - e.g. if for some reason Custom Property VZB_Server_Url was removed from them or its value does not match Vizlib Server's configuration. In case of errors, warning indicators are clickable and related to the underlying configuration in Qlik Sense.Same feature has been added for the Content Security Policy entries for Qlik Sense SaaS.

Vizlib Server - Custom TLS Ciphers. We extended the screen with TLS options to display ciphers that would be used by Vizlib Server depending on chosen configuration. If the security policy in your company disallows usage of predefined sets of ciphers, you can override used ciphers by setting VIZLIB_CIPHERS environment variable inside C:\Program Files\VizlibServer\setup.xml file.

Finance Comments on Qlik Cloud with Vizlib Server. Rumors say that the entire world is moving towards the cloud... so are our Finance Comments! Known and loved feature is now also available in an enterprise grade class for Qlik SaaS customers!

Writeback - Rest destination - support for untrusted certificates.In some rare cases you might want to configure REST integration to intranet endpoint that is being served with a self signed certificate. We added a setting that can be enabled to skip certificate check when sending requests to such endpoints. Should be used only if necessary!

Vizlib Server for Qlik Cloud - User Roles search. We added a possibility to filter for users in both Collaboration and Finance Users pages in the Vizlib Management Console.

Node upgrade to version 16.16.0. The underlying Node version has been upgraded to version 16.16.0. Within one of the upcoming releases we will upgrade to version 18.

Finance Report Scheduler. Report in constant 'executing schedule' phase with errors in logs.

Vizlib Server for Qlik Cloud. Transferring ownership for VMC writeback destination timeout.

Vizlib Server. Not possible to put a reverse proxy URL in Extension server URL field.

Vizlib Server for Qlik Cloud - Failed to get the API key error message (403) when logging in to Vizlib Management Console. There was an issue that prevented users without tenant admin role in the Qlik tenant to sign in to VMC.

Snowflake integration form invalidation bug. Sometimes it wasn't possible to submit a form despite of it being valid.

Validation fixes for creating SQL Integrations when using connection string option. There were cases when invalid connection string was accepted and that was causing further issues.

Teamwork: Changes made to workflows are not persisted. There was a bug which was preventing changes from being properly saved.

Snowflake - Timeout setting. We added new setting for Snowflake Integrations to adjust the timeout value when connecting to Snowflake API. This will help some users to establish connection when using slower networks.

Postgres SSL certs paths are not exported in config.There was an issue that paths used for Postgres Integration were not saved when exporting config which lead to an error when trying to import it back.

Vizlib Server: Issues with Writeback destinations screen after upgrade from 4.8.x. Two issues have been addressed. There were additional cases when Destinations view was not loading properly after upgrading from previous versions. Also security rules based on Qlik user roles are also now properly evaluated when checking destination permissions.

Vizlib Management Console - Destinations are not loading after upgrading to v4.9.0. In some cases, after upgrading to version 4.9.0, the destination screen was not loading.

Scheduled Task Destination Locking. This feature is useful in Writeback scenarios where an application used is being reloaded frequently by a Qlik Task on a scheduled basis - e.g. because data is fed from an external datastore every hour or even more often. The feature will automatically lock the Writeback Destination from being used by end users for the defined amount of time before the scheduled task starts. This prevents unexpected errors from being thrown when both the Writeback user and a QMC Task make an attempt to reload the same application.

Enable SSL for postgres databases. We added new option to authenticate to Postgres database, either one used by Vizlib Server to store its configuration or another instance used to store your Teamwork comments or Writeback data.

Vizlib Server - Extension server URL changed automatically after server restart. The extension server URL would change automatically after restart of Vizlib Server. That is fixed and we also improved the logging to be able to better track similar issues.

Cloud - Destinations are not shown. In some cases destinations were not loaded and shown in the extension.

Qlik Cloud - wrong API key used when Qlik user has a root admin role. There was an issue that users with root admin role wasn't able to connect to Writeback Destinations created by them. They had to either have content admin permission, or the destination had to be created as a server root user.

Logs Browser Improvements [Breaking Changes]. We are introducing a new version of the Logs Browser in The Vizlib Management Console (VMC). Key change is that after the update, all newly created logs, will be stored and read inside Vizlib Database, instead of separate logfiles. This means that after the update, history of logs visible inside Logs Browser, will display only logs created since the update. Former logs will be still available in logfiles on disk. Ability to create logs to filesystem is still retained and can be used as a troubleshooting backup in case when there are issues with establishing database connection. It can be disabled from VMC.

Vizlib Server - health check module - extensions not able to connect to Vizlib Server. After upgrade to v4.8.0 for some customers Collaboration extensions reported an issue related with certificate, which was a false positive. We fixed this case.

[Qlik Cloud] Finance Report Scheduler. We integrated the Finance Report Scheduler feature for our customers who are using Qlik Cloud.

We have introduced several improvements to the Vizlib Server on top of the Qlik Cloud. We focused on empowering the Content admins, to make it easier for them to create and administrate writeback destinations and applications. Content admins can configure their own API keys, which will be used by all destinations they have created. This ensures enterprise- level security access to your Qlik Cloud tenant.

Writeback - Snowflake keypairs. New authentication option has been added to the Snowflake authentication. Now apart from the standard username and password model, you can also choose key pairs.

[Qlik Cloud] Writeback - Cloud automations improvements for Input Form [BREAKING CHANGE]. We modified how writeback data is being sent to Qlik's automation API, to include custom payload schemas. Automations created with prior versions of Vizlib Server might have to be altered to work with the new payload structure. Easily integrate with various APIs and build sophisticated conditions based on the payload structure.

Improved connection error messages. With this change, it will be much easier to troubleshoot and figure out a solution, when your extension struggles to connect to the Vizlib Server.

Qlik Cloud - Writeback app reload does not work. Fix for a bug, that was introduced in version 4.7.0, which was preventing to trigger app reloads appropriately in Qlik Cloud.

Docker compose setup script changes - Qlik Cloud sign-in [BREAKING CHANGE]. We simplified some steps in the setup script used to generate docker-compose file for Vizlib Server for SaaS. There is one breaking change which may affect existing installations. From now on the docker-compose file will contain password in a plain-text format. If you have used setup script in one of the previous versions there is a high chance that your docker-compose file contain Vizlib Management Console admin's password in a hashed format. This will no longer work when upgrading to this version.

Action required: ensure that your docker-compose file contain VMC admin's password in a plain text format.

Enterprise customers are not affected by this change.

Writeback - Improvements to queue handling when multiple users write to the destination at the same time. New setting `Reload Buffer' is added to Locking section for Writeback Destinations of Insert mode. This setting allows multiple writeback requests to be gathered in one batch request improving overall usability of the table being used by multiple users at the same time.

New option for dynamic tags - Sheet ID.

Simplified access to VMC when using only one virtual proxy.

Finance Report Scheduler gives error "Cannot read property 'qText' of undefined" .

Issues with writeback when using Timestamp column.

Vizlib Server - Users section improvements.

Improvements to REST Payload Schema Editor.

[Enterprise & Cloud] Silent installation improvements.

Logs Browser access for Content Admins.

Server restart improvement.

Error: Http auth controller refreshToken failed with error: Unauthorized inside Logs Browser.

Vizlib Silent installation.

Snowflake Integration with proxy issues .

Config import doesn't work.

Teams Integration not working while using proxy.

Writeback Destinations - Integration Error Although Destination set to Public.

BigQuery connector error (lost file bigQuery-1.json) after upgrade VL Server to 4.2.0.

Vizlib Server: Websocket error when connecting from Writeback extension.

Upgrade from versions < 4.0.0 issues.

[Writeback] Search in Writeback Audit is case sensitive .

[Writeback] Dynamic tags - Year tag is broken.

[Writeback] Some QVD data sources were not filtered out when creating destinations.

(Enterprise Version Only)

[VMC] - Finance Report Schedules - unable to create new reports or edit existing ones.

Version 4.3.0 had a defect that prevented new finance report schedules from being created. It was also not possible to edit existing ones.

(Enterprise Customers Only)

[Writeback] Loop and Reduce - with loop values from source app dimension.

In the initial version, when defining the Loop and Reduce tasks, users had to enter (or paste) loop values manually. It is now possible to select a dimension from which those values will be automatically fetched. This will be particularly useful when needing to loop through many values.

(Enterprise Customers Only)

[Server for SaaS] Cloud automations - API update after Qlik release.

Recently Qlik has officially released the official version of the automations API, and some changes were required on our side.

(Enterprise Customers Only)

[Writeback] Destination time zone.

This feature allows you to specify the time zone in which dates are going to be saved. The current implementation was assuming that all dates with time were written in GMT+0, which could cause issues for some users. A new setting allows you to specify that saved dates are saved according to the destination (e.g. Postgres database) time settings.

The setting is available under Default Settings inside Vizlib Management Console and applies to all Destinations configured.

(Enterprise Customers Only)

Installer improvements.

We added several smaller improvements to the installer, including better port number validation, check for provided password strength, and link updates.

(Qlik Cloud Version Only)

Issues while logging in to the VMC by using OAuth.

When the token expired, it was no longer possible to log in. The issue was visible when signing in with Qlik Cloud and when trying to reaccess it after the session had ended.

Config import is not working.

Due to issues with the validation of the API key, imports of configurations did not work.

(Enterprise Customers Only)

MSSQL Integration - Windows Authentication support.

Allows to connect to MSSQL databases with Windows Accounts.

(Enterprise Customers Only)

Finance Report Scheduler.

Schedule delivery of Finance Report to the right audience with an automatic task.

(Enterprise Customers Only)

Teamwork Mentions - Very slow to find a match when typing username.

In setups which large users volume, mentions were working slowly. That has been optimized now.

(Enterprise Customers Only)

Writeback Audit export - Loading indicator is still visible after exporting to CSV.

(Enterprise Customers Only)

Vizlib Log File consuming lots of space on disk.

In some scenarios, log files generated by Vizlib Server were consuming a lot of space on a disk. We introduced a rotation mechanism that prevents this from happening.

(Enterprise Customers Only)

Snowflake Integration - Proxy support fix.

Fix delivered the port parameter was not accepted properly by snowflake-sdk.

(Enterprise Customers Only)

MS Teams Integration - Proxy support.

It is now possible to configure MS Teams Integration in the Vizlib Management Console while using http(s) proxy.

(Collaboration Enterprise Customers Only)

Snowflake Integration - Proxy support.

(Enterprise Customers Only)

Installation issues with Vizlib Server 4.1.0.

There were issues with the previous Vizlib Server version due to dependencies updates for Postgres DB and Snowflake SDK.

Upgrade Postgres SQL to version 14.1.1.

The default database installed with Vizlib Server will be automatically upgraded to a newer Postgres SQL version during this update.

This will not affect external databases connected to the Vizlib Server nor external DB chosen during the installation.

[VMC] Security Rules search engine does not work for some resource types. Searching for Resource ID sometimes did not return any results. (Only related to some resource types) .

[VMC] Security Rules, creating new security rule can fail when there is a child group.

When a child group was created, sometimes an error message with "validation error..." would show up. The validation message is now more user-friendly.

[VMC] MS SQL Integration - instance name fix.

Use of an instance name would break the connection to MS SQL Server.

[Vizlib Server] Extension Server URL custom property in QMC is getting changed without any actions.

There was an issue with using HTTP that could get changed to HTTPS.

[Vizlib Server] Writeback - cannot create a table without at least one column connected to the data model.

The issue was reported for Snowflake but could happen with other integrations too.

[VMC] Random errors displayed after performing a server restart. Related to the user login, more specifically, it was an issue for non-admin users.

[Vizlib Server] Silent installation fixes.

Postgres connections would sometimes get set up incorrectly.

[Vizlib Server] Writeback - Validate Fields does not work properly with QVD destinations.

Validation of fields did not work properly for QVDs and would throw an "Export failed" message.

[Vizlib Server] Security Rules - Entered values are not trimmed.

That could cause unexpected behaviors when copying and pasting values with additional whitespace characters.

Export Writeback Audit log.

Vizlib Server - General improvements to error handling.

Server-side Writeback - "Table already exists" error thrown when writing to snowflake destination

VMC Dashboard - Cannot connect to QES for rim nodes.

Email Integration - Connection to local SMTP server fails.

Additional Security settings including TLS version, HSTS, XSS, and CRSF tokens.

Node.js version upgrade to 12.22.3.

Improvements to the Writeback Destinations page.

Oracle Writeback Destinations - support for schema names.

Installation - support for using an existing database.

[Writeback] - Decimal numbers are written to QVD as text while using commas as decimal separators.

Vizlib Management Console - Improvements to Qlik Sense section (engine port).

Bug in Lock Groups after config import.

Silent Installation - Support for adding certificates (pfx, pem format) as parameters.

Fix for Writeback Delete operation not working for server-side destinations.

Vizlib Management Console (VMC) - Visual Improvements.

VMC - Teamwork Workflows Screen Redesign.

VMC - Logs Browser Style Changes.

Socket disconnected error pops out during bulk edit on larger data sets.

Writeback - improvements for SQL autogenerated columns.

Special characters in stream/integration ID break possibility to edit them.

Support for silent installation.

Vizlib Management Console v1.4.0, including new options for resource management.

Adding faulty slack integration can corrupt VMC.

(Collaboration Enterprise Customers Only)

Slack Integration - Proxy Support.

(Collaboration Enterprise Customers Only)

Vizlib Management Console - Comments browser, column picker, and additional columns for app name and sheet name.

Vizlib Management Console - New look and feel for the Integrations page.

Issues after editing main db integration.

Vizlib Management Console - Empty destination list for content admin users.

Change VMC admin credentials in VMC.

VMC - Modal not closing when navigating from Teamwork streams to the Users page.

New Server Version Notifications.

VMC - No horizontal scroll for writeback audit trails with lots of columns.

Creating an integration from a writeback destination view is not working.

Newly created finance and teamwork workspaces cannot be picked while editing streams.

Management Console - Multi-user access with roles and security levels.

Unable to find data source when using QVD destination type through Vizlib Server.

Setting an invalid certificate breaks the possibility of login to VMC (using HTTPS or HTTP).

Creating or updating streams/destinations improvements.

Importing config with advanced security rules clears conditions.

No toast on delete stream error.

[Enterprise only] VMC integrations and destinations management improvements.

A massive improvement has been introduced to the VMC. You can now manage integrations and writeback destinations without having to restart the server. Changes are applied instantly and take effect without having to reload the Qlik Sense dashboard.

(Collaboration Enterprise Customers Only)

[Writeback Table] Setup issues when configuring REST destination.

[Input Form & Writeback Table] Fix when using server-side destinations with reload tasks.

[Form & Table] New Writeback Destination - Oracle.

[Table & Form] Audit columns for server-side destinations.

[Table & Form] Automatically lock server-side destinations when writeback is performed.

[Table & Form] When writing back to the SQL destination Timestamp column is empty.

[Table & Form] REST destination issue with a basic authorization token.

Support for Vizlib Input Form and Vizlib Writeback Table. New sections in VMC for configuring Writeback destinations.

(Collaboration Enterprise Customers Only)

Unable to find data source when using QVD destination type through Vizlib Server.

Note: Vizlib Server Update from version 1.7.0 to 1.7.1 is required for the fix to apply.