Information Discovery. Governance with a business twist - Inspire 2017

You won't want to miss this session! Hear how Alteryx thinks about governance through innovative ways to empower users to find, understand and collaborate on all information assets relevant to their business questions. Attend this session to find out how analytic teams can best enable users with trusted information and how users in an organization can see their work discovered and utilized by their peers.

Video Transcription

JC Raveneau:
Okay let's get started. Hi everyone. So this session is going to be about Alteryx Connect, which we did this morning and the day before. We're talking a lot about it. My name is JC Raveneau, and have a partner in crime here, Dan. I'm the product manager for the product, but Dan is much better at demoing the product, so you get a real demo this time.

So I'm going to talk a little bit about- let's see the agenda- I'm going to talk a little bit about why we started Alteryx Connect, and what this is all about. Then we'll go into demo mode with our friend Dan here, and then I'll go through two more slides after demo to give you a little bit more insight into what's next, when the product's coming, all that stuff that you guys are anxious to learn about, right?

So let's get started right away. Why Alteryx Connect? Why did we decide to start this product? So last year I actually spent most of my year investigating the space and understanding what we needed to do next at Alteryx as far as product portfolio is concerned. And there was this idea that maybe we needed to do more into the area of data governance or data management.

And so I started to work with analysts and markets and also interviewing a lot of our customers, and I consistently got the same feedback. And this feedback is summarized on this slide, right? On the left hand side for you guys, what I've consistently heard is that people, customers, were trying to implement classic data governance or data management systems, and it was not really differing the value. And the reason for that is it's super hard to maintain and they were not seeing the engagement of the business users. So that was one complication.

However, on the flip side, folks were telling me, hey we have a real data discover challenge. We have data everywhere and people are not finding it, and I need help. I need people to be able to find the data, and I need to understand how people are using the data.

And the third bullet that I wanted to highlight here is this Tom, you know, it's a big retailer in Europe, and he actually highlighted the concept of crowd sourcing for meta data. He was telling me, hey JC this is good. I have a lot of tools to go out to my systems and load all the technical meta data that is out there, but guess what? The important information is not in the systems. It's in the people's heads, right? In the analysts that are working for me. They know they relationship between the data and the business. Which no system has been able to capture so far.

So very important concept of crowd sourcing the meta data here. So I started from those kind of, you know, interviews and customer descriptions and market descriptions, and then was like okay, I'm a product manager. I need to start from the use case. And when you want to start any product, you need to be very focused on the use case you're going to start tackling because you want to have a good product to address the use case. You don't want to have a product that does it all that can kind of half delivers on many different use cases.

So we decided to focus on the use case of what I call Data Discovery. And this is Annie, this is our business persona. She has a business question. She needs to analyze customer churn, but where do I start? Kind of the same stuff I was talking about this morning. And she has a lot of data assets around her.

On the left hand side, those are more like tables and columns and kind of raw sources of data. And on the right hand side you're finding Alteryx workflows, you're finding you know, Tableau workbooks, Power BI dashboards maybe. So stuff that is also already there, so if I have business questions, and there's already something there in the form of Tableau Alteryx that I can use, why not do that? Why go back to the table?

And the right hand size kind of [inaudible 00:04:49] describe pretty much what the situation is right now. Users are spending too much time finding the data. So, specifically, I heard this feedback consistently from Alteryx users. They're like, yeah you did great. I have this tool, this collapsing timeline that Jay was doing this morning. Yeah it works very well but now I'm spending 80% of my time not preparing the data. I'm spending 80% of my time finding the data, so can you help with this part of it as well?

When you finally get to produce something, whether you are an Alteryx developer or maybe a BI workbook developer, how do you promote your work? And this was also feedback I was getting from the customers is, I produced this thing. If it's a Tableau report or workbook, I publish to the Tableau server. If it's an Alteryx workflow I publish to the Alteryx gallery. If it's an Excel spreadsheet I put on a shared drive, and so on and so forth. And now there isn't one place where I can put my work and say, hey this is a great asset that I just produced. People should be using it, but how do I tell people? They should be using it.

So that's the one problem. Tribal knowledge. We talked a little bit about it in the previous slide. It's how do I capture the knowledge that is in people's heads? I see this constantly. I actually see it in Alteryx number 2 next to one other guy who is in our own analyst team, right. He does use Alteryx to do sales analysis for Alteryx, right. And he picks up the phone to ask people around about access to this table, or did you ever build a macro that does this thing or that thing? Because he doesn't have a central place to go and grab this information.

And the last bullet here which is actually a consequence of the first bullets, is people aren't just proliferating assets. Because if I cannot find something, but if I have great tools, like Alteryx is easy now that I might as well start from scratch, rather than starting to call 7 different people to find out where is the information. So you know, I'll start from scratch. And guess what? By doing this, I make the problem even worse, because now I have multiple version of the same asset. I've been wasting a lot of time redoing the stuff that someone else already did in some other place of the organization.

So this is my use case, and this is a use case we want to solve. But let me talk a little bit about data governance. Because this is, when I started on this project as I was saying a year ago or something, talking to the market- The market was all about data governance. You guys need to do data governance, blah blah blah. All the data governance stuff. And I looked in detail at the data governance platforms. I actually have good friends at Informatica, IBM is down the street, plus talking to analysts. And governance, the way it exists right now, is very much focused on compliance, policies, roles, approvals, security, and whatnot.

It's great. It is there. It is there to stay because we need compliance with some regulation, specifically if some of you guys work in government, healthcare, banking, finance, anything like that needs to be regulated. So governance is here, but are we actually gonna rebuild Informatica governance or IBM governance and pretend to replace those guys? That doesn't make sense.

However, Alteryx is all about the business users and enabling the business to achieve business results faster. So this is why, what we see as the evolution of data governance into something that we call Dynamic Data Management. Dynamic Data Management is about having a data catalog that is focused on business results, not focused on compliance, but focused on business results to enable the users to achieve more with the data. And how we do that- We think that instead of having this centralized entity right there that has to do the curation of all the data assets in one place with all these concepts of owners and stewards, and whatnot. It's very centralized. It's great, and it still exists. And it will still exist but it doesn't scale.

It doesn't scale because all of you guys producing 2,3,4, 10 Alteryx workflows per week. It cannot go through this whole process of these guys approving and then putting the catalog and commanding that stuff. And by this time, the business opportunity is gone. So the idea is we keep the good things from data governance, like glossary, metadata management, the lineage, the certification permissions, all that stuff. But we look at it from a business value standpoint, not from a compliant standpoint.

So this is our focus for this product. And I think it's important to kind of keep in mind as you think about the evolution of the product throughout our map, it's going to be very much focused on providing the business users with the capability to best leverage data. Langley was talking this morning about the focus on the [inaudible 00:10:41] We are talking to here. Enable the business with data.

So introducing Alteryx Connect, which has been [inaudible 00:10:55] Right now. I didn't know our session would be at the very end. So still introducing Alteryx Connect V1. So what this is. This slide you haven't seen. So this is my kind of high level pictures of Alteryx Connect. It's a collaborative data exploration platform. So that's important because I'm not saying Alteryx Connect is a data catalog. I'm not saying Alteryx Connect is a governance platform. I'm not saying Alteryx Connect is, you know, a place where you have metadata.

I'm first focusing on the collaboration. So giving a place for people to get to this tribal knowledge that we're talking about. And enabling people to discover the stuff that they need. Cause this is more important for you guys to be able to achieve your business results to find what you need, right? This vision here is that it should be a single point of entry. So when I have a question, you see my business user Annie in the first slide? She has a question. She goes there first, because she doesn't know.

She'll go there first, and she's going to find there, everything that she needs. So if there is some Alteryx workflow already there, she's gonna find it. IF there's a table she's gonna find it. If this is a business glossary entry, she's gonna find it as well. So she goes there first, and there she searches and she can understand, oh yes this thing exists. And she can understand how am I gonna be using this thing that already exists. And how I can collaborate with others, maybe to make it better or just ask questions, because I don't know what it's about.

So this is the focus we're gonna have, at least for the foreseeable future on what this platform needs to look like. I'm not gonna go through the details of this slide because I have more slides on this later. But those are the four, I'm sorry three. It was four before so I keep saying four, but I decided to collapse. Those are the three main components that we have in the platform and that we will be keeping on iterating on.

The top on is our Asset Catalog and Glossary, because you need to start somewhere. So you need to start with having in one place all the metadata that you need, and two types of metadata in the platform. One is what we call the technical metadata. This is the data that we get from the systems, and the glossary, which is more like the business definitions of terms and KPI's. I'll go back to it to explain how it works and all that stuff in the next slide.

Information Discovery. I was talking about that earlier. Information Discovery now is, I have my catalog. I have stuff in there. How do I access it? How do I find what is relevant to me? So, again, I'm going into more detail in the subsequent slides. And the last bullet here is around the Enrichment and the Collaboration.

So now I have mostly technical metadata in my platform. I can search for it, but how do I make this better and more relevant to the business? How do I capture this tribal knowledge that we're talking about by providing an environment that engages users to collaborate and enhance the existing content by this kind of business intelligence that they have in their heads?

Let's look a little bit into the details of that. Whoops, I clicked too fast. All right. So the first thing that the platform does, it's going to catalog your assets. How we do this, if I can get it up on the screen. On the left hand side over there, you have your source systems. I call them source systems. Source systems can be so those are the source systems we support right now. I think I didn't forget any one of them.

And that are going to be supported in V1. Maybe there will be more than that, but at least those guys are going to be supported in V1. So you have Analytic Gallery, which is the Alteryx workflows. You have [inaudible 00:15:25] You have Phi Systems or I call [inaudible 00:15:28] Force and XSO. We are going to deliver to you guys a set of workflows. We're using our own tool, isn't it great? We're using our own tool that we call the metadata loaders. The metadata loaders are nothing but Alteryx workflows that are going to go ahead and grab metadata from the source systems, take this metadata, process it into workflows. There's no black box. If you guys want to open the workflow you can see what's going on there and load the metadata catalog in the Alteryx Connect Platform.

Take metadata out, process it, load it into the platform. That's what those metadata loaders do. Obviously, we're going to be adding to those loaders. The platform, the way I like to abstract it, is a metadata catalog. A glossary, that we talked about. This is where you have your definition, business KPI's, stuff like that. And people. People are very important. We're talking about a social platform so people are very important.

And what we're doing is processing all this information to create relationships with things. So we harvest things from the different systems, and whenever we can find relationships like this Alteryx workflow is using this connection, and this connection has also been harvested, then I an establish "hey this Alteryx workflow totally uses this table". And then I can start to think about, hey I can start establishing lineage between the different things.

So it creates relationships between all those entities in the platform, and there is an indexing going on, so we can have the discovery thing going on. On the right hand side here, this is my user input. So all left hand side is automatic, goes through the platform, then these collaborative environments users use it, and they start editing stuff to enrich the content. Or they maybe start editing stuff to have discussions about the content, and so on and so forth. This is what happens in the platform.

So this is how you end up with the asset catalog in the middle. And this is something that is constantly evolving, right? You're never done with it, because as we were saying, there are new assets being created every day, and so what you want to do is you want to schedule the metadata loaders so they keep refreshing the assets. And you want to keep users active on the platform. So maybe you start with a few users that are more [inaudible 00:18:22] That are starting to edit stuff, but our goal and your goal as well, should be to have this community of users that want to contribute to it. Like a community. So we'll be adding stuff in the platform to help with this, but that's very important.

The second step is Discover and Understand. So what you will find in the version 1 first of all, is a search. A search, the way we think about it, is a primary interaction with the platform. We don't expect users to be browsing across dozens and dozens of assets. We expect users to be searching first. It's a boosted search, so the search is tuned to present certain assets first. For example an Alteryx workflow that matches the search is gonna come first before a table, for example. Because, hey if there is an Alteryx workflow that exists and answers my question, then I might as well use this instead of starting from scratch.

There is also this concept of social thumbs up and down in the platform, so that's going to influence as well. Something we do not see here in the screenshots because it's not there yet, it will be in version one, is also the concept of certification of an asset. So search is our first point of entry. Glossary is interesting, because I'm not sure that a lot of you guys are using glossary, but glossary is a very good entry point. If you want to resolve a business question, you might as well search for business terms, and the glossary, because of the lineage and relationships, the glossary can actually help you find the technical asset that corresponds to your business term that you search.

What I did this morning, is I entered the system through the glossary, and with relationship, I navigated down to table it was referenced in the glossary. So that's a very good way to find what you need as well. Rich content, descriptions, annotations, tags. Everything is there in the platform. The description here is a very rich text, so it's not just- We like to put one line because we're lazy. But what you see here is that you have links in the description itself. It means you can reference an existing asset in the platform in the description of another asset. And the platform is going to create the link between those two things. So cross reference those two things.

A description can be very rich. You can have long text, you can have full, you can have Wiki page almost in the description, so you can really document your asset as much as you want. Relationships is something that everyone gets excited about. Whenever I say lineage everyone cheers about lineage. That's great. So this is lineage. This is a good example of it. So in the middle we have the Alteryx workflow because this is what I searched for. And on the left hand size, this is what you'll see in the demos as well. You have the inputs to your Alteryx workflows. In this case, we have a table and there are two Alteryx [inaudible 00:21:49]

And on the right hand side you have to output. Which in this case was [inaudible 00:21:56] a Tableau data extract. So on each and every asset, you're going to find lineage. If you have a Tableau workbook, you're going to find lineage back to where it started and so on ad so forth. And I saw a very nice demo of the latest development field this morning and it's getting there, so I'm pretty excited about it.

All right so now we discovered and understood our assets. It's time to interact and collaborate, because as I was telling you guys, this was our intention to have a platform that is very social and where people can interact with each other, which is very much missing right now. So who is involved? So who has been touching that asset? Who is the owner, if we can find one? Who has been contributing, so on each on every asset you find, who is involved with this asset?

Our goal is to have on each and every asset, always, the contact that you can ask a question to. So if you're stuck, there is an owner, there are some contributors. Pick someone, and ask a question. That's as easy as is, right? Ask a question, ask an answer. This is the conversation pane, so it's a chat. You can get there. It's what I did this morning with my friend Dan here. Ask a question, request access, whatever. You have this discussion pane here that is your point of contact with all the people. You can also assign tasks to people through the discussion panes, which you know I maybe, then you want to show that later. But if you actually point this thing to someone, it's going to create a task for them. So you can start having some kind of workflow in there, where hey Dan, this table is not very good. There is no good description. I assign a task to you to update the description because I have no idea.

Take some actions. You'll find at the right hand size of the screen at the top, some actions editing the assets. We have three categories of users in there. Administrators, we have contributors, and we have readers. By default, everyone is a contributor, so everyone can edit and enrich what is there. Vote stuff up and down. Usually people are a little bit scared voting things down, so you have usually this kind of situation where people vote things up and there's zero vote down. But you know, I like voting things down when they deserve it.

Commenting gets you to ask an answer and sharing the asset is very interesting. Because if you find something useful you can click on share and send that stuff to someone else. It doesn't send the stuff, it sends the link to stuff, so we always have a single version of the truth.

So the last thing here is tracking the activity. Dan is gonna show us, this is our feed. The idea is lots of stuff happened on the assets, and it's good if you see that. Hey there's activity here. It kind of prompts your attention. Someone has been doing something. Someone that you know maybe has been using this thing. SO it might be interesting, and you might be incline to click on it and discover something you didn't know about before because you don't know what you don't know.

So that's the tracked activity. Something that is not mentioned here. There is versioning on those things. So if you start changing things, it's all tracked, and there is a versioning. You can have full trust ability on what was done on the asset. You can even compare the different versions of an asset. You can restore a version of an asset that has been overwritten and so on and so forth. So everything is tracked which is going to make our governance people happy.

Demo time. Dan.

Dan Hilton:
All right. Thanks JC.

Crowd question:
Quick question.

JC Raveneau:

Crowd question:
[inaudible 00:26:13]

JC Raveneau:
I'll get to this yeah. Question is about the server. I'll get to this right after the demo. Yep.

Dan Hilton:

JC Raveneau:
You need to flip the screen again.

Dan Hilton:
Ah. Yep. All right. So as JC said, the platform is really focusing on enabling data analysts and data workers. So as an analyst I come to the platform, I see a home page that looks like this. We see a couple different pieces. The main panel here shows high level asset categories including Alteryx workflows, Tableau reports and soon to be some other reporting types, glossary definitions, and data sources which include files and relational database objects. And then also a list of users. We also see browsing history for my own user, so things I've done in the past. And we see recent activity on the system overall across all users.

And then, as JC noted, the main way that we would start to solve a business problem is with the search. So as an analyst, I've been tasked with answering a problem. I'm trying to predict customer churn for our customers, and I suspect that someone in my organization has probably tried to solve this problem. But I don't really know who or what they produced or what data sources they may have used to produce such a thing.

So I'm just going to look across a variety of different assets that were harvested from my enterprise. I look for customer churn. I notice a variety of different assets including some Tableau workbooks and a definition from the glossary, and an Alteryx workflow. And the ranking of these search results is kind of influenced by the refinement of the data asset. SO we're kind of favoring more refined sources like reporting and Alteryx workflows, over more raw data assets. And it's also influenced by the social ranking. SO things that are ranked higher will tend to bubble to the top a little bit more.

So in this case I notice that this Alteryx workflow is relatively highly rated, so I'm gonna dig into this a little bit to try to understand what the data sources are and what the situation is with this data asset. When we click on the data asset page, we see kind of a high level description, we see some details about where the workflow was harvested from. So this came from a particular gallery studio. And then we see our relationship. So lineage, the data that feeds the workflow, the data that's produced by the workflow, and we see that same kind of lineage tracking below in list form.

And then we also see that activity for this data asset. SO if it's changed over time. If there's been some kind of changes in it's attributes we can see that as well. So here as an analyst, we can see that it's producing a couple of KPI's, and we want to make sure that they're in line with the KPI's that we care about. That it's the exact same definition. So we can link to the glossary definition and confirm that the definition is exactly what we want to use.

We note on the definition that there are relationships here as well. So all of the different types of data objects in the system can be referenced to one another. So people can be referenced to glossary terms, glossary terms can be referenced to data objects and so forth. SO this glossary term is actually used it looks like in a couple different places, including in our original report that we're evaluating.

So we'll go back to that Alteryx workflow. We're happy now that the attrition KPI is the KPI that we care about and that we want to continue with. We look at the relationships. So notice we have a couple different inputs, a couple files in a SQL database table. And as an analyst, we've used this table in the past a little bit, and it used to be problematic. I remember that it had some sourcing problems a while back and I'm a little bit skeptical of it. So I'm going to click on the database table and dig into this a little bit further. So I see all the columns, I see where it's derived from.

I also see that the owner is Derek. I've worked with him a little bit in the past, and I trust his opinion. I'm going to ask him if some of the sourcing problems have been sorted out. So we can ask something of Derek like, is this table contain order details for the last 24 months, and are there any gaps? And he can respond. He'll be notified via email, and he'll also have this little indicator in the top right that he's been pinged by someone. That he has a question outstanding. So he notices that and responds that yes, the sourcing problems have been worked out and so we're kind of happy to continue on our journey.

So, going back to the workflow. We've kind of done a little bit of validation. We've discovered the assets that are related to what we want to do, and we're happy that we can now start with this Alteryx workflow that's been produced and actually take that and tack some additional data pieces onto it. So we can launch and fire up the Alteryx gallery that this was derived from. This isn't actually on our network so I can't hit it at the moment but any of the platforms that have a web based URL that represents it will link back out, so a Tableau server will be able to bounce you there or to the gallery.

So the value really here is that, as an analyst, I started not knowing much. I knew I had a problem, but I didn't know where to start, what data was in play, or what reports were in play, and I pretty quickly understood what's available to me and how I can kind of be a lot more efficient. Not spend a lot of time just searching and asking people where to start.

JC Raveneau:
Thank you.

Dan Hilton:
Thank you.

JC Raveneau:
Thank you Dan. So I'm going to- Question?

Crowd question:
[inaudible 00:33:37]

Dan Hilton:
So you're asking the TDE itself, like the file itself? How to doc it into the system?

Crowd question:
The relationship diagram. The lineage. How did that TD information come in? Like what TD is feeding that workflow it's feeding to.

Dan Hilton:
Right. So-

Crowd question:
Did anyone manually create this lineage or?

Dan Hilton:
Like how did we create the lineage. Yeah so, the Alteryx workflows reside on the gallery. And we have a series of these metadata harvesting workflows, and one of those is workflows from the gallery. And when we execute this workflow, it calls the gallery API, pulls down all of the workflows, and then we parse out the inputs and outputs from the workflow CML, and we ship those off to the connect server as the inputs and outputs as metadata. So we know what the workflow inputs and outputs are, then we harvest from these other sources as well. We have one from the SQL server, one for Oracle, one for files on File System. And we join those two together to see, this Alteryx workflow is using this SQL table, or this TDE. Here's also a definition of the TDE table itself or the SQL table itself. Make that join, and that's how we track lineage.

Crowd question:
Make that join manually or is there...

Dan Hilton:
No no. The system's doing the joining automatically.

JC Raveneau:
So I want to make sure I have a couple minutes to work you guys through two more slides. One is about what's next. A few words, so this is very few words right? Kind of four words on this page. So availability. The thing is planned to be released in Q3 this year. In version 1. Q3 this year. Packaging- This is packaged as an add on the Alteryx server. So you have to license Alteryx server. However, when you license Alteryx server, you get this with it for the same price. The great same price. That's great.

Setup and Deployment. That was your question earlier. Those are two different systems. You can install them on the same server. We will have an installer that installs both products on the server. Then there will be an option to manually split those things into two different things. So I would say the minimum requirement or recommendation is you know, minimum configuration is everything on the same server, but the recommended configuration depending on your workload and number of users, you're going to want to split the thing out in a separate server.

So that's what the setup and deployment is about.

Crowd question:
[inaudible 00:36:54]

JC Raveneau:
Great question. So if you install it on another server, for example you want two additional CPU's to split Alteryx Connect, then you will need to license two additional CPU's. That make sense? Okay.

Last slide about the product directions. So this is kind of high level directions right? We're not giving detailed roadmaps. We are going to focus on these three points. One is going to be the Portfolio Integration with the rest of the Alteryx things. So think about the interaction with the server and the gallery, which we can always make better. Then kind of tried to show the launch button that takes you to gallery, but we can do more. For example, integrate the gallery versions into Connect, right?

Integration was designed here as well. What I showed this morning was actually not in the product yet. But it's something that's on the roadmap. And so on and so forth. Yeah the Alteryx server is also something on the roadmap in the portfolio integration.

Enriching the data catalog. Obviously we are always going to add more connectors, loaders, to this platform so we can address more of your platforms and as we release these, we'll be seeking your feedback in terms of what we need to do next. Our current plan right now is to start addressing all the Alteryx connectors in the order of which they are used. So we collect information and data about what you guys are using in your Alteryx workflows, and this is our matching order in terms of adding connection to this platform.

Something that is also in there that we'd be very focused on is, how do we present the information to the users in a way that is- we're targeting business user and analysts right? Not IT people. So in a way that is meaningful to them, without overloading people with information. So we'll be working quite a bit on the user experience to make sure we've got this right. And there were, during this Inspire, there were UX sessions going on in this product downstairs. I don't know if any of you guys participated, but this is what we're researching. It's how do we create a seamless experience that gives the information without overwhelming the user with details.

And the last piece of it, which is last but not least, it's very important to me, is focusing on the discovery and social experience. So it's great to have all this technical data in there with the automatic loaders and lineage, but let's be frank. If this is only technical information, technical metadata, it's going to be relatively hard for business people to use it. So we want this to be very collaborative. We want people to be engaged with it, and same stuff. We will be focusing very much on the experience for discovering things, and we'll be focusing very much on the experience on how we manage to engage people, so they actually contribute and collaborate on the platform instead of picking up the phone or sending emails. And so on and so forth. So these are your high level product directions.


And yeah, please while we're going through questions if you have a little bit of time.

Crowd question:
First off, great job. I'm really excited about it. Off your demo this morning, just one question, cause the question that you input into the text box for Q and A. You were asking about the refresh cycle. Couldn't you just actually create that and imbed that as part of the metadata so you know from that data source or from that data asset, what the refresh cycle would be? Cause then ultimately, you have to harvest that information that conversation, and that's going to be in the text box as opposed to being in the actual platform itself.

JC Raveneau:
That's good idea. Yeah. Obviously was kind of for show when I picked this example, but yeah that's a good idea. Yeah.

Crowd question:
What are your plans to integrate with other metadata tools? Like we have Corribra, in organization. We also have IBM, IGC. We have a lot of metadata sites, but they don't have the social experience you're talking about here. So do you have anything in the roadmap to bring in those tools into Alteryx Connect?

JC Raveneau:
The answer is yes. I don't know exactly when, but the answer is yes. We've been actually asked already by other vendors if we could integrate their metadata into the platform. So this is something we're looking at, yes.

Crowd question:
And the other thing is, maybe it's already there, but does the platform also provide a catalog of different SQL's you're running. And help us rationalize those SQL's. Is that a feature today?

JC Raveneau:
So not a feature right now. You could always have your SQL as a text in there. We obviously focus first on the Alteryx user base so not SQL. So maybe down the road I'll be thinking about that but I'm focusing first on the Alteryx users.

Crowd question:
Sounds good. Thanks.

JC Raveneau:
Thank you.

Dan Hilton:
There's one over there.

Crowd question:
So you're predominantly at this point doing metadata extraction and things like that in order to populate this information? In our use case where I am right now, we're leveraging a lot of contextual information about where workflow is executed to determine things lik output locations and what aliases mean. So depending on where a workflow gets executed, our alias could point to a different server, or our output could end up being renamed or have a different end location. Is there any plan that you have to address those sort of dynamic output input location situations?

JC Raveneau:
So you're talking about the alias in the Alteryx context?

Crowd question:
So yeah, specifically there, I'm using aliases and they're pointing to different servers dependent on where it's being run, what user is running something. It's pointing to a different piece of the data set.

JC Raveneau:
Yeah. So I think that we need maybe discuss more about this specific case, but as far as using the alias and the connection definition in general, we are thinking about integrating this with Connection Manager. Which is a new version of the alias. Which should probably give you a little bit of what you're looking for, but let's discuss after in more details.

Crowd question:

Crowd question:
I think we have time for maybe like one last question. If there is. Maybe not.

JC Raveneau:
Out of questions. Right on time.

Crowd question:
Thank you.

JC Raveneau:
Thank you everyone. Thanks.



Los Gehts