Analyze usage of Qlik Sense visualization extensions across your entire environment.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
build
docs
src
.editorconfig
.gitignore
.verb.md
CHANGELOG.yml
LICENSE.md
README.md
bower.json
gulpfile.js
package.json
sense-go.yml

README.md

sense-extension-governance

Governance for Visualization Extensions in Qlik Sense

Analyze usage of Qlik Sense visualization extensions across your entire environment.

(Table of contents generated by [verb])

Purpose and Description

  • Did you ever want to know, where you are using a particular visualization extension?
  • Did you ever want to know if you have any broken/missing visualization extension across your environment?
  • Did you ever want to get an overview which visualization extension are used in a particular app?
  • Do you want to prevent users getting an "Invalid visualization" error in your deployment because you've forgotten to install your visualization extensions properly?

If you can answer one if the questions above with YES, then this solution might be interesting for you.

Screenshots

List of installed extensions

List of used extensions + apps

List of missing extensions

Installation

  1. Download the latest version
  2. Qlik Sense Desktop
  • To install, copy all files in the .zip file to folder "C:\Users[%Username%]\Documents\Qlik\Sense\Extensions\sense-extension-governance"

Usage

No configuration necessary and available, just install the extension and drag and drop it onto a sheet.

Known Issues

  • To run this extension all apps must be closed, otherwise you'll get and error message which is not fetched properly in all versions of Qlik Sense.
  • Setup with a virtual proxy is not fully supported (opening an app does not work correctly)

Related Projects

Some related projects (Qlik Sense Visualization Extensions) I have recently created:

Contributing

Contributing to this project is welcome. The process to do so is outlined below:

  1. Create a fork of the project
  2. Work on whatever bug or feature you wish
  3. Create a pull request (PR)

I cannot guarantee that I will merge all PRs but I will evaluate them all.

Author

Stefan Walther

Change Log

See CHANGELOG.yml

License & Copyright

Copyright © 2015 Stefan Walther Released under the MIT license.


This file was generated by verb-cli on November 06, 2015.