Navigating the Workfront API and Fusion Changes for Multi-Select Fields with Ease

Transcript

Hey everyone, welcome to today’s workshop. We will get started here in just a minute. So just bear with us as we let everyone in from the lobby. Like I said, we will get started here in another 30 seconds.

Feel free to say hi, introduce yourself in the chat. Everyone should have access to the chat pod. Just let us know who you are, maybe what company you’re coming from. New to Fusion or if you’re like, nope, I’m here to learn all about what these changes are. As an advanced Fusion user, would love to kind of just get to know some of the folks here on the call.

And David, yes, we will send a link to the slide deck and a link to the recording afterwards. So just know that for everyone here on the call, you will be getting a copy of that. So we are about one minute after the hour, so I’m just going to go ahead and get started. We have a fairly decent amount to cover today. So if this is your first time joining or you just happen to stumble into today’s workshop, welcome. Today we’re going to be talking about navigating the work for an API in Fusion changes for multi-select fields. I am joined here by Andy Hess from our professional services team who will take lead on today’s workshop. But just a few housekeeping items before we get started. This session is going to be recorded. And so if you are unable to stay for the whole time, no worries. We are going to send you guys a link to the slide deck and recording and any other resources that you may need after today’s session. So just keep an eye out for a follow up email from the csatscale at adobe.com email address. We’ll likely get that out this afternoon with all of the resources. And should you have any questions, you’re always more than welcome to reach out to us directly.

Also from a housekeeping standpoint, you guys should all have access to come on camera, come turn your microphone on. You have the chat pod, you have the Q&A pod. So these are all going to be available to you throughout the session. So feel free to just raise your hand or come off mute when Andy is presenting. Should you have a question, we are going to make sure that there’s ample time and pause kind of after each section to make sure that questions get addressed. But the chat pod is likely used or we probably recommend it using it for sort of just asking your peers recommendations, best practices, questions, maybe some tried and true things that they’ve done with Fusion. If you have a question for Andy, I really just encourage you to post that in the Q&A pod just so that I can use that at the very end of the session to go through the Q&A. So with that, that’s all I have. I think from a housekeeping standpoint, I’m just going to stop sharing and pass it over to Andy. And Andy, I imagine you have some sort of introductions and agenda, so I will let you have the floor.

All right. Well, hey, welcome, everybody. It’s been a little while since I’ve done one of these, so happy to be here in front of you guys. Unfortunately, not being an individual contributor consultant anymore, I have less opportunities to get out and see all of the constituency out there. So I always appreciate these opportunities. So nice to see everybody.

The presentation that I’m going to go through is intended really for, I’m going to suggest all audiences. And the reason I’m saying that is some of you I’m recognizing and the names up here are pros at the work for an API and Fusion. And these are concepts and things that you’re really comfortable with. Some are not, though. So this is intended to be really for all audiences. So I apologize if some of this is rudimentary for some of you, but I promise there’s some meat in here and some information that you’ll all find very helpful. So with that being said, let me go ahead and just kind of step through what we’re going to look to talk about today and, you know, initially writes what’s changing. You know, why does it matter? And you’ve probably all seen some information around versioning a Workfront event subscription. And what does that mean? And what’s coming with some of these changes? Is it changing the Workfront API? Yes, it is.

So.

Did you have a question, Annette? Andy, I’ll just go ahead and mute everyone. But like I said, you guys, well, I’ll have the option if you do have a question, please just raise your hand and we’ll get to that. Perfect.

So.

The along with the Workfront API version, there’s going to be a Fusion version for the Workfront connectors, and that’s an interesting concept. You’ve never seen that happen before the way that this is going to be presented to you. So I’d like to show you what that’s going to look like. No, if you save it as a new view, it becomes your.

Must be hitting your spacebar. Yeah, you can share it.

I’ll just go ahead and just turn off the microphone for everyone at this rate.

OK. No problem.

So, well, what’s changing? And some of you guys may have seen this. For those of you who’ve worked with the Workfront API for a long time, you understand that there’s a kind of a weird thing that happens with multi-select data.

And there’s a scenario where if only a single value is picked, it’s coming through and can be entered back to the API as a string, meaning just a value.

And this is an image of a JSON structure and how the API communicates.

So a single value can come through as a string. But when that exact same field or type of field could present multiple values, it’s going to come through as what we call a simple array.

And a simple array, you can see here, what’s different is this hard square bracket, right, where the choices are kind of comma separated inside of this square bracket. And that JSON structure we call a simple array. Now, that’s created some fun because it’s inconsistent. And the new method you can see here, it will always have the bracket, right? It’s always going to be considered a simple array. It’ll just be a simple array of one.

Well, why? Why would they change that? So the old process and the way that it was presented was inconsistent, right? And it caused a lot of workarounds to have to occur. And it was one of the first things that if I’m working with a new developer and the work for an API, they’re like, well, how come it’s, you know, sometimes a string and sometimes an array? And because it causes errors in their process, it can cause errors in a fusion process. You could be expecting a single value, but instead the system is trying to ingest an array and that can break your fusion scenario.

It can do the same thing as, you know, people working in custom code and they’re developing work around our public API. So it creates problems. So it’s being changed because the consistency in that will help simplify adoption of work for an API for developers. And it just makes things easier for it to be stable. It’s a change that should have happened five years ago. And finally, they’re going to pull the trigger. And in version 21, they’re going to make this change. So this is going to be a change consistently across the API. Right now, the change is going to be initially in the event subscription.

So the concept of versioning in an event subscription is simply related to whether the information coming into that payload in the event, when it’s a multi-select, will it always be a simple array, meaning version two, or will it be varied content, meaning might be a string, might be an array.

Now, with that being a case, does anybody have a specific question around that? Does that make sense? Is any confusion around that? And again, I did see a lot of knowns in the chat, so perhaps everybody’s got it. But yes, Latin add empty array multi-field. Yes, that’s exactly right. That little work around that those of you who work with Fusion is something that you’re used to messing with. Right. And once it goes to version two, that will no longer need to happen. I think the good news is that statement always worked, whether it was multiple values or a single value, didn’t it? So when you change to version two, if you had a statement like that in play, it won’t break. Right. And where it might break is where you didn’t have a statement like that, where you have a field that was expecting an explicit value as a string. And instead, now it’s going to get an array. And I think that’s where the opportunities for it to break. Right. So. Gregory, I’m going to take a moment just to kind of review your question.

All right, just to read it for everybody, one of our main interactions makes use of variables for the multi-select fields.

Right. And has data matching between the work front value and the other systems list value.

Should we be worried? Let’s see.

For the multi-select field. And again, as long as you’re expecting it to be an array today, it wouldn’t break. If you’re expecting it to be a string, that’s where you could have some trouble.

OK, Andy, another question came in the Q&A pod. What’s your advice on how we can look at our current scenarios to identify which ones we need to update or fix? That’s a really good question. I don’t know that there’s a simple answer there. I think in some ways it is going to be a bit of a process. Right. You’re going to need to understand where you have multi-select fields.

Yeah, David, that might be a thing. Right. Just pull the trigger and see what happens. Right. That’s actually not a horrible idea. Most of us should be leveraging Fusion in more than one team. Best practice is to have a dev QA and a production team. Right. And your scenarios as you’re working on them, start in dev. That’s your playground. You could version this to version two in your playground, run the system, run through a UAT script. Right. Hey, run this process, this process, this process through the scenarios and make sure that you’re not running it into any issues. And if that’s good, sure, then you can promote that or version that in the upper environments. But that is a good way.

The other is some of it you might know, like, you know, you’ve instituted this flat and empty array type thing into your processes.

So if you’ve done that already, then it’s going to be fine. You’re not going to see an issue.

I think where we might run into some issues is on updates to fields. So I think that would be something that we would need to test. Unfortunately, because the event subscription is happening in advance of the Workfront API being updated.

A lot of us, I would suggest that it might be a good idea to kind of hold hold tight a little bit. Like don’t necessarily change your event version, although because that’s really the ingest payload that gets affected, not anything you do with it downstream.

It’s probably relatively safe to update that. But again, do it and test it, do it in a lower environment.

Where other things can happen is really when the Workfront API catches up, which isn’t going to happen until like October.

But sticking with just versioning your events right now, you know, there are a couple of things you should know when you create a new event today, it’s automatically going to be in version two.

You have a manual process where you can push it over. There is so there’s a directly an API in the event that you can use. In Fusion, there is a module that’s been created specifically just to version your events. And you can do it for every single scenario in that team. Or you can do it for just ones or a list of individual scenarios that you would that you would want to update.

There is a window to where the event subscription will be able to be downgraded, like where you’ll be able to go back and forth between one and two. But that’s kind of a short period. Once you move to version two, they’re going to want to try to hold that.

And what we’ve heard right now, the messages that in mid-January 2026, the system is going to automatically on the back end push everybody to the version two of your events. So this isn’t something that you want to ignore and you’re going to want to keep an eye on so that you don’t have any surprises in January.

I’ll also follow up. We did an event in partnership with the software development team earlier in May. And they had talked about maybe potentially figuring out a way to build a report to help identify some of those fields that are going to need updating. And so I will follow up with them and see if we can get any more information. So I’ll include that in the follow up email that goes out this afternoon. Thanks. So Gregor, you asked a question about selectively updating in different environments.

And this really has to do with what I like. I like to use the team construct in Fusion to create an entire group of scenarios and connectors that are connected specifically, let’s say, to sandbox one. So let’s say Dev, you create a team called Dev in there. You have connectors only pointed to sandbox one and then create a QA team and only connect that to sandbox two. Create a prod team. So if you only have a my team and that’s just your out of box team, then I would rename that, maybe call it production or leave it my team and create a prod team. And if you’re just using one team today, you might have in there connectors and work front for all the different environments. You could have a sandbox, a preview and a production connector for work front in one team. I wouldn’t consider that best practice. Really, we want to separate those into different teams, align those teams to environments, and then it’s much easier to track and to manage those types of changes, Gregor. So also when you would use that Fusion module to say update all my events in this module, it’s going to do it for that team.

And push those through.

So I had talked to this a little bit before about the work front API versions. So our current core API is version 20. It was released in March.

Typically the work front API is versioned twice a year. And we have another version coming up in, I believe, October that will be version 21. So, you know, and again, this is information a lot of you guys are familiar with, but, you know, our API again goes through these cycles. And about any version is going to basically fall to be unsupported within about four years of release. I think right now we’re getting ready to decommission version 14.

So that’s one thing you want to keep an eye on. And I think I actually saw somebody doing an external lookup script, calling back to work front and an external lookup, but they had v14 in the API call and the external lookup, and it was failing because we just depreciated version 14. So keep those in mind. Now, prior to version 21, the payloads of both input and output on those multi selects are the way that they’ve always been, where it could be a string or a simple array. But in version 21, they are going to roll that up so that it’s aligned with that. And thanks, Cynthia. And there’s some links here in this presentation that you’ll get a copy to that will take you to some of the same links that Cynthia just provided.

So the other thing that’s going to be happening is the work front connector itself. So you guys have probably seen if you’re familiar with Fusion modules that have this little funny green arrow, right. And this seems a little grainy. You probably can’t read this, but it’s basically saying there’s a new version right of the app available. You want to consider replacing that with the new version.

And with work front, what they’re going to do is there’s going to be another button right here that lets you click right there and say, go ahead and version this. And what it’s going to do is it’s going to change it to a different app. And with the understanding that with that now it’s going to always have an array output from a multi-select and always be expecting an array input, right. If it’s a put or a post or you’re creating an object right for those multi-select type fields.

So keep that in mind that there will be a process coming up that hasn’t been released yet. They haven’t mocked it up. So I haven’t been able to pull anything in from the Fusion developers to indicate what exactly that looks like and what that process will be. We do expect this to come out in alignment with the API. So again, in October sometime, which is usually the second week normally of October, these releases come out. And when that happens, this feature for Workfront modules will also be released. Now, you might ask yourself why. Why would Workfront release a new version of the app versus what they’ve been doing all along, which you can just go in and like select the version of your API right there in the Workfront modules, right. Usually it’s like in the custom API, you can pick the version.

And in the other modules, normally it just tends to roll along. And I think the Fusion team actually like once or twice a year, you know, they’ll move it into the next version. I think right now they’re using version 19. Probably in October, they’ll roll it to use in version 20. And, you know, they tend to maybe not go bleeding edge, right, and work with the API version that’s probably been out there for six months or so. And they automatically do that. Now that won’t happen here. And our current, what’s going to happen is the current Workfront modules are going to get like a legacy type indication. And you’ll see this little green arrow saying that they’re in the old version.

We’re making this a manual process because if it was automatic, it could introduce a breaking change, right, where you’re not expecting it to come back as a simple array. You’re not expecting to ensure that your put to the field is a simple array, right? So you’re going to probably need some updates in your environment and your code to align with that change. So rather than making it too easy, they’re kind of making it a, you know, hey, stop and think about this moment, right, where you need to take an action to roll it up.

So we expect after this that it’s kind of go back to the old process.

So unless the API is releasing a breaking change, we probably won’t see this again for a while. If they do, then this will be the process that it will follow yet again. And we’ve done that. You can see I’m using frame as an example. I know this is a process for ADO and quite a few other third party connector modules out there. You’ll see this type of a process.

Or you can, you have to update it. And I think what they’re doing with Workfront, rather than having the user, right now, the user would have to create a new module, right? They’d have to create a new connector module with the new version because what comes with that is remapping things, which is a bear. You know, if you insert a new module and you’re consuming data downstream from that, if that map number changes, it can be a bear managing that. So that’s why they’re going to have this little trigger button that’s, again, it’s not showing, but there will be a button that will let us take the existing module and roll it to the next version. And that way your module number stays the same and you don’t have to remap everything downstream.

So there’s a reason for doing this. Number one, why it’s a manual step, but number two, they’re trying to make it as easy as possible so you don’t have to go through, jump through too many loops, right, and remap everything.

The expectation is this is going to come out and we’ll have additional training that we can release to it, probably in September, in advance of it happening in October.

And I plan on revisiting this particular post in Experience League because, as you guys all know, these webinars get posted up to Experience League with a chat. And as that comes out, I’ll come back to this chat and provide additional information and links to new information and exact functionality that the Fusion team has released so that you can have one place you can go and check that out.

Andy, I’m just going to pause you here for one second if the question came in. Is this change related to a legacy versus not legacy module as well, or is this different? I would say it’s not the same as a legacy versus non-legacy.

When we see those legacy versus non-legacy, it’s really more of a, those types of changes have more to do with not an API level change, but a difference in the way the Fusion module operates.

And like right now, we have a legacy versus non-legacy module, and it has to do with like selecting the custom form that you want to map from versus it automatically loading every value from every custom form. That’s the current thing that you’ll see in a Workfront module that says legacy versus not legacy. It’s around the idea that it’s a lot easier to pick from a smaller list of field values by saying this, give me only the fields on this form, right, or these three forms versus, you know, everything. And if you’re some of our larger accounts where you’ve got thousands of fields, it could be really handy to just pick a certain form. But that legacy change isn’t necessarily related to the underlying API, and that’s why this is a different step altogether.

Thanks, Andy. I know, and also for just that teaser of the frame, I know people were like, oh, what’s happening with that? We’re going to be hosting a Q&A session on the new document approvals, which is really the future of proofing, you know, talking about the Frame.io integration in partnership with the product team on July 22nd. So that event is on Experience League. If you are interested, Jason’s going to be leading that, the product manager, over that. So for people who are interested in that frame sort of future of Workfront, that would be a great session for you. Yeah, that’s going to be a very good one. I’ve worked very closely with the Frame product team. What a great group. Just I can’t say enough about that entire team.

So a lot of the what’s on this particular cell here we’ve discussed, but here it is in writing, just kind of going through some of these best practices, using lower lanes to go through the test, test the change and stuff like that, and what you’re looking out for.

So let’s talk a little bit more about maybe other things are changing, which there are. There are more things happening in the Workfront and Fusion world that are coming. And I think it’s important to talk about that as well. So the main thing, right, that we’re really talking about now is this breaking change with the JSON consistency.

So that’s obviously a big deal, and that’s the core of the discussion. But there’s another thing that’s happening, and there’s a link here in the deck on some other things that happened with events today. When you get an event on a create, and if you’re watching creates and updates, what you normally will see happen is you probably get two events, right? If you’re watching creates and updates, you end up getting like a mirror of the payload, and that can cause some consternation around getting duplicate functionality, right? You could go from an intake request and create and spin up two projects if you’re not careful in how you’re building your Fusion scenario. So they’ve recognized that as like a common issue, and there have been some additional things really that also kind of support how this will work. But the reason that you get the second pass is because you’re looking at updates and because calculated fields and those events normally would happen after the first, like when you hit submit, and then calculations occur. It sees an update, you get another event. What’s going to happen now is that they’re ensuring that those calculations are going to occur and present themselves in the original create payload. So you don’t have to both go get the second call because you maybe need those calculated fields. They’re going to be there on the first call, and you won’t get a second thing that could cause a duplication of a process. So that’s a big deal. That’s another that’s a great reason for moving to version two on the events today. The other thing is they’ve changed a number of other behaviors. I think delete is an interesting one. If you’re registering deletes, you end up getting kind of a weird payload on that, and they’ve adjusted that to make that easier to manage and understand.

There’s a link there. Definitely follow up, take a look at what is changing in the version two of the event. It’s a little bit more, like I said, than just multi-select JSON consistency.

I don’t know what else is changing in version 21, just because they haven’t released yet what’s coming. So obviously we’ll all be watching to see what’s coming out in version 21 of the API. I’m positive there’ll be things in addition to this. I think one of the things that might be coming out in version 21 will also be like the approval API, the document approval API, which is going to be a new element. It’s also kind of what we mentioned frame. A lot of what’s happening in the frame native connection is based around the new document approval API. So that’s going to be a really great thing that we can leverage for things other than frame as well.

The fusion connector and the change here also is more than just managing and using the new version of the API.

One of the other things that they’re going to do is that indicator and update process. That’s kind of a new thing. They’ve never done that before.

That’s going to make these types of changes a lot easier because it’ll hold your connector or your module number. Your mapping IDs will remain. But the last item here I think I’m most excited about and that’s you’re going to be able to use an Adobe technical account. So an Adobe API technical account can now be used when they release the new Workfront connector as your connection account, your service account. So instead of having to have the client go and create an account in the console connected to the domain or whatever they’re doing to create a service account, you’ll be able to use an Adobe console technical account.

And in a lot of cases, for those of you who are using AEM and using the native connector with AEM, best practice is to probably use that technical account that you’re connecting to AEM with.

So it really simplifies a lot of things. Are there any questions about that particular item? I saw some thumbs up, so I think you guys were excited about that as well. I don’t think any questions, just some excitement. All right, cool.

So that’s pretty much it. And we kind of went through this quickly. I had a feeling we would.

And you know, really just kind of want to open the floor for any questions, anything else you guys want to chat about, best practice, how to manage this.

Andy, do you mind if I take over your screen for a second? I’m going to share a few things that are happening in the Fusion world from a resource and an event standpoint, because just in case people want to drop for the open Q&A, I at least want to let you guys know about a couple of things that are happening, especially this right here. And can you guys see my screen here around an in-person scale up for Workfront Fusion? Okay, great. Okay, so this event, we kind of just heard about it. And so we are very eager to share that there’s going to be an in-person Fusion. Think of it like a lab, like if you went to Summit, an in-person Fusion lab, hands-on working session in New York City on July 16th. So if you are in the area, you have to have Workfront Fusion already. You can’t be sort of, you have to have like a paid Fusion license to attend because you’re going to need to bring your computer, open your Fusion instance and sort of follow along. It’s absolutely free to attend. So if you are in broader New York City area, mid-Atlantic and are interested, I really encourage you to attend this session. Like I said, it’s a free hands-on Fusion lab, full day, I think like a nine to four type of event. So great opportunity for you to learn and connect with some of sort of our technical experts in the Fusion space. So that’s probably the most important thing I wanted to share. Cynthia just posted a link to that in the chat.

Just an update, I know Andy has kind of talked about some of the API and Fusion updates that are coming. The actual Workfront release is happening in, what is it, second, third week of July, July 17th. We’re going to be hosting a release webinar in partnership with the product team a week before July 10th to just sort of prepare, enable you, get your questions answered. So just know that that is coming down the pipeline for you. Just some Fusion event templates, or I’m sorry, Fusion scenario templates are now available. So if you haven’t checked out, there is a documentation on experiencing around like templates that you can, you know, basically tried and true, easy to install. Just be sure to bookmark that check back often because there’s constantly new templates being added. This being one of them, where the change project timeline when tasks completed early, so that’s available to you. I’ll also just, I’m not going to go through this. This is just some documentation on Experian League. You guys will get a copy of this slide deck in the follow up email with all of these links. And then just upcoming events. We’re hosting a session tomorrow on Workfront planning. Like I said, the third quarter release is happening in July. There are some open forums, which are our admin chats and the collectives. Then the content approvals. That’s the, you know, future of proofing and Workfront in partnership with product and then another planning session at the end of July. So I think that’s all I have. And I will just leave the next say 25 minutes. Yep. Amazing. I’m just going to stop sharing my screen here and you guys have 25 minutes. Floor is yours to ask Andy any questions you have. And actually let me turn microphones back on in case anyone wants to come off mute.

Yeah, so I apologize I didn’t have more on the Workfront Fusion modules to be able to show you more of a sneak peek of exactly what it’s going to look like and how that functionality works. But we’ve had some great partnership between services and the Fusion product team to talk about what would be the easiest way for our users to be able to manage this change. So they’re taking some heavy strides to ensure that it’s as simple as possible and requires less, you know, less impactful changes as possible. All right, you guys should all have access to your microphone, so feel free to just come off mute and ask your question.

To Andy.

Okay, I think everyone’s having lunch.

Maybe you just did such a great job explaining things, Andy, that everyone feels enabled and prepared for what’s to come. I can start the process by asking a very basic question. New user here, new Fusion user. So basically I’m asking to summarize what’s happened. So basically, like, Wow, I’m sorry, I totally blanked out. So never mind.

Well, you know, it’s hard to come off mute right and speak in front of 100 people all of a sudden. And yeah, but I appreciate you giving a shot. The chat will be available in this, you know, Experience League and I’ll keep an eye on that over the next couple of days. So if it’s something you want to ask, you know, ask it in the Experience League post once this gets put up there, which is probably going to be probably late today or tomorrow morning sometime, Nicole.

And yeah, you guys can can chat with me there. Ritesh? Yes, sir. Thank you very much, Andy, for the wonderful presentation for Nicole and all the other organizers. It’s really helpful to hear what’s coming up and everything else associated with what you said. Question. In regards to AI, since we have a lot of AI that is coming in, is there any plans around having AI do the actual Fusion work for us and we as system admins, directing AI to go pick things up and connect, you know, use connectors, use whatever we need to to connect every other tool to work from that we have in our system here today. So AI is now advancing day by day.

Yeah, very quickly as well, right? Yes, I think it’s almost hard to keep it to stay on top of the horse, right? Right. So there are a couple of things. First of all, I know that we do have the ability to use AI in Fusion today to create scenarios for you or create different different connections. So there is today a, you know, kind of like an ask AI feature to go, hey, I want to, you know, convert a request to a project and it will create the three or four modules to do that. And so there does exist AI features in Fusion today. And yes, it is being expanded all the time. I, you know, had a look at the development schedule and what’s coming up. And there are a good number of AI elements that are, that are constantly being worked on. So yes, you’re going to continue to see additional enhancements in how you can leverage agentic type processes, you know, in Fusion and make your job, make your job easier. The other thing that’s coming is we now are, will very soon be releasing an MCP connector. So if you’re familiar with that technology and connecting to AI libraries, that is a big deal. It was very funny. I was just in a discussion with the Fusion leadership team, and we spent a lot of time talking about some other really cool things coming up that we’re going to release in parent-child interchained scenarios, which is going to be really amazing.

And in my mind, at the end of the call, it was like, oh, by the way, we’re going to have an MCP connector for AI agents. And it was like, what? You saved the best news for last, right? Because that really will change how we’re able to leverage Fusion and also connect properly, right, to all these different tools that are on the market for us. So that’s coming very soon as well. Well, thank you.

For this, I think we say coming very soon. I know that our team is usually like, what’s the timeline? What’s the ETA? Because everybody’s super excited about news like this. Yeah, well, the change scenarios Sam just put out there, there is a beta that if you’re interested in leveraging, reach out to Sam Taylor. I would suggest the same is true when it comes to like the MCP connector and things like that. There definitely would be, you know, looking for people to help test it. I know that it’s already passed in. It’s through internal QA and it’s really just going through the cycle that, you know, the final cycles it has to to get through the release. So a lot of this stuff is going to be available pretty soon.

That’s right, Travis. I think one of the biggest things that we have to continue to work through in the parent-child scenarios is just making sure that we understand how we handle errors, right? What’s the best way to manage that? If the child is erroring, how does it report back to the parent and things like that? And there are some processes that we’re working through. And so we’re definitely looking for some beta on that so that we can get some feedback from the larger practice out there.

I think Lindsay has her hand raised. Yeah, I just want to follow up question to the AI question. If you’re saying we have those capabilities today, is there any documentation on like where we can see that in Fusion? Because I feel like I don’t see anything AI related in my Fusion instance. And so I’m intrigued by that and I want to have access to that.

There we go. So Sam just dropped this in the link and thanks for coming on camera, Sam. But that’s why I have Sam here is because he’s a direct link to product when it comes to extensibility and work front. And he is the guy. So he’s placed in a link on exactly how you use Fusion’s AI Assistant. It is there, but it’s not obvious, Lindsay. I agree. Like it’s not the most obvious thing in the Fusion platform. But that link will show you how to use it. Okay, interesting. Is it related to license levels, Sam? It’s related to an AI agreement for generative AI. And, you know, as you probably know, it’s really important for Adobe for us to provide a business safe AI, and to be really clear about how AI is using your data. So that AI agreement has to be reviewed, you want to make sure you understand that and sign that before it’d be enabled in your environment. And then if you have questions about that deeper ones beyond just reading the agreement, you can work with your account team, we can get those to you. But that’s all about making a business safe AI available so you can actually use it in production. Okay, sounds good. Yeah, I’ll reach out to my account manager, because I think we have it for work front proper. But for some reason, I just don’t see it in Fusion. Oh, it might be a matter of just getting that on file. And that’s, you already went through the approval, then it might just be an administrative change. That’s awesome. Thank you so much for clarifying. Yeah, but I would also be thinking about the MCP server, that should be pretty big, I think that’s going to be a little disruptive in the API low code automation team. So if you start market, so when you think about potential future tools, understanding how MCP is used, understanding how you models that you might have access to and the type of tools you might want to work with are good things to think about now. And then in our next roadmap, as we release probably towards later into the year might be an update where we can say this is when to expect it. As Andy said, we we’ve worked a lot of technical stuff, and now we’re just working through the go to market on it.

So Tracy, are you asking if there are customer success at scale events on templates? If we have customer successes, that would be even better, right? Like in terms of use cases, but I’m not sure first what’s coming in terms of templates, and then the templates that we currently have just in terms of hey, this is a scenario that we can play through because I know that they are there. It’s always for at least for me, I’m not sure about the rest on the line.

If you have something like a scenario that you can play through, not a fusion scenario, but an actual scenario to play through with a fusion scenario. And if there is a template, that’s usually like a step by step. That’s super helpful for me. I’m not sure if that’s doable, or if this is going too much into dev.

Okay, so you mean more like a document that kind of walks you through, right? This is exactly how you would deploy it and the elements and how it would connect to let’s say, an operational process and work. Yeah, document or just those are the templates that we currently have in the system. Here’s where you find them. This is what’s coming. And this will help you use case ABC, for instance. Okay. Now, a fusion is really where, when we talk about templates, is probably the main, is really just a fusion element, right? And that’s going to be available just in the template menu in your fusion environment. So there’s a pretty big list there of templates and you can search that. And that’s right. Experience League will also have some pretty good documentation on templates.

I know that the templates are something that in fusion specifically that are kind of near and dear to the customer success team. I know Euan and Jennifer and team, those guys are constantly trying to come up with, you know, the next tool that really helps and supports the clients build out scenarios quickly. And adopt the tool as easily as possible. So it’s a big deal. Workfront blueprints is another concept, though. And I think at some point we’ll start to have some alignment between a workfront build and the fusion build. And I think that connecting those two things will also help accelerate our ability to, you know, to scale the processes for you guys.

I will, before I get to your question, Rohitesh, there’s actually a post on the community forum, and I’m not sure if it’s been closed, but Jen at one point, who is on our customer success architect team, had a call for like fusion templates. So if there was a fusion template that you’d like to see added to the library, that’s kind of where she pulls her ideas from. And like I said, we kind of released them on a, I wouldn’t say a regular cadence, but you know, as bandwidth allows, we try and, you know, get out new, you know, fusion templates on a pretty, you know, regular basis. And so I’ll dig up that community post. And that way, in case you guys do have ideas for additional fusion templates, you can post those there. Because I know Jen is always, her and you and I are always looking for more ideas.

For sure.

Thanks, Tracy. Rohitesh? Thanks again. I’m being lazy and just hearing the questions that are being asked. I thought I’ll ask a question that is related to my laziness situation here.

It would have been nice if the AI was able to hear out a scenario, and then pick a template for us here at a scenario when we type it, and then pull out what is the most optimal solution for what we’re trying to do. Because that’s what AI is really intending to do to help customers out. So if that kind of intelligence can be built in using models across the 3 trillion data sets that are available, would have been very nice. It’s going to help boost productivity and start off with the most efficient solution, instead of having to think and scratch the head and say whether this one or this other one would be more suited to our needs and have a brainstorming session for that.

Sure. I know that we definitely leverage some of our internal AI tools all the time to mine all the information that we have out there and we’ve collected in Adobe in general. And we use that quite a bit internally for that purpose specifically. So that is something that we do internally as an enablement for all of us here internally at Adobe. So we are using AI very heavily in our day jobs, that’s for sure.

When will we be able to leverage that to customers so that we also get the benefit of what you have? Great question. And that’s really, I would suggest it’s part of our principal focus as we think about what we’re doing over the next 12 months. Most of it is geared on how do we responsibly harness AI and put it in the hands of our users. So that is our motto right now. That is what we are actively looking to do. So most of what we do is exactly towards that focus.

Well, I think that’s probably we’ll call it for the day. I appreciate your interest in joining me and spending some time talking through this. I’m sure you guys could use eight minutes back of your day. I know I can, but it was fantastic to see everybody. And I’ll keep an eye on the chat when this gets posted. And if you have any other questions you could think of, it will be available. Thank you all.

Thanks, Andy. Keep an eye out for a follow-up email this afternoon with all the links and resources from today’s presentation. And so if you have any feedback to share, please be sure to just add that in the anonymous survey that Cynthia posted in the chat. Otherwise, we’ll be publishing this to ExperianCe. So should you have any other follow-up questions for Andy and team, you can always post those there. So seven minutes back in your day, guys. Have a great rest of your week and we’ll see you soon.

Take care.