How it works
For a business / end-user perspective of the usage of QQhelper, please follow the links above.
For a technical perspective of QQhelper functionality, please have a look to the following diagram:

Data inputs of QQhelper
The data used to feed in QQhelper is coming through 3 major processes (dark blue arrows):
- the automatic collection and processing of the metadata regarding the content of the QlikView files
- QQextractor is collecting all the existing relevant objects and their relevant properties
- QQdocumenter is the process of human introduction of all explanations
- QQtaxonomy includes the human definition of a taxonomy in order to allow conceptual associations bewteen equivalents terms (inlcuding here also the abbreviation both local or ogf the industry)
Data outputs of QQhelper
Once the required data has entered QQhelper, there are 8 different processes of providing back this information in dedicated structured ways to QQhelper environment:
- QQnavigator allows regular business users and helpdesk users to understand the reporting principles applied when the QlikView files have been developed as well as to easily locate the required piece of information
- QQsearch is the part of QQhelper allowing a fresh, unexperienced business user exposed to a complex QlikView BI implementation to find the way towards the required information
- QQpopulator send back the explanations to the objects within the original QVW files
- QQanalyzer is identifying the new and modified objects as a preparation for the next process the human processing of the explanations
- QQauditor is providing support to internal or external auditors to understand how reports have been calculated
- QQhelpmanager
- QQmetaalerts (or QQverify) identifies unusual ans unaccepted situations insisde the metadata
- QQprinter and QQpdf tranfers all the information to printable/PDF version, at various levels of details
- QQopener goes further with the ease of use and, once identified the exact report required, it can actually facilitate the opening of the respective piece of QlikView