Passing variables to applications via the QlikView QMC with Script Parameters and Publisher

Following this post which talks about methods for configuring apps, this post looks at how to achieve this via the QMC in QlikView and set variables in reloaded QVWs.

You’ll need to have Publisher enabled to access the features used for this example.

In a QlikView deployment with Publisher you’ll have access to the Reload tab for a task. This includes the option to add Script Parameters, which essentially leads to duplicate apps based on the provided field or variable name.

However – provide just one variable value, and you’ll pass this into one copy of the app.

Continue reading “Passing variables to applications via the QlikView QMC with Script Parameters and Publisher”

Integrating QlikView into SalesForce SFDC with SSO – forcing TLS1.1 or higher

Integrating some QlikView screens into Salesforce, and using Salesforce to authenticate your users is actually very simple. Joe Bickley from Qlik wrote about setting up Salesforce SSO back in 2012 – and I thought I’d have a go.

The only road block encountered along the way was Salesforce’s decision to disable TLS 1.0. They have a number of very good reasons, including the famous Poodle vulnerability. It meant I experienced the error below:

UNSUPPORTED_CLIENT: TLS 1.0 has been disabled in this organization. Please use TLS 1.1 or higher when connecting to Salesforce using https.

on

AppExchangeAPI.GetUserInfoResult userInfoResult = binding.getUserInfo();

This isn’t yet a mandatory change for production organisations, but it will be by 22/07/2017. Any development organisation will have it enabled by default, without any method for disabling. Other services do not have a disable date at the time of writing this post.

Uh oh, things aren’t well with SFDCLogin.aspx

Continue reading “Integrating QlikView into SalesForce SFDC with SSO – forcing TLS1.1 or higher”