Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Qlik offers a wide range of channels to assist you in troubleshooting, answering frequently asked questions, and getting in touch with our technical experts. In this article, we guide you through all available avenues to secure your best possible experience.
For details on our terms and conditions, review the Qlik Support Policy.
Index:
We're happy to help! Here's a breakdown of resources for each type of need.
Support | Professional Services (*) | |
Reactively fixes technical issues as well as answers narrowly defined specific questions. Handles administrative issues to keep the product up-to-date and functioning. | Proactively accelerates projects, reduces risk, and achieves optimal configurations. Delivers expert help for training, planning, implementation, and performance improvement. | |
|
|
(*) reach out to your Account Manager or Customer Success Manager
Your first line of support: https://community.qlik.com/
Looking for content? Type your question into our global search bar:
Leverage the enhanced and continuously updated Knowledge Base to find solutions to your questions and best practice guides. Bookmark this page for quick access!
Subscribe to maximize your Qlik experience!
The Support Updates Blog
The Support Updates blog delivers important and useful Qlik Support information about end-of-product support, new service releases, and general support topics. (click)
The Qlik Design Blog
The Design blog is all about product and Qlik solutions, such as scripting, data modelling, visual design, extensions, best practices, and more! (click)
The Product Innovation Blog
By reading the Product Innovation blog, you will learn about what's new across all of the products in our growing Qlik product portfolio. (click)
Q&A with Qlik
Live sessions with Qlik Experts in which we focus on your questions.
Techspert Talks
Techspert Talks is a free webinar to facilitate knowledge sharing held on a monthly basis.
Technical Adoption Workshops
Our in depth, hands-on workshops allow new Qlik Cloud Admins to build alongside Qlik Experts.
Qlik Fix
Qlik Fix is a series of short video with helpful solutions for Qlik customers and partners.
Suggest an idea, and influence the next generation of Qlik features!
Search & Submit Ideas
Ideation Guidelines
Get the full value of the community.
Register a Qlik ID:
Incidents are supported through our Chat, by clicking Chat Now on any Support Page across Qlik Community.
To raise a new issue, all you need to do is chat with us. With this, we can:
Log in to manage and track your active cases in the Case Portal. (click)
Please note: to create a new case, it is easiest to do so via our chat (see above). Our chat will log your case through a series of guided intake questions.
When creating a case, you will be prompted to enter problem type and issue level. Definitions shared below:
Select Account Related for issues with your account, licenses, downloads, or payment.
Select Product Related for technical issues with Qlik products and platforms.
If your issue is account related, you will be asked to select a Priority level:
Select Medium/Low if the system is accessible, but there are some functional limitations that are not critical in the daily operation.
Select High if there are significant impacts on normal work or performance.
Select Urgent if there are major impacts on business-critical work or performance.
If your issue is product related, you will be asked to select a Severity level:
Severity 1: Qlik production software is down or not available, but not because of scheduled maintenance and/or upgrades.
Severity 2: Major functionality is not working in accordance with the technical specifications in documentation or significant performance degradation is experienced so that critical business operations cannot be performed.
Severity 3: Any error that is not Severity 1 Error or Severity 2 Issue. For more information, visit our Qlik Support Policy.
If you require a support case escalation, you have two options:
When other Support Channels are down for maintenance, please contact us via phone for high severity production-down concerns.
A collection of useful links.
Qlik Cloud Status Page
Keep up to date with Qlik Cloud's status.
Support Policy
Review our Service Level Agreements and License Agreements.
Live Chat and Case Portal
Your one stop to contact us.
This article is intended to get started with the Microsoft Outlook 365 connector in Qlik Application Automation.
To authenticate with Microsoft Outlook 365 you create a new connection. The connector makes use of OAuth2 for authentication and authorization purposes. You will be prompted with a popup screen to consent a list of permissions for Qlik Application Automation to use. The Oauth scopes that are requested are:
The scope of this connector has been limited to only sending emails. Currently, we do not enable sending email attachments and are looking to provide this functionality in the future. The suggested approach is to upload files to a different platform, e.g. Onedrive or Dropbox and create a sharing link that can be included in the email body.
The following parameters are available on the Send Email block:
As we do not currently support email attachments, we need to first generate a sharing link in Onedrive or an alternative file sharing service. The following automation shows how to generate a report from a Qlik Sense app, upload the report to Microsoft Onedrive, create a sharing link and send out an email with the sharing link in the body. This automation is also attached as JSON in the attachment to this post.
A scheduled reload using Qlik Data Gateway fails with the following error:
Internal error. (Connector error: Unknown reason:. Connector process started but gRPC server failed to initialize after 3 attempts (DirectAccess-1500)) The engine error code: EDC_ERROR:22013
Manual reloads may work as expected, but scheduled reloads continue to error out.
The error indicates a resource shortage.
Increase the Qlik Data Gateway VM server CPU and RAM to meet the system requirements. See System prerequisites for details.
The claims can be accessed via an API Endpoint:
For User claims:
Please log out of the tenant and re-authenticate using the new identity provider connection. Once logged in, change the URL in the address bar to point to https://<tenanthostname>/api/v1/diagnose-claims This will return the JSON of the claims information of your IDP sent to the tenant. Here is a slightly redacted example:
Explanations of the different sections in the diagnose-claims endpoint:
internalClaims
: Summary of the user in Qlik Cloud. Usually derived from the IDP claims, but also contains information specific to Qlik Cloud access control (like the user’s roles).claimsFromIdp
: The raw claims received from the IDP. For Azure AD, most likely this comes directly from Azure AD’s ID token, however groups from the ID token are not imported to Qlik Cloud, the Microsoft Graph API is used to retrieve them instead.extraClaims
: This section only applies to Azure AD at the time of writing this article, since groups are fetched from Microsoft Graph API. If groups were retrieved correctly from Microsoft Graph API , they will be shown here.mappedClaims
: Applies the extra claims mapping on top of the raw IDP claims to get the final set of claims used for the Qlik Cloud user.For Group Claims:
Once logged in, change the URL in the address bar to point to https://<tenanthostname>/api/v1/groups This will return the JSON of the claims information of your Groups sent to the tenant.
The information in this article is provided as-is and to be used at your own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
Feature requests are submitted to Qlik through our Ideation program, which is accessible via the Qlik Ideation Portal and is available for registered Qlik customers.
What would be applicable as a feature request for Qlik Stitch?
Certain fields you need are available through specific integrations, but are not currently supported by Stitch.
You're looking for additional flexibility or functionality in Stitch that isn’t yet available.
If either of these applies to you, we’d love to hear from you!
For instructions on submitting an idea or proposing an improvement, see How To Submit an Idea or Propose and Improvement For Qlik Products.
If you notice certain fields not receiving data from a specific date onward, or if data replication unexpectedly stops for some fields, it may indicate a potential data discrepancy issue. However, before diving into investigation or troubleshooting, it's crucial to first confirm whether a discrepancy actually exists.
To confirm whether a discrepancy exists, you will need to check the following things.
Stitch will create the _sdc_primary_keys even if none of the tables in the integration have a Primary Key. Primary Key data will be added to the table when and if a table is replicated that has a defined Primary Key. This means it’s possible to have an empty _sdc_primary_keys table.
If you are not in all of above situations, please feel free to contact Support for further investigation or troubleshooting.
To follow the standard procedures for data discrepancy issues, please kindly provide the relevant information according to our document here:
data-discrepancy-troubleshooting-guide
The status of the Qlik NPrinting Engine consistently appears as Offline on the Engine Manager page.
The Qlik NPrinting Engine Logs read:
RabbitMq server is not connected - trying diagnoser queue creation again in 5 seconds
Qlik.NPrinting.Engine 24.4.14.0 Qlik.NPrinting.Engine.EngineService 20250521T190411.917+05:30
ERROR NBHI-DC-APP-69 RabbitMq service is not connected - trying again in 60 seconds.
ERROR: RabbitMQ.Client.Exceptions.BrokerUnreachableException: None of the specified endpoints were reachable
---> RabbitMQ.Client.Exceptions.OperationInterruptedException: The AMQP operation was interrupted:
AMQP close-reason, initiated by Peer, code=541, text='INTERNAL_ERROR - access to vhost '/' refused for user 'client_engine':
vhost '/' is down', classId=10, methodId=40
Additionally, the RabbitMQ logs may read:
EXTERNAL login refused: user 'client_engine' - invalid credentials
[info] closing AMQP connection ([::1]:60918 -> [::1]:5672)
[info] accepting AMQP connection ([::1]:60921 -> [::1]:5672)
[error] Error on AMQP connection ([::1]:60921 -> [::1]:5672, state: starting):
[error] EXTERNAL login refused: user 'client_engine' - invalid credentials
[info] closing AMQP connection ([::1]:60921 -> [::1]:5672)
For information about how to obtain log files, see How to collect the Qlik NPrinting Platform Log Files.
Initial checks:
If the issue persists, the RabbitMQ installation needs to be repaired. To do so effectively may require multiple rounds of reinstalling the Qlik NPrinting engine, as well as the RabbitMQ certificates to be recreated.
Our expected result is:
RabbitMQ repair:
All Qlik NPrinting services must be running for this procedure to work.
This cycle should be completed only twice at the most, but it is necessary to reestablish a connection between the Qlik NPrinting Engine and RabbitMQ.
If this fails to resolve the issue, log a support case with Qlik Support, including detailed information about all troubleshooting steps that have already been performed.
This indicates the RabbitMQ installation is corrupted or otherwise damaged. Multiple root causes exist:
Users previously assigned a Basic User entitlement have unexpectedly been promoted to Full User entitlement.
This is working as expected and will happen when a Basic User is granted any additional permissions. Source: Types of user entitlements.
An exception is the Collaboration Platform role, see Qlik Cloud Analytics: Assigning the Collaboration Platform User role to a Basic User does not promote it to full.
To determine what promotes a user to a Full User:
It is also possible to use the Access Evaluator App to have a more holistic overview over assignments.
To avoid users being promoted to Full Users, remove any assignment, both in single spaces and at a global level.
Verify the users are not assigned any roles other than than Has restricted view.
Be careful when using the Anyone group, since assigning any other role to this group will promote all users to Full.
This includes the default data space: Default_Data_Space created on tenant setup. Remove the Anyone member:
Turn off Auto assign for all Security roles in the Administration Center.
If a user was manually assigned a role, the role has to be removed again manually.
Is it faster to use a CSV file versus a Parquet file? Will one load to Qlik Cloud faster than the other?
The answer to this depends on the data.
The Analytics Engine makes calls to read data from the file as needed (streaming). While parquet files have built-in compression, which can affect how quickly certain data can be accessed, an equivalent CSV might be larger in raw data volume.
The following error occurred in Qlik Cloud Analytics:
Unexpected token: 'NONCLUSTERED', expected: 'Relationship' The engine error code: EDC_ERROR:11005 The error occurred here: CREATE >>>>>>NONCLUSTERED<<<<<< INDEX IX_WebProducts_ProductID ON #WebProducts(ProductID) !EXECUTE_NON_SELECT_QUERY
Add the following SQL statement to resolve the issue:
SQL CREATE NONCLUSTERED INDEX IX_YourIndexName1234 ON "test_db".SalesLT.Customer (LastName DESC) !EXECUTE_NON_SELECT_QUERY;
Some Qlik Cloud visualisations allow images to be shown from external URLs.
Is it possible to embed images that were uploaded to the media library?
We currently don't have a global repository for images in Qlik Cloud, but each app has its own media library, where images can be uploaded.
To link them:
Using a full URL to display the images (example: https://TENANT.REGION.qlikcloud.com/api/v1/apps/APPID/media/files/FILENAME.png) will work inside the app when authenticated on the tenant, but it will not work in other scenarios, such as mashups or the reporting service.
Make sure to use a relative URL (example: /api/v1/apps/APPID/media/files/FILENAME.png) instead.
For suggestions on how to improve the media library, please log an idea at Qlik Ideation.
The following release notes cover the Qlik PostgreSQL installer (QPI) version 1.2.0 to 2.0.0.
Content
Improvement / Defect | Details |
SHEND-2273 |
|
QCB-28706 |
Upgraded PostgreSQL version to 14.17 to address the pg_dump vulnerability (CVE-2024-7348). |
SUPPORT-335 | Upgraded PostgreSQL version to 14.17 to address the libcurl vulnerability (CVE-2024-7264). |
QB-24990 | Fixed an issue with upgrades of PostgreSQL if Qlik Sense was installed in a custom directory, such as D:\Sense. |
Improvement / Defect | Details |
SHEND-1359, QB-15164: Add support for encoding special characters for Postgres password in QPI | If the super user password is set to have certain special characters, QPI did not allow upgrading PostgreSQL using this password. The workaround was to set a different password, use QPI to upgrade the PostgreSQL database and then reset the password after the upgrade. This workaround is not required anymore with 1.4.0 QPI, as 1.4.0 supports encoded passwords. |
SHEND-1408: Qlik Sense services were not started again by QPI after the upgrade | QPI failed to restart Qlik services after upgrading the PostgreSQL database. This has been fixed now. |
SHEND-1511: Upgrade not working from 9.6 database | In QPI 1.3.0, upgrade from PostgreSQL 9.6 version to 14.8 was failing. This issue is fixed in QPI 1.4.0 version. |
QB-21082: Upgrade from May 23 Patch 3 to August 23 RC3 fails when QPI is used before attempting upgrade. QB-20581: May 2023 installer breaks QRS if QPI was used with a patch before. |
Using QPI on a patched Qlik Sense version caused issues in the earlier version. This is now supported. |
You can also click Copy link - this will show a warning that the bookmark needs to be published. When confirming the warning, the bookmark will be automatically published.
If the share option is not available or if users who should see the bookmarks cannot find it, verify that Sense has not been set up with Security Rules that disallow sharing or access to specific objects. See the attached document for details.
Loading MS Access data (.accdb file) using generic ODBC (via Data Gateway) in Data Manager fails with the following error:
Failed to add data
Data could not be added to Data manager. Please verify that all data sources connected to the app are working and try adding the data again.
The Direct Access ODBC Connector log reads:
Message=Error in HandleJsonRequest for method=getRawScript,
exception=Exception, error=ODBC Wrapper: Unable to execute SQLForeignKeys:
[Microsoft][ODBC Driver Manager] Driver does not support this function.
internalError=True
Use the Data Load Editor to load MS Access data.
Loading file-based Access DBs through ODBC to a modern BI tool is not recommended, specifically with larger files. These are likely to underperform during the loading process.
This error indicates the MS Access ODBC driver doesn’t support the SQLForeignKeys ODBC function. However, retrieving the table foreign keys is essential for Data Manager (as opposed to Data Load Editor).
SUPPORT-4446
A Talend Spark Stream Job configured with Yarn cluster mode and Kerberos enabled is encountering issues and failing to execute, presenting the following errors:
YarnClusterScheduler- Lost executor 3 on me-worker1.xxx.co.id: Unable to create executor due to Unable to register with external shuffle server due to : java.lang.IllegalStateException: Expected SaslMessage, received something else (maybe your client does not have SASL enabled?)
jaas.conf content =
Client {
com.sun.security.auth.module.Krb5LoginModule required
useKeyTab=true
keyTab="/tmp/adm.keytab"
principal="cld_adm@XXX.CO.ID"
doNotPrompt=true;
};
KafkaClient {
com.sun.security.auth.module.Krb5LoginModule required
useKeyTab=true
keyTab="/tmp/adm.keytab"
principal="cld_adm@XXX.CO.ID"
doNotPrompt=true;
};
The external shuffle service within YARN is configured to mandate SASL authentication; however, the Spark executor is either improperly configured to use SASL or is transmitting an incompatible message.
Common causes includes:
This error results in the executor's failure to register with the shuffle service, prompting the YarnClusterScheduler to mark it as lost.
Ensure that the external shuffle service is enabled, and that the SASL settings are in accordance with YARN's configurations:
spark.authenticate true
( #not necessary
spark.network.crypto.enabled true
spark.network.crypto.saslFallback true
)
The new Straight Table was moved into the new native section of charts from the visualization bundle. The new Straight Table offers many improvements from the old table, and we encourage everyone to start using the new table instead of the old one.
This article aims to answer any frequently asked questions around this switch, beginning with:
Here are some examples:
No, the old table will continue to work in the foreseeable future. Any changes will be notified in advance. Regardless, we highly recommend upgrading your tables as soon as possible to enjoy the new Straight Table's new functions.
The easiest way to convert your tables is to drop the new table chart onto the old one.
The new table looks different and offers more functionality that must be enabled to be used.
Not anytime soon, it will be a soft fade out. The new Straight Table will be the preferred choice for all new applications, and we anticipate many will upgrade to benefit from new functionality. Over time, the usage of the old table will diminish until most applications are using the new table anyway.
Qlik Sense Enterprise on Windows will have the table feature aligned with Qlik Cloud Analytics in a future release.
We’re closely monitoring feedback on the new table and are dedicated to creating the best possible experience, including improvements to accessibility. We are committed to accessible standards so people with disabilities can use our products. Printing, the tables should, of course, print in as consistent a manner as possible. As for usability. we aim to enable experienced users to reach functionality quickly, while also not overwhelming new users.
This article aims to help you facilitate the most effective way to collaborate with Qlik Support. It defines your responsibilities as a partner, including reproducing issues, performing basic troubleshooting, and consulting the knowledge base or official documentation.
For the Qlik Talend guide, see Partner Guide: How to Prepare and Collaborate with Qlik Talend Technical Support.
Before contacting Qlik Data Analytics Technical Support, partners must complete the steps outlined in Qlik Responsible Partner Duties and should review the OEM/MSP Support Policy to understand the scope of support and the expectations on Partners.
Content
Identify which Qlik product, environment, product configuration, or system layer is experiencing the issue.
For example, if a task fails in Qlik Sense Enterprise on Windows, try running it directly in Qlik Sense Management Console to determine whether the problem is transient. Also, try running a different task to determine whether the problem is task-specific.
Similarly, if a reload fails in one environment (e.g., Production), inform the customer to try running it in another (e.g., Test) to confirm whether the issue is environment-specific.
Always include the exact product name, version, and patch (or SR) the customer is using.
Many issues are version-specific, and Support cannot accurately investigate the issue without this information.
If the product the customer is using has reached End of life (EOL), please plan the upgrade. If the issue can be reproducible on the latest version, please reach out to us so that we can investigate and determine whether it's a defect or working as designed.
For End of Life or End of Support information, see Product Lifecycle.
Partners are expected to recreate the customer’s environment (matching versions, configurations, and other relevant details) and attempt to reproduce the issue.
If you do not already have a test environment, please ensure one is set up. Having your own environment is essential for reproducing issues and confirming whether the same behavior occurs outside of the customer’s setup.
In addition, please test whether the issue occurs in the latest supported product version. In some cases, it may also be helpful to test in a clean environment to rule out local configuration issues. If the issue does not occur in the newer version or a clean setup, it may have already been resolved, and you can propose an upgrade as a solution.
See the Release Note for the resolved issues.
Regardless of whether the issue could be reproduced, please include:
While pasting a portion of the log into the case comment can help highlight the main error, it is still required to attach the entire original log file (using, for example, FileCloud).
Support needs the full logs to understand the broader context and to confirm that the partial information is accurate and complete.
It is difficult to verify the root or provide reliable guidance without full logs.
Additionally:
Please do not simply forward or copy and paste the customer’s inquiry.
As a responsible partner, you are expected to perform an initial investigation. In your case submission, clearly describe:
Sharing this thought process:
Even if the issue remains unresolved, outlining what you already tried helps Support move forward faster and more effectively.
Attach all relevant files you received from the customer and personally reviewed during your investigation, as well as all relevant files you have used when reproducing the steps.
Providing both the customer’s files and your reproduction files allows Support to verify whether the same issue occurred under the same conditions, and to determine if the problem is reproducible, environment-specific, or isolated to the customer's configuration.
This includes (but is not limited to):
All support cases must be submitted using your official partner account, not the customer's account.
If you do not yet have a partner's account, contact Qlik Customer Support to request access and to receive the appropriate onboarding.
Review the support policy and set the case severity properly. See
Qlik Support Policy and SLAs
This template helps guide you on what to include and how to structure your case.
What happened? When did it happen? Where did it happen?
Clearly describe the event, including:
Only include what is needed based on the case type.
Examples:
List the files you have included in the case and what each one is.
Explain what investigation was done before contacting support.
Examples:
Thank you! We appreciate your cooperation in following these guidelines.
This ensures that your cases can be handled efficiently and escalated quickly when necessary.
Question
After moved migrated GitHub from on-premises to cloud and so switched from credential login to SSO, is there a way to authenticate Talend Studio to GitHub using SSO login? If using personal access tokens (PATs), is it on the security risk?
So far Talend Studio cannot SSO directly to GitHub, it can use a workaround with PATs or SSH keys, and thereby also be more secure than without SSO.
How a personal access token can be authorized for SSO
This link above explains how a personal access token can be authorized for SSO. So using a username and PAT from Studio to login to GitHub. GitHub allows granular permission controls for PATs and SSO authorization further mitigates security risks. Developers will need considerable rights.
How an ssh key can be authorized for SSO
You can do much the same with SSH keys
When attempting to connect to a GitHub repository from Talend Studio, encountered an error with the following message:
"git-upload-pack not permitted on 'https://github.com//.git'"
Common Symptoms:
Error:org.eclipse.jgit.api.errors.TransportException
Message:username or password are not correct
GitHub Desktop and Git Bash access may still work
Can successfully access other GitHub repositories
This issue is caused by a missing Single Sign-On (SSO) authorization on the GitHub Personal Access Token (PAT) being used.
When a GitHub organization enforces SAML SSO, all PATs must be explicitly authorized for use by the organization. If this step is skipped or the organization has changed its SSO enforcement, Git operations like git-upload-pack
will be denied — even if the PAT has the correct scopes.
To address the issue, please verify and reauthorize Single Sign-On (SSO) for your GitHub Personal Access Token (PAT) by following these step-by-step instructions:
Optional: Test via Git Bash
Run:
git clone https://user:PAT@github.com/<org>/<repo>.git
If SSO is not configured, you will receive a message:
Your organization has enabled or enforced SAML SSO...
Qlik Talend Cloud: 'git-receive-pack not permitted' error while creating a project
Using Qlik-CLI to export an app without the '--exportScope all' parameter fails with the error:
Error: 400 - Bad Request - Qlik Sense
This is observed after an upgrade to Qlik Sense Enterprise on Windows November 2024 patch 10 or any later version. The error is intermittent and the export may succeed if executed several times.
Reviewing the output shows Status: 201 Created, followed by the error after retrieving the app from the temporary download path:
> qlik qrs app export create "dbb1841d-f3f6-4a49-b73f-0a24cc003b1b" --exportScope all --output-file "C:/temp/App3.qvf" --insecure --verbose
Insecure flag set, server certificate will not be verified
POST https://sense/jwt/qrs/app/dbb1841d-f3f6-4a49-b73f-0a24cc003b1b/export/e237e6c8-d367-45d3-9eff-9f191b3f1ef5?exportScope=all&xrfKey=4B21426C21AE6B85...
Status: 201 Created
{
"exportToken": "e237e6c8-d367-45d3-9eff-9f191b3f1ef5",
"appId": "dbb1841d-f3f6-4a49-b73f-0a24cc003b1b",
"downloadPath": "/tempcontent/f8deec7c-5ab4-4462-879b-38990febbd1b/Test.qvf?serverNodeId=ae6a7f27-1abd-439e-b4da-0a0b0f4a3e61",...
}
GET https://sense/jwt/tempcontent/f8deec7c-5ab4-4462-879b-38990febbd1b/Test.qvf?serverNodeId=ae6a7f27-1abd-439e-b4da-0a0b0f4a3e61&xrfKey=4B21426C21AE6B85...
Status: 400 Bad Request
400 - Bad Request - Qlik Sense
Error: 400 - Bad Request - Qlik Sense
This is being investigated by Qlik as SUPPORT-3800.
Delete the content of the cookie store ( ~/.qlik/.cookiestore) when the error occurs.
In Windows, this can be found in %USERPROFILE%\.qlik\.cookiestore
A batch job can be created to automate the deletion.
This is caused by an incorrect cookie handling by Qlik-CLI. While exporting the app, the responses include the Set-Cookie header, but qlik-cli fails to update the cookie store with the new cookie.
When passing parameters from postman to a talend services, tRestRequest component is receiving null response.
Review the schema of the tRestRequest component to ensure the Comment field is appropriately assigned.
In REST API Mapping section, by default, if you leave the Comment field empty, the parameter is considered as a Path parameter.
There are some parameters missing/misconfiguring in the Comment field of tRestRequest component and you need to define what type of parameter it is in the Comment field of the schema.
Below is a list of supported Comment values:
empty or path corresponds to the default @PathParam,
query corresponds to @QueryParam,
form corresponds to @FormParam,
header corresponds to @HeaderParam.
matrix corresponds to @MatrixParam.
multipart corresponds to the CXF specific @Multipart, representing the request body. It can be used only with POST and PUT HTTP methods.
https://help.qlik.com/talend/en-US/components/8.0/esb-rest/trestrequest