Unlock the Power of Workfront Data Connect

Transcript

Hey everyone, good morning, good afternoon. We will get started here in just a second, letting everyone join in from the lobby, so just bear with us, like I said, for about 30 seconds before we get going. So feel free to say hi, introduce yourself in the chat, everyone should have access to the chat pod, let us know who you are, what organization you’re coming from, maybe what city, state, maybe from a user group perspective, so yeah, feel free to say hi in the chat, and we’ll get started here momentarily.

All right, let’s go ahead and get started. I imagine there’ll be a handful of questions, for our presenter here on today’s call, so if you guys just happen to stumble into today’s workshop, welcome to today’s session focused on Data Connect in Adobe Workfront, and so just from an agenda standpoint, we’ll go through some quick introductions, an introduction to Data Connect, and then I’ll hand it off to, or I’ll hand it off after really the introductions, to our product leader Matt Mitchell here to kind of walk you guys through the different capabilities of Data Connect, a little bit about the roadmap, and then we will make sure to leave some time at the end for some Q&A, and so just from a housekeeping perspective, this session is going to be recorded, so you don’t have to worry about screenshotting anything on the screen, you will get a copy of the slide deck and a link to the recording afterwards, so keep an eye out for a follow-up email. I always try and get it out within a few hours of the session ending, so it’ll come from our csatscale at adobe.com inbox, which is just customersuccessatscale at adobe.com. You guys will have access to a few different sort of areas. You have the chat pod, which is really for you asking questions to your peers here on the call. If you have questions for Matt that you would like to get answered live at the Q&A, you know, while we wrap up in the Q&A at the end of the session, we will be asking your peers for some questions, recommendations, best practices. The Q&A pod is for asking our presenter questions for the follow-up as soon as we’re done with the slide deck. I think that’s all I have from a housekeeping perspective, so I will hand it off to Matt here to introduce himself and go through more about Data Connect.

Perfect, thank you. I’m really excited to be here. I’m excited to share some of the content that we prepared for you and even some of the lessons learned that we’ve had since we’ve launched the Data Connect product. I also need to learn from you. I think that’s a reasonable ask. I just posted a survey to the chat, so this is less more of the introduction, where are you from, what organization are you from, but it’s to help me collect some information around how you rely on business visualization. If you can do that and in exchange, I’ll try to do a good presentation for you today. You’ve had a chance to read my bio. If we haven’t met before, I look forward to answering the questions that you have. I’ve been around the Workfront At-Task application for quite some time, and I think they tapped me on the shoulder for all the reporting and data analytics because I literally wrote the instruction book on how to do a lot of the reporting stuff. I’m happy to bring that experience into the conversation as well. Let’s get into it.

You are probably in one of two camps. You’ve heard of Data Connect, you know what it is, and you have some specific questions that you would like answered. Nicole shared with me some of the questions that were submitted as part of the registration for this webinar, and I think we’ll probably through the content address most of those. If not, we’ll do it during the question and answer session. But then also, some of you might be at the camp of, I have no idea what this is, and maybe need a 10,000-foot view of what Data Connect is. Let me just describe it in a quick sentence. Data Connect is our prescribed way to pull data out of Workfront into your business visualization services to answer questions and provide visibility to drive business decisions. I had an interesting call earlier this morning with a customer, and the response was, this is so cool, and I asked if I could quote them on it. They said, yes. There you go. We have a customer who didn’t know they had this, who had been investing quite a lot of time trying to pull the data out in other ways. They are so excited to be able to use this in a meaningful way to drive better, more insightful action inside of their organization.

So, but really, what is it? We always have those kind of marquee slides in these things, but let’s get into the nuts and bolts of it. Data Connect provides a secure and scalable way for us to provide those business insights to you, to deliver reliable data access in seconds.

It is designed to be a simplified experience that any of you that are currently using business intelligence tools like Tableau or Power BI or Domo or Looker or whatever, you already have this discipline, and what you need is access to the data, as opposed to using alternative or work around solutions like Hefty Fusion or API processes to scrape the data from Workfront and build your own data lake. We want to give your data teams direct access to the data so they can spend more time in the data, finding the insights, finding those little nuggets of truth, finding the patterns of behavior that are going to help drive your business forward, as opposed to spending their time collecting and maintaining data egress workflows.

The great news, as well as you can see on the slide, is this is available now for many of you. It is included in the Ultimate package. The customer that I was referring to earlier today didn’t realize that they had access to this, and they’ve been spending the last six months, maybe a little bit longer, building Fusion scenarios to do exactly what they could do without that Fusion investment. This is also, as mentioned on the slide, this is available for customers with the Select and Prime packages. There is an add-on offering. You can speak to account manager for more information about that.

Moving forward just a little bit further into the presentation, I wanted to provide some real examples of how the business visualization capabilities that Connect provides, or the data access, better said, how that can be used inside of your visualization layer. Leading up to this webinar, I’ve done a number of interviews. I didn’t receive, I didn’t even ask for permission to use any specific visualizations, and so you’re not going to see any customer-generated visualizations here. They always contain way too much sensitive information, but the visualization that you see on the screen is representative of the types of things that our customers are using Data Connect for right now. I just want to talk through a handful of them. Some customers are using Data Connect as a way to monitor user activity. They’re using it to count the number of reports that are happening per quarter. They’re using it to identify chokepoints in request processes and doing aggregations on aggregations through the visualization tools that are always going to be much more robust in these visualization surfaces than is ever going to be available inside of the Workfront application reporting. They’re using it to generate metrics to understand how long they are spending in specific statuses. Oh, that animation didn’t work.

That’s a little embarrassing. I apologize about that. They’re looking at different time and status and identifying, as I mentioned previously, some chokepoints that are plaguing their business. When we ask our customers, and I have a few more examples here in just a second, when we ask our customers what they’ve been able to accomplish with this, I’m going to provide some summaries of what they’ve said. One customer that’s been using this actually from the time prior to the release of it, where last October told us that Data Connect extends their Workfront’s reporting capabilities. They continue to invest in and use Workfront, as a way to augment the information that they can present inside of Workfront to allow their organization to bring all the data into one place and to put it on a surface that their senior leadership and senior decision makers trust. They’re accustomed to seeing the data inside of Tableau or Power BI and the like. They mentioned that Data Connect simplifies the process of visualizations. It’s become a plug-and-play solution compared to the more complex approaches that they’ve used in the past, like exporting from Workfront reports to Excel and building their data set that way. It reduces the amount of time to get information updated inside of the visualization layer. Data Connect also helps identify gaps in their processes by visualizing the flow of tasks and projects that they can’t necessarily see inside of Workfront because the Workfront data set is what’s current and not necessarily provides the historical data set that Data Connect provides. They use Data Connect as a source for compliance checks. I call them finger-pointing reports to measure how often fields are or are not used in some cases and to improve training and to identify fields that are candidates for cleanup. They’re using Data Connect specifically because their business has come to rely on these business visualizations to do aggregations on aggregated data sets. Other customers that we’ve talked to from this pool of early adopters are also planning on using Workfront on reporting capabilities for their reporting, but they rely on Power BI in their case and the data from Data Connect for more complex analytics and capacity planning or capacity visualization. One customer we spoke to is also using it for SLA tracking. I’m listing all these things because what I want to do is maybe plant in your head some ideas of ways that you can use this data that you haven’t thought of. One of the things that’s common to all the customers we spoke to is really the preference that the audiences that they’re putting the data in front of prefer. They prefer to go to Power BI or to Tableau or other visualization services that they rely on because that’s where all of the other data from all the other systems of record sit as well. They also rely on Data Connect because they can more easily join data with external data sets from those other systems of record, avoiding costly data migrations or data integrations. For example, placing data inside a data center that’s run into custom fields where it doesn’t naturally sit or belong just to get a report fashion the way that you would expect to. Data Connect and these visualization surfaces allow a lot more fluidity of that data as you can join it with other data sets. Multiple customers told us that they use Data Connect to pull into their own data warehouse. So, many customers have investments already where they’re collecting their other enterprise data, places like Snowflake or Redshift, Databricks, you name it. Then they’re able to further enrich the data with the external sourced data and control visibility into who has access. They create more interesting visualizations that describe the whole business and not just the work processes.

They rely on the daily history and transactional event views that we provide inside of Data Connect so that they can tell stories around patterns and the historical nature of how things progressed. It’s not just about where are we, but how did we get there so that they can use this to investigate specific activities and the behaviors that end users are manifesting inside of the data to remove those friction points. I spoke to one customer who was a very early adopter of Data Connect and they describe Data Connect as the location you go to smooth out the data and look at everything in aggregate. That’s kind of this in a nutshell. I want to deviate a little bit from the PowerPoint at this point and actually give you a quick tour of what Data Connect really is when it comes down to how you might be utilizing it. I have my personal environment stood up here in this tab. What you’ll notice is there is within the setup area of Workfront, underneath the system heading or submenu, there’s a Data Connect option. Data Connect allows you to create the connection points. Data Connect will allow you to create a JDBC connection into the Workfront data lake where we’ve been collecting information, the transactional events that’s been going on inside of your environment for about the last three plus years and where we can surface this.

To start using this, really all you have to do is create a new connection. We ask for two inputs, a description so that you know what this is actually meant for, if it’s for a specific person, if it’s for a service user like my Power BI service user versus my Tableau service user, and then a user profile or user credential.

Generating the connection, I’m not going to do this because I don’t need to create an extra one in here, will generate a URL and a temporary password that you can go and choose your own credential. Once you’ve done that, approximately 30 seconds later, you can log into our Snowflake instance where you actually have access to all of the data that belongs to you that we’ve been collecting. There’s over 110 Workfront objects that are currently included and this is growing. When we launched this, there were about 70 objects. And so just within the last six months, we’ve almost doubled the number of objects that we support inside of Data Connect. Each object that we have or that we provide, I’m going to maybe narrow the search down to the projects objects or the list down to the projects objects. There’s a current state view of that project data. There is a low latency refresh that loads this data approximately every four hours, is how fresh the data would be, versus a daily history view. So a snapshot in time so you can track back and see and do comparisons and see how does today match up to yesterday or a week ago or two months ago or two years ago and see how things have shifted on any given project.

Then there’s also the transactional event data view. And this is the data view that you would use is you want to start calculating things like how long do my projects average in a given status or how long does a team take to move forward with an approval decision and look at maybe some of the historical transactions that are taking place inside of your instance of Workfront. This list of data views here is, I narrowed it down, as I mentioned is ever growing. Just recently in the last quarter we added support for the new document approval storage and decisions capabilities. So you’ll see those represented in here. We are in the process of adding Workfront planning as well as in the process of adding a number of resource management data sources that are currently in development.

And we’ll notify you through normal release channels when those objects are ready to be released. Returning back to the deck, let’s talk a little bit about Roadmap. What are our plans? As I mentioned previously when we launched this back in last October, we had about 70 different objects that we supported at that time along with that current state daily history and events views. Since then, we have grown that to, and this is already out of date, I put this together last week. I identified 112 objects. I think it’s closer to 130 now as we’ve continued to grow just within the last six months. And so we’ll continue to invest in this and add more to it. Here’s some of the things that we’re thinking about. So one of the things that we need to work on is we need to finish that work that I mentioned previously around supporting Workfront planning structures and their data.

Workfront planning was released last August, and many of the customers, the early adopters of that product would find tremendous value in us having that data set alongside the Workfront traditional objects. I also mentioned previously that we’re working on adding support for resource management records, including staffing information and different estimates that you put into those staffing plans, both the duration as well as the effective cost of those, down to a finer grain than I think the current resource management views allow, where you’d be able to get down to the date grain and then be able to aggregate the data across multiple different attributes associated with that either planned effort or that actual effort.

We also recognize that as new features are being added, we’re going to constantly be in a mode of adding other features as they launch. And so we’ll always adopt that posture. And we have some things that are on our horizon shortly to improve some of the data that we have around request management, both for documents, planning records, and Workfront. And so we need to include that data. We are looking at some alternate and improved authentication options as well. You saw just momentarily ago the ability to create a reader user. Many of our enterprise customers expect us to also provide an ability to use public and private key tokens to provide that authorization into the data lake. And so we want to support that. We are also in the process of supporting data lakes for your sandbox lanes. Currently, Data Connect only supports the production lane, but we have a proof of concept that’s in the works right now that allows us to accomplish the same thing for the different sandbox lanes that you might rely on. We are also, for those customers that are Snowflake customers, we are looking into options and started research around how do we share your Workfront data inside the Workfront data lake to your own Snowflake data warehouses so that you can do more with the data in a location where that data already resides. So there’s a lot in the data lake. I don’t have a specific timeline of when any portion of this is going to be released, but as I said previously, pay attention to the normal release channels and release notifications and we’ll socialize that there. Okay, let’s move forward in the agenda. Next up was some questions about registration. Nicole, I don’t know if you had a specific format you wanted to do these. I’m happy to talk through each of these individually. Some of these we’ve already kind of talked about.

And if there are related questions from either the chat or the question and answer pod, feel free to interrupt me and also answer this question while you’re on that topic.

So some of the questions that were asked during the registration for this event, when will planning data be available and data connect? We just kind of talked about that. I’ll be a little more precise than the slide was as far as timeline. I’m optimistic that within the next two to three weeks that we will be launching a beta around planning data within data connect. And so if there is interest in joining that beta, the first cohort of customers we’re going to be looking at are people who already have access to data connect and are already implementing planning, but then we’ll open up that aperture a little wider in the next phases of that beta as we prepare for that to become a GA capability inside of data connect. Are there other related questions on that one? I don’t think so, Matt. I think we’ll just try and run through these and then there’s been a few questions coming through the Q&A pod that we will. I’m going to go down as opposed to right and left. So the next question around is data connect replacing Canvas dashboards in Workfront? No. Canvas dashboards is a separate investment that we’re making to further expand the Workfront reporting, the in-app reporting capabilities to include especially the new objects that are being introduced through products like Workfront planning so that you can report holistically across the board.

Along the way, Canvas dashboard has a focus on improving the end user experience and making it so that maybe the learning curve is a little shallower than having to go in and do a whole bunch of text mode to get information out that you’re looking for.

And so we are continuing to invest in Canvas dashboards. We probably could do a separate webinar just on that topic in the coming months, especially as we get closer to some of the release milestones that we hope to achieve in the next quarter or so. And so the short answer is no. Data Connect does not replace Canvas dashboards. It has a different purpose. Its purpose is for more analytical reporting as opposed to what I call descriptive reporting, which is where the Workfront in-app reporting capabilities have historically sat. And that analytical reporting requires a different data set, which is why you see things like that daily history view and the events view becoming available to you through Data Connect.

The question around what people or teams in my org do I need to engage with to get this up and running? So the configuration inside of Workfront is really simple. You saw like 90 percent of it, and it’s really just a matter of being a system administrator and you can create one of those data accounts to use as a connection profile for your BI team or whatever other resources you might need to tap on the shoulder. One of the things that we’ve learned from the alpha and the betas that we executed leading up to the launch is that it is really important to engage your data teams as you’re rolling out Data Connect. They are accustomed to these large data sets.

They have familiarity with the connection set up from the visualization layer and know how to make quick use of it. The customers who did not bring their data teams into the project in the alpha and the betas really struggled to find a lot of value in the product during that kind of kicking the tires trial mode and learning mode for us. But the customers who did bring their data team usually saw immediate results where they were able to start replacing fusion scenario or report export workflows within a week or two of having access to Data Connect. They were able to rely on the Data Connect data instead and kind of simplify their weekly toil or reduce their weekly toil and simplify the automation processes that they might have had set up. So I don’t know if that was an exact precise. Name specific roles, but generally you want to work with your data team in order to fully leverage this data. The next question is how is Data Connect optimizing data workflow and what are the benefits compared to alternative options? So in this case, Data Connect itself and the data that resides inside of the data lake is really providing the historical details that you need in order for you to identify the friction points, the choke points, and so on. And then it allows you to identify those areas of investment that you need to make either in process or training or maybe the way that you configured work front so that you can further expedite work and optimize your processes.

The nature of the data is or the data that we’re presenting is delayed. As I mentioned previously, it’s not real time. I don’t think that there’s a way for us to optimize that much further beyond the four hour refresh rate that I mentioned previously. And so I don’t know that you want to use it as the baton handoff between user A to user B or system A to system B, but it does help you identify how did that baton handoff go either for a specific use case or kind of holistically. Do we see approvals delayed and how does delayed approval impact tasks as an example or task completion which then impacts project completion? And so that is how it optimizes workflow.

And then the final one that we lifted from the registration forms is can Data Connect be used to report on resource capacity and forecasting? And the answer is not quite yet. Though I will mention that during the alpha, I saw one customer do something quite remarkable around resource capacity and forecasting. We do provide access to the assignments table, for example, and so they were able to deduce things based off of that and create some projections into how fast they were going to burn through resources. Now, some of the work that we have planned is going to allow us to do that with the data that is being provided in kind of your staffing plans and some of the surfaces that we have inside of the resource management area of Workfront that I think would allow us to take that to the next level.

So what other questions? We will move forward with anything that has come through the Q&A pod, and if there are other questions that have come up, I am happy to address those as well. Yeah, thanks, Matt. I will just go through them as they came in. So Kristen had a question around offering a test drive for Data Connect just to see if people can get their hands wet and sort of make a business case to leadership by actually going deep dive and understanding the tool. Is that something that is available? It is not something that is readily available. I would need to think through how we could accomplish that. So I am sure we have noted that in our collection of questions, and it might be something I want to circle back to you, Kristen, and then generally to the community if we make a decision on that, we can update you on that.

Okay, great. Another question. I know you had talked about how Canvas Dashboard or Data Connect is not replacing Canvas Dashboards, and again, maybe it is something that we just do our own dashboards, or are we sort of focusing more of our efforts on Data Connect? Yeah, it is not an either or in my mind. We have resources that are focused on the Data Connect aspect of Data and Insights, and then we have other teams that are focused more on the in-app reporting through Canvas Dashboards and supporting the reporting capabilities that we had historically. So it is not an either or in my mind. As far as new visualizations that are planned, there is nothing planned in the immediate future to add new visualization types beyond kind of the tried and true bar charts and line charts and pie charts and stuff like that, that we have the table representations. The stage that we are at with Canvas Dashboards is we are still working on some of the parity capabilities that are absolutely essential, and so the first iterations that will be released will provide very complementary capabilities to what we have today in classic reporting, but we are mindful of the need for us to grow outside of just those core visualization types. And so in our engineering efforts, we are making decisions now that will allow us to do more with it, including the charting library that we decided that we would use as opposed to the one that we are using for classic reporting. It is going to provide us a lot more room for growth as soon as we kind of get through these table stakes reporting capabilities that we have to have when we release Canvas Dashboards. Okay, hopefully that gave everyone here some clarity on sort of the difference between the two and what is kind of coming down the pipeline. So someone had asked around, we are already pulling work front data warehouse and then creating types of reports in like Power BI, so since they have already invested the time of getting data and it is working well, is there a benefit to also going the route of data connect? I think the primary benefit for those organizations that have already kind of invested in the API scrape or the export is generally going to be around the frequency of refresh. The customer that I mentioned this morning, it was in that boat, right? They had invested in Fusion to pull data into their own Snowflake and they were building their own data lake. Some of the challenges that they recognize that they were facing right now and why data connect is more appealing to them than to continue to maintain that Fusion scenario is because that scenario only operates on a 24-hour basis and they do a daily scrape and for other processes, maybe less volatile data, they are pulling out weekly, whereas we are providing a refresh of the data every four hours. So there is one reason why you may want to move. Now, I might be speaking to somebody who has their Fusion scenario set up to pull on the hour or something like that and my argument there kind of falls flat, but I think there are other reasons as well.

One of the primary is the way that we are handling custom data, for example. The custom data inside of data connect is automatically flowing in and is related to the projects and tasks and issues and documents or whatever without necessarily needing to go in and change a mapping inside of your Fusion automation to siphon that data out. So there is some benefit there. The other benefit that I think is just the robustness of the volume of objects that we are pulling into the data connect data lake, you saw it on the slide 112 probably getting closer to 130 objects that we are currently supporting and to create those mappings for all of that peripheral information, including bridge tables that don’t necessarily show up in the Workfront API, things that in the API are classified as secondary objects and are not directly queryable. All of that data is showing up inside of data connect as well, which allows you to be a lot more flexible in building that data set or using that data set to join to information that is maybe slightly more detached and requires one of those bridge tables. I think there’s probably a handful of other reasons, but those are probably the strongest arguments as to why maybe you would want to move to data connect as opposed to continuing to scrape the data. In the conversations that I’ve had with customers that have gone through that transition, most of the time it sounds like it’s really, really smooth where they are able to quickly point their existing Power BI or Tableau visualizations at the new data set. Sometimes maybe there’s some tweaking that has to take place because the way that we reference a column name isn’t the same way that you referenced a column name inside of the data lake. You would have to make those modifications, but most of the work of building the visualization is actually already completed, and so it’s really just changing the source. I think that there is an argument where this is a better way for us to pull that data out.

Even if you wanted to continue to use your own data lake, performing the egress from our data lake by establishing a JDBC connection to a data processor to load the data into your existing data warehouse might be more efficient than continuing to use a Fusion Automation or other API scripting to pull the data.

Thanks, Matt. Another question came in, and for those who are asking, I know we’ve seen a few questions come in like, how do I get access to Canvas dashboards? It is included in the Ultimate package. It’s available as an add-on for select and prime, and so you’re always more than welcome to just reach out to your account team, your account manager for more information or a quote if you are interested. So just again, a reminder that it is technically available to everyone. It just might come as an added cost. A question came in, well there’s been a couple questions here around security, so I’m going to try and maybe compile these into one, but is it possible to create a private data share from Data Connect to our Snowflake so that we keep a copy of our data in our instance and then connect our internal tools to Snowflake rather than pulling directly from your Data Connect, asking just from more control and from a security standpoint? Yeah, that’s a great question, Justin, and that is something that we would love to be able to add to our team. We are very excited about that. It’s not ready for us to present as an alpha or beta feature quite yet, but I’m optimistic that in the coming months we’ll be able to try that out with a handful of you, and we would love that feedback before we release that capability generally. And if customers have more questions around overall security of Data Connect, is that something that you would recommend they connect with their account manager on? Yeah, absolutely, because your account manager will be able to plug into our security team who handles those types of questions all the time. Okay, great. Another question came in around pulling data. I know you had mentioned the new document approvals. What about proof? Someone had asked around, will Data Connect also pull in data from Workfront proof? It’s not currently in the plans, though I am open to looking at that again.

One of the assumptions that we had made early on with regard to the proof, we thought that maybe an interesting piece of that is the decision, and so we prioritized making the document review and approval decisions data available inside of Data Connect, but maybe failed to fully appreciate the other analytics that can be derived from the proof record itself. For example, the proof creation date tells you a lot more than the document version creation date to know how long the actual approval cycle was. And so I think that there is maybe some rethinking on our side that we need to do to make that proof data more available to you through Data Connect.

Awesome. Another question is, how do we make the data that is available in Snowflake available in PBI? And truthfully, that’s an acronym that I’m not familiar with, so Matt, maybe you are. Yeah, PBI would be Power BI. Oh, perfect. Yeah, and actually I debated whether or not I would include a video recording of that. The steps that we provide for establishing a connection in our documentation are quite limited, and so I’m not surprised this question came up. And primarily, that’s because we don’t necessarily want to provide documentation that describes features of other products like Power BI or Tableau, but it may be something we need to rethink and make an exception to because it’s very common. And so I think that would be one that I would want to take offline, and we can have a conversation if we’re documenting who’s asking each one of these questions. I’m happy to walk you through that individually. Yeah, and I almost wonder if it might be better for them to reach out to their account manager or if you have a customer success manager, and then I imagine that you guys can connect offline. Yeah. Okay.

All right, I’m going through the list here. Another question.

What are the most consistent challenges they’ve had in reconciling field names in Workfront to the names and relationship in Data Connect? I’m aware of and regularly use the entity and relationships diagram, but the matching remains challenging, and the tables slash views in the data lake are much more expansive than what is represented in the diagram. Any guidance for managing this challenge? Yeah, I’m just going to skip ahead to another slide. There is a QR code that connects to the help article on Experience League. This is the overview landing page for Data Connect. I want to make sure everybody has access to that documentation, but let me jump into it really quickly as well. One of the pieces that we’ve provided here within the Data Connect documentation is this terminology table. Because to the person who asked this question, to their point, what we call something in the interface is very different than what we call something in the data lake as well. This documentation is an attempt to provide a translation map for you, where something that we call the access level object, and maybe this one’s less exciting because everything’s access level across. In the interface, we call it access level. In the API, we refer to it through this object code, and then the API label, it’s also called access level. But in the data lake, we refer to it as access levels, and then these are the three views for access levels that we provide. That one’s an easy example because it’s pretty much the same across the board. But access rules is a little bit different. The actual entity name is an access rule. In the API, we refer to it in two different ways. It can get really, really confusing. This table here is an attempt for us to document some of those nuances that don’t show up in things like the API Explorer, the table of database relationships, or in the Workfront metadata. This table also includes, it doesn’t include every single field referenced for a particular object, but it focuses on the relationships that exist from the access rule in this case, anything essentially that ends with an ID, and how it’s related to other things inside of the project or a task or an issue or whatever the case may be.

This is the documentation that I would instruct people to review. If there are improvements that we can make, I would love to hear about those improvements so that we can make this more clear. One of the things that, there was a question earlier about what types of resources do I need? We started creating this documentation during our alpha, or during our beta, based off of some alpha feedback that we had received around this front. And we tested it throughout the beta, and I think that we’ve arrived at a pretty good format, but maybe there’s still more that we can do. And the primary audience for some of the other documentation isn’t necessarily the admin that’s been building reports for 10 plus years inside of Workfront, who has a pretty good understanding of the Workfront anatomy and relationships. But the audience is more so for maybe your business analyst team that has very little familiarity with the Workfront data structures and how things are connected to each other. We believe that if they were to use this documentation, they’d be able to to make the cognitive leaps that they need to make fairly easily to get to the data that they’re looking for. All right, we have one more question, and then I will just share a few wrap-up slides. So, Matt, another question came in around the context of campaign performance tracking, and how do Data Connect and Adobe Analytics complement each other, and what do you recommend of insights that are best used for? Yeah, so the insights that are coming from the campaign are going to more describe the in-market activities and the performance in that regard, whereas Data Connect is more looking at the performance of the production of that asset that was used in a campaign, or maybe all the contributing assets, and how long did it take us to do that? So, I think that in the future, it would be very interesting for us to collate those two data sets so that not only can you describe how an asset performed or a campaign performed in market, but you can understand the investment that went into it and the challenges in the investment that went into it coming out of the Workfront dataset, kind of the operational data to produce that asset or campaign. And so, I think that there’s probably a need for us to do that, and one of the things that I think is a stepping stone is centered around Workfront planning. The idea behind Workfront planning is that that is where we identify kind of the initial incarnation of the campaign and all of the derivative necessary pieces to that campaign, and it’s the earliest representation of a campaign as a strategy is being developed. And then that campaign record would have a reference ID number or something like that that would trickle down into all of the other aspects of producing the campaign, including things coming from Marketo or AJO or any of the other surfaces that actually put content out to market. And then because we would have that common linking attribute across the work execution to produce the campaign, as well as the in-market attributions, we can then join that data. And so, like I said, it’s kind of a stepping stone, but it’s a really important problem for us to solve. All right. Thanks, Matt. I’m going to take over and just share a quick screen. I know Cynthia had posted a link to the survey here in the chat. If you guys could just take a minute, it’s a totally anonymous survey, to just share feedback on today’s session. I’ll also share any comments back with Matt, so we’d love to have you guys complete that before you wrap up. Just a couple things. Our marketing team had asked us to help promote the Gartner Peer Insights Survey. There’s two different categories, marketing work management and collaborative work management. If you are interested in filling out the survey, it takes about 10 minutes, you are also entered in or you are able to get a $25 gift card as a thank you. So a little bonus. If you are willing and interested, it’ll end next week on Friday, June 6th. Adobe Workfront User Groups, if you guys aren’t familiar with these, these are sort of your customer-led networking collaboration opportunities for you to get in touch with and, you know, like I said, crowdsource some solutions with some of your peers in your local region. So there are cities like Boston, New York, Philly. What else is there? Southern California, Michigan. So the Workfront User Group program has its own unique link and there’s different chapters that you can look up for. So we’re always looking for new chapters for any other city that you’re interested in. So if you are interested in becoming a lead, there’s some more information there.

The Adobe Workfront Champion Program, this is huge. This is new for Workfront this year.

It’s a really fantastic opportunity for you to be able to share your expertise and be an advocate for Workfront. If you have, you know, a few years of experience, if you are interested in doing some speaking opportunities, just sort of just being a part of the broader Workfront community. And so applications are going to close on June 10th. I don’t believe there will be an extension of that deadline just based on how many applications we’ve received so far. So you guys have about another week and a half, two weeks to get your application in.

And then last but not least is upcoming events. There’s a handful of upcoming events happening in June along with a third quarter release happening in early July. So just put these on your radar. There’s a session coming up on June 10th that’s going to be hosted on the community forum. So it’s not going to be on like MS Teams or Adobe Connect. It’s simply like a Reddit, ask me anything type session around if you’re interested in, you know, asking your peers around Workfront certifications. We have Erickson joining us for a session on Fusion and how they’re, you know, they’ve unlocked event costs using the tool. There’s some of our open forums, which are like our admin chats and our Workfront collective. There’s so much happening. So just bookmark the events page on Experience League and see what’s coming. Someone had just asked about Adobe Summer Break. If you guys aren’t familiar, Adobe has Summer Break here. Customer support is available during that summer break. But for the rest of us, we will be off the week of July 4th. So I believe it’s June 30th to July 4th. So we will not be hosting events during that time. But like I said, customer support is readily available during that should you have any questions. That is all I have for you guys today. I just want to say a huge thank you to Matt for coming and sharing your expertise, your insights, your roadmap, and just being open to answering questions live on the spot for, you know, 20, 30 minutes. So I’m sure everyone on the call appreciates that. And so, Matt, if you have any final thoughts, otherwise everyone is free to jump. No, thank you, everybody. I hope I answered more questions than I created.

I’m sure you did. Yes. And you guys will all get a follow-up email this afternoon. So keep an eye out for that. I’ll do my best to get it out as soon as possible. And should you guys have any follow-up questions for Matt, I’ll also post this to Experience League if anything else comes up. So we’ll see you next week for some more events. Bye, everyone.