In Yellowfin 8 we introduced two new products, Yellowfin Signals, to automatically discover the most critical changes in your business as they happen, and Yellowfin Stories, to provide context to the numbers and tell compelling stories with your data. We’ve received great feedback since then and implemented some of the requested enhancements to improve the user experience, increase governance and performance.
How do you organize an effective meeting when you don’t have a physical space to hold it? How do you manage workflows across different time zones, when some people are starting work as others go to bed? How do you integrate new people into the culture when you don’t have a physical HR department?
In my last post, I gave you the first six Do’s and Don’ts of Data Governance and promised to bring together an additional six to consider when making a data governance plan for your organization. Here are six more dos and don'ts when building your data governance framework.
In addition to tracking your email marketing & automation KPIs from Klaviyo, you can also pull data from all of the tools that Klaviyo integrates with right into Databox, too.
This post is the last in a three-part series about deploying Kong as a service mesh. The first post discussed how we define the term “service mesh” here at Kong, and the second post explained the architectural pattern used to deploy Kong as a mesh. In this post, we will talk about the new features and configuration options we added to give Kong its mesh capabilities.
A few years ago, Qlik ran a campaign called the Whole Story. The related video is still posted (fun fact: It was filmed in Qlik’s office near San Francisco). Our message was that you don’t know the whole story in your data if you a.) aren’t able to look at all the data while b.) understanding all the relationships between data.
