Systems | Development | Analytics | API | Testing

%term

Part 4: How machine learning, AI and automation could break the BI adoption barrier

In the last three parts of this four-part series, we have looked at: research on the state of analytics today and the lack of BI adoption; the history of BI and how we have arrived at the augmented era; and the four main blockers to BI adoption that is stunting the growth your business data culture. Today, let's take a look at how AI and machine learning (ML) can close that adoption gap.

The Qlik Sense April 2019 Release

April is an exciting time at Qlik as we build momentum towards Qonnections 2019 and later in the quarter, the global Qlik Analytics Tour. These great events will showcase Qlik Sense April 2019 – which is now available! This release sets us apart from the competition with significant advancements to our multi-cloud capabilities – including a new enterprise SaaS deployment option, as well as innovative advancements to our market leading AI capabilities.

Delivering Connected Customer Experiences with APIs

Today’s connected experiences — such as controlling smart home accessories from a mobile app or ordering takeout via a voice assistant — involve a lot of software talking to other software. This means these digital experiences rely in large part on application programming interfaces (APIs). When someone uses their social media account to log into other websites, an API mediates the interaction.

Qlik Associative Insights - Simple Yet Practical Example

See the power behind our new Associative Insights capability available with Qlik Sense April 2019. The Associative Engine identifies the data values that are unrelated to your selections, and the Cognitive Engine analyzes the unrelated values and brings the most significant insights forward possibly revealing new discoveries and prompting new questions. I’m going to show you a very simple example to prove to you how powerful this is.

Time-Tested Insights on Creating Competitive API Programs

When the Application Program Interface (API) first came into existence, developers viewed it as a revolutionary approach to creating re-usable software fragments. Instead of creating new code from scratch for every new program, they could now use existing functionality to develop new features. Not only did this decrease the amount of time needed to deploy a program but also meant they could leverage existing code which was already tried and tested.