qs-data-connection-analyzer-v1.5.2

Added a new field "DataConnectionSystemDefault" which indicates whether the data connection was shipped with Qlik Sense Enterprise or not. This is an inline table as it is not possible to dynamically detect, and it is entirely possible that additional data connections could be added and shipped with the product in the future, in which case this table will need to be updated. The current values of the data connections considered to be "system" are as follows:

ArchivedLogsFolder
AttachedFiles
DataPrepAppCache
monitor_apps_connector_logs
monitor_apps_qlikview_logs
monitor_apps_REST_app
monitor_apps_REST_appobject
monitor_apps_REST_event
monitor_apps_REST_license
monitor_apps_REST_license_analyzer
monitor_apps_REST_license_login
monitor_apps_REST_license_overview
monitor_apps_REST_license_professional
monitor_apps_REST_license_user
monitor_apps_REST_task
monitor_apps_REST_user
monitor_apps_REST_user_condensed
QLogs
ServerLogFolder

qs-data-connection-analyzer-v1.5.1

Resolved bug where sessionapp_ was not removed from the AppID field. Certain script logs contain this prefix that was not properly filtered out (I had missed that I had "Lower()'d" the filename, and had to change LET vAppGUID = Replace(TextBetween('$(vFileAbsolutePath)','/script/','.'),'SessionApp_',''); to LET vAppGUID = Replace(TextBetween('$(vFileAbsolutePath)','/script/','.'),'sessionapp_','');

The impact of this bug appears to be minor, as the SessionApp_ log files are predominantly an artifact of the Data Manager (data prep), and as their "AppID" did not match due to the bug, as they are session applications, their "AppID" would never match any existing application in the QRS.

qs-data-connection-analyzer-v1.4.3

Fixed an issue where LIB CONNECT TO data connections that contained brackets were not properly trimmed, and therefore didn't map back to their corresponding mappings in the QRS.

qs-data-connection-analyzer-v1.4.2

Update README.md

qs-data-connection-analyzer-v1.4.0

This release addresses the issue where web file connectors were not parsed. There is now additional parsing logic to handle "lib://" -> "]".

qs-data-connection-analyzer-v1.3.1

Updated README.

qs-data-connection-analyzer-v1.3.0

Updated README.