Fusion Decoded Part 2 – Let’s Start Building

Transcript

Welcome everyone. We’re happy to have you today for Fusion Decoded Part 2. Let’s start building.

I’m Leslie Spear, part of your Workfront Customer Success team. I have with me Nicole and Cynthia also on my team. Jen is part of our extended team. We’ll be hanging out in the chat as well as I see Sam Taylor is here. So you’ve got a lot of friends here, so don’t be shy. Feel free to ask questions. We’ll do our best to answer them or we’ll get back to you if we need to look into them a little more. So just a couple of housekeeping things if you can go to the next slide. We are recording this session. So you will get a copy of this recording and the slides and some notes later via email. So keep an eye out for those.

But I think that’s all you have for me. So I’m going to hand it over to Jen, who’s going to share her magic and do some demos today. So give her a little grace. We all know that live demos are chaotic in their own way, but she is such a great volunteer to walk us through this journey of starting Fusion, what it is, how you get going. So Jen. Awesome. Thank you so much, Leslie. All right, welcome back. Welcome to the highly requested part two of Fusion Decoded. Let’s finish what we started last November. But I should probably introduce myself first. So I’m Jen Desmond. I’ve been a technical success architect for Workfront at Adobe for about four years. We’re getting closer to five every day. Before Adobe, I was actually a customer. And one of the main reasons I made the switch over to Adobe was actually to learn Fusion. So I learned Workfront the hard way by self implementing, which gave me a lot of empathy for customers. I have a lot of grace for you, let’s be honest. I also didn’t come in with any API or automation background. I oversaw integrations, but I did actually build them myself. So everything I know about Fusion, I learned from scratch after joining Adobe. I am so lucky to have great experts around me, but I’ve also pushed myself to learn hands on as much on my own as possible. I have been through a lot of pain. Let’s be real. So I truly see it from your perspective. We also have Sam Taylor, our senior product manager over Fusion here with us in the chat. He’s gonna join us in the Q&A fun at the end. So many thanks to Sam for joining us today.

All right, so what are we gonna cover in part two? Well, I’ll catch up those of you who didn’t join us in November. And then I’m gonna tell you a few particulars about the demos. And then we’re going right into Workfront and Fusion to get those demos completed.

So I don’t wanna spend a ton of time recapping. But I also want you to know how we got here. So the first part of Fusion Decoded covered the deceptively simple topics of what is Fusion, what can it do, how do scenarios work? And then we started the demo. As I’ll show you later, we didn’t get very far there, so that’s why we’re here in part two. We did get to that last topic there that I have there. What is it? How to get started? So we’re not gonna cover that either. So this session can certainly stand alone in terms of demos, but the link to part one is there. If you wanna go have a look, see the recording, check out the slides, it’s there.

All right, finally, let’s talk about what you can expect from the demos. I’m gonna show you today.

So I showed this before, but it bears repeating that we’re here to live demo how to start a scenario from a template and edit it. If you have Fusion, you have access to the templates. Because of that, this is a more beginner level session, sorry. But I hope it’s valuable for all. I’m here to show you the value and the magic of Fusion. And in turn, get your automation and integration ideas flowing, get excited. See what you can see, find what you can find.

Everything I’ll show you today was inspired by real customer asks. To save time, I’ve prepared a few scenarios in advance. But again, no matter what, everything came from a template originally.

I’m triggering the scenarios manually. But in part one, I told you all, all, all about webhooks and pulling triggers, which are options for you to start a scenario. And you can learn more about them in part one. Lastly, this is just a disclaimer because I have to put it here. I’m using my personal work for an instance for these demos. It is a huge mess. It’s very embarrassing. One day I will get to it. So imagine what you’ll see with the data you’re used to.

Okay, we’re going to take another step back in case you don’t know what a Fusion template is. So like I said, if you have Fusion, you have 57 Fusion templates available to you. A lot of them my colleague and I built based off of feedback from customers. Most of them are work for an automation, but there are some integrations kind of in there with Marketo, Anoplan, Jira, there’s a couple more, I think. So basically, you’ll be able to implement what you see today as soon as you’re ready.

When we create Fusion templates, there are a few things that we can’t include in them, like custom fields and data stores and things that are specific to your organization.

We’ve had to create them in the ways that we can. Expect to do a little bit of work to replace triggers, webhooks if you want to do that, add your custom fields and whatnot as you adapt them for your use.

Okay, so here’s the list of intended automations that I wanted to demo on part one. We did actually finish up numbers one and five. So those are crossed out. But we’re going to actually revisit number three because I was impatient and I didn’t wait long enough for the data to appear in Fusion for us to work with. So I’ve learned my lesson and I’m going to slow down and we’re going to get to the number three. So in the real world, some of these automations that I’m going to show you, you’d kind of like blend them together to form something more cohesive. But I’m singling them out here for demo purposes, obviously, because it’ll make more sense to you if we evaluate them in small little chunks. And I’m going to be able to more easily show you, excuse me, how Fusion is influencing Workfront.

So for most of these, Fusion sends updates about what it did in the objects. And this is huge. It really helps everyone in Workfront understand and appreciate how hard Fusion is working for them. I highly recommend sending updates to objects for visibility. So many customers who have Fusion tell me our users don’t even know that we have Fusion. And it’s because they’re not really transparent in kind of communicating inside of Workfront what Fusion is actually doing.

So let’s save this as a reference and we’re going to start the demo in Fusion. So we’re going to see how far we get. And if we’re running out of time, I’m going to do what I did last time and open it up to the audience to kind of help me pick what to focus on. Okay, finally, we’re getting there. So for each of these, I wanted to break down each automation by the problem they’re aiming to solve, what Workfront looks like before we run the automation, and then explain what Fusion is doing and show the effect in Workfront. So we’re going to start here with scenario number two. So for this one, our first one, it’s copy new notes and replies from a source issue or request, no matter your terminology, to an already converted project. So we have a problem in Workfront. If an issue is converted to a project or a task, doesn’t matter, an update, which we call a note object, on that issue does not flow to that converted object. The same applies for replies. So what we’re going to go look for in Workfront is an issue converted to a project or a task. In our case, it’s a project. And we’re going to add an update to it. That’s our condition. What Fusion is going to do is it’s going to take that update, that note that we’re going to write, and any replies to the converted object so the project users are aware of the update. Okay, let’s go right into Workfront. So I have this issue.

And if I go down here into my issue details, you can see it has a resolving project. So here’s what we’re going to do. Very simply, we’re going to type in here, I am an update.

And then we’re going to add a reply.

I am a reply. As we know, this is just living here on the issue. It’s not on the project at all. They’re not talking to each other in that way. That’s why we’re going to go over to Fusion. And we’re going to choose a template.

And this is the one I want. And if you haven’t used this template experience, what it’s going to do is it’s going to have a wizard that’s going to kind of walk us through the things that we need to change in here. And some of the other configurations are hidden. So it’s really focusing you at this moment on what needs to be changed. So the first thing I have to do is choose my org. Pardon me, I have a lot going on here. And then my team that I want this to be associated with. And now the wizard is bringing me through what I need to change. So the first thing typically will be changing the connection to something that makes sense for you. Then for this specific module, we’re going to be making sure in our filter that we are looking at the opt task, which is the issue. And we’re making sure that it has a resolving object. That’s what all of this means. Now you can add to this filter, like maybe you only want this to go to a specific or be actioned in a specific project or portfolio. So we have a little bit of text up here to kind of walk you through that process. So for this one, that’s all I needed for this module. I hit continue. And this is just asking me to choose where to start, which we’ll deal with later anyway.

Now what we’re going to do here is we are going to talk about some variables. Now these are going to be used later. But what I need to do here in this first variable is I have to choose what my resolving object type is. Is it a project or is it a task? And for me, I don’t have to change this. I’m working with my resolving object as a project. No problem there. The next variable is asking, do you in your instance call an issue an issue or a request? And so for me, it doesn’t really matter. I’m not going to change this, but I’m just going to leave this as issue. So that’s the whole purpose of this because we’re going to use this information later.

Okay, next for this, all I have to do is make sure my connection is good, make sure my connection is good. And I’ll explain what’s happening in these modules after we set everything up. That’s my connection there. And so this is the actual update text that we’re going to send. And we’ve gone up the top route of this. And this is a not a reply. This is tiny, you can probably not see it at all. But this top route is just for the regular old updates. And this is what we’re going to put as the update. So we’re going to say the owner, the person that typed it in the update, has created a note on the source. And remember, we’re saying, do you call it an issue or request in your environment? That’s what this variable is. And then we throw in that note text down here. So that’s all this means. I don’t want to change it. I’m going to hit Continue.

Down here, my connection. Sure. Great. Love it.

Nothing to change there. And then here is where I can change the update text for the reply, which is quite different. If you wanted to change anything in there, you would go into note text here. The rest of this kind of has to stay the same. Because what this is doing is this is making sure that the reply is associated with the correct parent note. Because we have to know where to put the reply. That kind of happened a module before this that this didn’t show. But I’ll show it to you. Let’s hit Continue. And now our scenario is ready to go. This is ready to use. So what we’re going to do, we already have our conditions set inside of Workfront. So we’re going to run this and I’ll kind of give you a few details about what this is doing. So I like to choose where to start. So I’m manually choosing which notes I want Fusion to work with. And this is fabulous for demoing. But this is also fabulous to know for testing. So you can grab on to specific records and kind of have the automation deal with just those. You can do lots of testing in this way. So we know that I put in two different notes. The first one was just the plain old note and the second one was the reply. So I want to start from here because I want to grab both. I’m going to hit OK. I’m going to run it. Off it goes. Okay, so I had the first go up the top route where we went using this module, went and it updated the text on that project here with the regular old note. Bottom route is our reply went down here. But first, what it had to do is it had to read and we didn’t actually get to see this because this didn’t need to be set up. We just needed to put in the connection. But this is making sure that it understands what the parent note is. So it can associate that reply properly when it gets down over here.

Okay, all of that said, let’s go over to Workfront. And so here’s our issue. And let’s move from our issue over into our resolving project to see how that looks. So here it is.

We have Jenn Desmond has created a note on the source issue. I am an update. And then there’s my reply. Jenn Desmond replied in the source issue. I’m a reply. Of course, you could change how this looks. You could add some HTML, put some bold, put some italics. You could do all of those things. But the template right out of the box, that’s what it does. Okay, so that takes care of the first one.

And let’s go back over to our slides to talk about the next one.

Okay, so this scenario is called Task Update Incompletion if Approved on Proof Decision. So we have a problem, another problem. In proof on a task, if that task, if that proof is on a task and the proof is approved, the task remains in an incomplete status. A lot of customers have said, you know, we really wish that if an approval was approved fully in a proof on a task, we really want that task to be completed. So for us, our conditions and work front here in order for us to test this will be an approved proof on a task. And then what Fusion is going to do is it’s going to go ahead and complete that task. Then it’s going to send an update.

I feel like I’m going to say the phrase deceptively simple a lot here, but really, that’s all we’re asking for. Okay, so let’s go over to work front and we’re going to take a look at our conditions here. Now, because I learned the last time, I set up some things in case I become impatient and don’t want to wait for the data to process. But I feel like for today, because of the Artemis II, really, really, really want to approve this rocket ship. So that’s what we’re going to do. I’m going to go into this proofing workflow and remember, we’re going to approve this. So I’m just going to come in here. I could do approval changes. I’m going to do approved. Okay, so that’s approved. Now, remember that this proof is sitting on this task and this task is at 0% complete. So our goal here is for this approval right here to close this task and make it 100% complete.

So let’s go over here and this is one that I have prepared so that we don’t have to wait.

Okay, so I didn’t want to have to build this one from a template. It would have taken a little bit too much time. So let me walk you through while the data is processing, I’m going to walk you through what exactly is happening here. So in our first module, we’re watching our proof decisions. And so remember, this is on the proof API. We talked about APIs and the different APIs that we have in part one, but this is the proof API, not the work front API. So things are a little bit different over here. And there isn’t really a filter for me to say that I only want approved decisions. So we have to have a filter here that is looking for just new decisions. And then after that, we’re going to make sure that this is an overall decision. So in our filter, we don’t want anything that’s pending. We’re looking for approvals. That’s our goal here.

Then we have to do a little bit of magic here in our set multiple variables. So what we need to do here, and this is a really, really smart way of setting this up. What we know is that in module one, we’re getting back some details about the proof activity, but it’s being returned as approved by GenDesmond. That’s what we’re going to see. And so that first variable is splitting that phrase. And so we need to be able to get the proof decision that approved in the approved by GenDesmond so we can use it later. Then the second part of that phrase approved by GenDesmond is me. It’s the decision by. So what we’re doing is we’re using these two variables to split that phrase. So we get the proof decision and we get the decision by, and we’re using the word by to split that up for us. Makes it really, really easy. There are other ways to do this. You could have more modules that are getting this data in different ways, but this is actually a really smart way of reducing the modules that you would need to get this information in another way. We’re getting the information, just not in a way that we can use later. And so that’s the purpose of this.

OK, so then after that, what we’re doing is we’re just getting some more info about the project that we’re going to use later. So here we’re getting the user ID.

Then we have a router and we’re starting to go and process the data in different ways. So up here, we’re only looking at proof decisions that are approved. And then we’re making sure that the task is not complete. And if it’s not, we’re going to complete it. And then remember, we’re going to send an update because we love to send updates. We love that. Changes required as a decision is going to take a different path. It’s going to go this way and it’s going to create an update and notify. It’s not going to close the task. This was a choice. Now, of course, you could always change that. Then we have a bottom router just for any other decision, which is going to create an update. So the TLDR on this one is we’re only going to complete the task if the decision is approved on this one. OK, I have blabbed long enough such that I know that this is going to work now. Choose where to start and do it manually.

And we’re going to see, huh, there it is. OK, perfect. Love it.

We’re going to do both of these decisions. One of these is the decision overall and one of them is mine. We’re going to run this and I’m going to open this up to kind of show you.

So I’m getting two bundles here. And so the first one is an action because remember, this is watching all proof activity. And so it’s separating out these actions of the proof status has been changed. And then the second action is the new decision. So there’s that phrase approved by Jen Desmond that we then, using this set decision, we’re parsing that out. We’re splitting it out. We’re separating it so we can take this approved as our proof decision and know who it was approved by and use all of that data later to send the update, complete the task, do all of those things. OK, so let’s go into Workfront.

So now we’re back in Workfront. What we know is that this got approved and all we were asking it to do and let me refresh. We were asking it to complete.

There’s our percent complete is now at 100. Task is done. And then we wanted to send an update. I can’t remember if we were sending in here. Yep, there it is. OK.

This is the update that we sent. Again, these can all be changed. They’re coming out a certain way in the template, but you can change it. There’s a lot going on here. We give the proof with the number and the document version and its ID. And then we say what project it is and what task it is. And then it says has been approved by Jen Desmond on the date. And then the task has been marked as complete. Again, deceptively some simple does a lot of things, but there is a ton of flexibility for you to be able to change this however you want to.

OK. That one’s all set. Let’s move on to the next one.

All right, we’re looking at a tailored notification based on a change. So this one we are going to start from a template. Our problem is that Workfront doesn’t send customized notifications when fields change. Yes, it doesn’t. We wish it would, but Fusion can handle it. So what we’re going to do is we’re going to set up a task status that has changed. That’s what we’re going to do. And then what Fusion is going to do, it’s just going to send a notification to the project owner.

Deceptively simple. OK, let’s go back into Fusion. Go back to the templates.

And this is a tailored. Here it is.

OK, in we go. And now we’re back to setting this up from a template. So I’m going to come through and choose customer success again. And my team is Workfront.

And it’s only going to show me the things I need to fill in. So there’s my connection, which is good. And I want status.

OK.

Here we go.

All right, so what we’re doing in this set multiple variables is we’re going to put my domain in here, and this is only used because it’s going to put it in the update to create a URL, which is actually really cool. So I’m going to set that. And then the second one is just pulling the task assignee. And if it’s not, it’s going to go to the project owner. So that’s really all that saying.

OK.

And this is where I get to change the update text, which I actually will want to do, but I’m not going to do it quite yet. We’ll talk about that in a little bit so I can just hit continue. This is ready to go. What I forgot to do is go and work front first and kind of come in here and play around with my status so my status is blocked. Now we’re going to push that back to new.

The use case is here. Any time that this status on a task changes to blocked, what we want to do is we want to send an update to the project. That’s the goal here. So let me do that again. I’m going to switch this to blocked.

Perfect. Now the way that this is set up is I am looking at the status. I put in here status is what we’re looking for, but I didn’t actually stipulate that I only care about things that go to a blocked status. So that’s where we’re going to take this template and we’re going to start to make some changes to it. So I’m going to put a filter here. I’m going to call it blocked. And I want my condition to be new text value is equal to and I’m going to use the status code of blocked that I just showed you, which is going to be p, k, b. So now only those are going to come through. I don’t care if a task goes from a new status to a complete status to an on hold status. None of those I want to care about. I only want to care about things that are blocked. And then there’s one more thing I want to do here. I’m going to come down into this update and I don’t really love.

Yeah, I don’t really love this piece right here. I want to know what the before and after was like, what was the task changed from before it was blocked? So I’ve copy and paste this in instead. So now I’m going to say the task status has changed from old text value to new text value because that’s what I personally care about. Right.

Let’s run this thing. But I want to choose.

And now I can see that, yeah, right there, there’s my p, k, b status.

So now in my results, I’m only going to affect this one status change that I made. Let’s go take a look.

There’s my blocked. Now you won’t see anything here because I’m putting this on the project. But if I go to this project and look at the updates and here we go. Now it has gone to the task owner, which is Kermit. And now it’s saying that this task in this project has changed. You should be aware of it changed from new to p, k, b. And then this is where we put the domain in. It created this nice little URL here that you can kind of click on and get back to that specific task. So lots of examples here, you know, to kind of show you all the different ways that you can change these templates and inside of all of these templates are different ways to do a lot of different things. So don’t just think of them as, you know, out of the box automations. It’s learning different ways to handle different use cases and things that you need to do inside of Fusion. OK, so ready for the next one.

All right, scenario number six, project creation from CSV.

So here’s our problem. Sometimes you want to create projects in an automagical way without using a kickstart. Kickstarts definitely have their place, but the love can run out after a while and there’s a different way to do it and it’s Fusion. The conditions and work front, I actually have a CSV uploaded as a document and work front, so you’re kind of keeping the information all inside there.

What Fusion does is Fusion is going to create a new project for each row in the CSV in a specified portfolio, template, etc. that you specify.

This is a super powerful template in the sense that you’ll be able to understand how to do other things with it. You can upload issues, portfolios, programs. There’s just a little bit of remapping that you have to do and then you can use this for a lot of different things. OK, let’s go into work front. We’re going to go over here to project upload.

And so all we’re going to do here, this is a document. This document is living on this project and this is where the information is living that we’re going to use. We’re going to give it to Fusion to create new projects for us. So let’s take a look at this document.

It’s just a CSV. It’s nothing exciting, but what I’m able to put in here is the name of the project, what status it is, what portfolio I want it to go in, my plan start date, and my template. And you can go pretty far with this. You can add lots and lots of fields to this as long as you map it properly. And I’ll show you all about that. You’re good to go. No, I don’t want to save. Leave me alone. OK.

So let’s get into Fusion.

OK, so from here Fusion is going to get that document. That’s all it’s going to do. This was the ID of the document that I just showed you.

And then it’s going to parse it. And this is really simple. All you have to do is say how many columns are there. It contains headers, comma delimited, and then it’s just mapping. And again, when you’re using this in the template, it has instructions to tell you how to prepare that CSV and what you need to do there. But I’ve already prepared all of that so you don’t have to watch me do it again. Then again, do you mind just resharing the CSV folks in the chat saying like the CSV didn’t appear, they didn’t see Excel, they didn’t see your file. Show that again. Yeah, it’s probably because it’s on my window. I’m sharing the window, not a screen.

How can I show? Yeah. Do you want me to reshare? Yeah, maybe just for a second. A few folks in the chat had asked if you could just reshare somehow. Yeah, let’s do that. Let’s do that.

OK, let me reshare my whole screen.

And then let’s go back and preview this.

Although it’s a bit of a lie, I need to be on V2. I don’t know why it keeps doing that.

All right, let’s show this.

OK, so here’s the CSV. So this is really simple. It’s just a few columns. They have headers and the headers we’re going to use later, that’s how we do our mapping. And so we have project name, status, portfolio, plan start date, template. There is a gotcha when we’re talking about dates. They have to be in a specific format and that format is actually documented in the template itself, so you will see what that format is. It actually needs to be, it can’t be 26 for the year, it has to be 2026 or it will spit that right out. It doesn’t like it, but again, that’s built into the template in terms of the instructions.

So there’s the CSV.

OK, now I’m just going to stop sharing and reshare.

From my window.

Why am I not seeing the right window? There it is. Perfect.

So John, a quick question while you’re getting going. Do you have to always download for work run first a CSV file or could you just start your own CSV file? I’m guessing it’s a little bit like kickstart, but it’s going to be a lot easier if you download it because it’s going to be formatted in such the way it needs to be. I wasn’t sure if you had thoughts on that. That’s a really good point. So. In the template there is no CSV. You’re going to prepare the CSV yourself and then you upload it yourself into work front. So it’s not like we’re giving you a CSV like kind of like we do with kickstarts. You’re creating it right from scratch and then uploading it to a location in your work front. Does that make sense? Yes, yeah, thank you. Perfect. Alright, so. Showed you the file, showed you the CSV. Let’s go over here and I think I showed you almost all of this. So let’s actually go over here. Let me continue. This module, module 3, is where you’re going to actually map everything because this is the creation of those projects. So what we’ll do, and this is really simple, is all you need to do is select the fields to map. And when you use the template, this is all done for you.

But. Project name is project name, plan start dates plan. I mean, it’s it’s just a one to one mapping. It’s really simple. So if you needed to change this for something else, change the record type to, I don’t know, maybe you want to upload a bunch of issues or something. You would just remap everything based off of how your CSV is prepared.

And then, like we love to do, we’re just sending an update about these new projects. So every single update on these new projects is going to say the file name that they originated from in case somebody needed to go look at that file name and say, you know. What file was this prepared from? You know what date all that stuff there it is. It lives. So let’s run it. Let’s do the thing. Now this is going to take a little bit of time because we’re actually creating things inside of Workfront, so we’ll kind of let this. Let this do a little thinking and we’ll go over to Workfront. And if I look at this portfolio, you’ll start to see these projects come in.

Just refresh this a little bit.

OK, and here are our projects that are coming in. We’ve got Fusion Decoded 2 and then 1. And so there’s that portfolio that I wanted them to be called.

There’s the status I wanted them to begin. Those are the planned start dates I wanted, the template I wanted. And you can see the status update. So a new project has been added, blah, blah, blah, blah, blah. And that’s how that works. Again, this is a really, really powerful thing. I think that over time you’re going to find lots and lots of ways to have some fun with this one.

OK, let’s move on.

To our final. I think we’re going to have time for questions, which is awesome. OK, so our final one is to bulk append to project name with convention. So you’ve got a problem. You’re rolling out a new naming convention for projects and you need to rename quite a few. That’s why this is a bulk.

Or you have a naming convention built into another scenario, but sometimes users rename anyway and you want to use this scenario as a batch update for governance. That’s exactly how I would use it. Let’s be honest.

The conditions in Workfront, we’re just going to have a bunch of projects you want to rename. That’s really it. And then Fusion is going to come in there. It’s going to rename those projects in your desired portfolio with your desired convention.

OK, let’s go in to Workfront.

So I have these three projects. Bad name one, two and three. I really don’t love that a lot. I want to change those. I have a convention for it. I really wish people would follow it. Oh, I don’t need this. It’s OK.

OK, so.

Let’s fix some names.

First thing we’re going to do. I made a little bit of a change to this based off of the template. The template is going to find projects in a specific portfolio. I wanted it to be program, so that’s the first change that I made there. It’s OK.

The next is the module that’s actually going to change the project names. Now, I don’t actually love this naming convention. It’s a little bit much for me. And in fact, as you saw, my names of my projects were literally bad name. Like their names that I don’t want them to have. So I’m going to change this a little bit. I’m going to get rid of everything in front of this format date. Like I don’t really want that.

So we’re going to just delete this goodbye. But I do want to keep the format date. I like that.

Then, as I’m looking at this, I’m getting this name and that’s the original name right there coming from the first module. And I really don’t want that. So I’m just going to delete it. So I’m just showing you how I’m changing up the way that we’re going to rename these projects to kind of suit my needs.

OK. And then the third, like we love to do here, is to send an update about that renaming. So that’s what I’ve got going on here.

Right. Let’s run this.

OK. All three have been changed.

Let’s reload.

OK. And here’s my convention, which was entry date.

I believe it was entered by and then it was portfolio and then the reference ID. So you can see how that happened. Easy peasy. This one, again, deceptively easy. Big impact.

Right. Back into the slides. We’re almost done. Ready for questions. There we are. Ready for questions.

Awesome. Thank you, Jen.

Rauwatesh, I know you have your hand up.

Yeah, thank you very much for the presentation. That was awesome.

And I have a small question here. I see you have access to the AI assistant in your fusion scenario right on top when you’re sharing that.

Could you, for the sake of sharing how easy it is using AI assistant to help developers within fusion develop scenarios, could you, for that particular purpose, create a short scenario with modules using the help of AI assistant so that those who haven’t used it when developing scenarios by colluding modules, bringing them together can now take a peek at how that looks? I’m going to divert to Sam. Sam, for AI in fusion today, what do we have available? I had thought we only had the ability to check documentation. We have more? No, no, we don’t. So scenario generation is not currently a capability there. I think you’ll see something in that roadmap in the near future. So probably at the next opportunity, quarterly, as we identify the next quarters roadmap, watch that. I think you’ll see something there. There will likely be a fusion diagnose agent and optimizer agent before there’s a scenario generation one. We’re going to, we’re prioritizing some governance use cases first for that.

Okay. And a follow up question on that one is we have the Adobe Gen AI agreement signed. And as a result of that, now the developers are seeing AI assistant show up. So the question from them was, what’s the purpose of, you know, just seeing it when we can’t utilize it toward building scenarios. So why is it showing up as soon as we have our Adobe Gen AI agreement signed? It’s just occupying space on the right hand side of the development screen.

What you’re most likely seeing is a setting that’s turned on both when you’re interacting with Workfront AI assistants and with fusion assistance. So same setting as putting on there, it’s limited and can search experience leak, but the existence is not intended to imply it can be used for scenario generation.

Is there a way we can hide that? Because typically if the, that feature is available to kind of hide it, then it gives us more estate to go look into scenarios when expanding, if we have lots of modules involved.

Yeah, possibly. Can you give me a screenshot of that? Yeah. It seems a little unusual there, but we can explore whether or not that can be removed for you.

Where do I send it to? If you send it to this, I was gonna say if you either post it in the chat or if you send it to the scale inbox, we’ll make sure Sam gets that. Yeah. Please include the email. That’d be the best way to get back to you.

Awesome. Thank you. Jonah? Thanks. Hi there. Thanks for the presentation. Just real quick, when we’re creating objects using a CSV file, I want to do that same thing for requests with attached custom forms, especially with mandatory fields. Do I have to map out, do those mandatory fields actually need to be filled out or can I leave those blank when Fusion creates it? Because my people won’t know by the time they generate the issue.

Yeah, that’s really interesting. I mean, honestly, for me, what I would do is I would upload your issues with the CSV and then have another module to go in and add those custom forms that you want added on to those issues. That’s what I would do because then they’re going to be blank, right? Right.

Okay. Now, I mean, that works because right now, one of our users here also said that they have sort of like a waterfall selection with regards to project types. And yeah, we have a similar setup. And so, I mean, but at the same time, we just went through planning. We just wanted to get these issues in there, but they wouldn’t be able to fill out all the fields yet. But like you said, maybe. Yeah.

And then, yes, use the alert, use the notification module to alert them, hey, this issue is in we just fill that, we just attach the forms, please fill them out just like you would a regular request. Okay, cool. Thank you. You’re welcome. I think, Michaela, I don’t know if you raised your hand to help answer that question because you also posted in the chat.

Yes, I did. So we do project duplication for existing work that we have in the system year after year, and they don’t fill out the mandatory field. So we just tell it, duplicate the project using a concatenated field for the portfolio and collection, start date, and then I think like project type. So that’s all it takes. And then it creates the shell of the project. Not all of the mandatory fields are filled out.

So I do know that works. But I’ve never tried it from a CSV. We used to do kickstarts. One of our colleagues actually transitioned to Workfront because of kickstarts. So we’ve only done it through a duplication process, and I would like to try it through the CSV process.

Awesome.

Nick, you too? Me too. Yeah. So I had a question. Last year we had a discussion that we’ll be creating in Fusion a promotional manager, where we can move the delta changes. If I have a scenario in a lower environment, say, for example, in development environment, and now I need to move only the delta changes in production environment because the same scenario exists in production, but only a delta changes. Fusion is on top of it. We have made it in the dev environment, and now I want to move it to the production environment. Then in such cases, I don’t want to download the whole blueprint and upload the blueprint and then change the connection, and it is a very tedious job. And we have around 100, 200 scenarios, and every release which happens in two months, we have to move a lot of scenario delta changes. And I understood, like last year we had a discussion with Adobe, and they said that they are going to create just like an environment promotion Workfront. In Fusion also package deployments and all those things will be available. Just wanted to know when are you planning to release that? The first step on that is the APIs for cloning scenarios. Those APIs will be released after this quarter. So for planning purposes, I would mark June in your calendar. That will allow you to do an API based cloning, and then other features to support environment promotion will come in future quarters.

OK, and one more question. As of now, for all the environment related IDs, say for example, IDs or links, webhook URLs, all those things we are storing as of today in data store so that if we are moving to a new environment, we can use the data store. But I could see that in other SaaS tools we have for environment related variables, we have another table. Are we looking such feature to be released in Fusion as well? Where in environment related things we can store it in a table and we can use environment promotion there as well, extend it.

Data structures and data stores are team based and there’s no immediate change to that. What I would recommend if you want something that’s available across multiple instances is to find another data store. So an option you might think of is Workfront planning. If you have that, there might be spreadsheet options. We even have people using building app builder data store for that.

Yeah, app builder again, where we have to store and even in a Workfront planning, but in Fusion itself, we can extend the variables in data store and data structures are one kind of table and has a limitation. A number of data stores we can create in a team have a limitation. But is there any table beyond data structure or data store where we can store only the environment specific variables? The only data store is that data store. There’s not another one.

No, but in future are we thinking to have such a feature in Fusion is what I was thinking. In environment promotion which are going to release in future, right? After this quarter, maybe. In that are we thinking of creating an environment specific environment variable specific table as well is what I wanted to know.

There may be some things on there, but we don’t have a specific, I understand the need, but we don’t have any specific road map that would fulfill that exact request. But what I’d recommend is in the immediate future is find a data store that’s API accessible and that would fit your needs really well. Okay, thank you. And you’re welcome.

Awesome, Jason.

Okay, maybe Jason doesn’t have his question anymore.

Harsh.

Oh, sorry, I was muted.

Okay, hey, Jason.

Jason, you’re second? Should I go ahead? Yeah. Should I go ahead? Okay, I was going to get back in line. I just had a quick question regarding copying notes from the task to the project that was shown there. You mentioned putting in HTML and formatting. Is that a standard HTML format in that case or is that another draft JS formatting? Oh, you could just use plain old HTML. That would be wonderful. It works great. That would be great.

I’m trying to remember which template I have. I do have, it’s one of the proof templates. I have some HTML buried in a couple of modules. I wish I could show it to you, but it’ll take me too long to find it. So yeah, it’s possible. It’s buried in some of the templates. That’s what I’ll say. Yeah, so not a problem. I like the support for plain HTML. It comes quick. The draft is fine. It works fine. But knowing that plain HTML can be used there is a little quicker for me. Yeah, got to work. Thank you.

All right. I think I’m going to run through the closing updates real quick and then we can take whatever time we have left. So if you go to the next slide for me.

Awesome. Wanted to call out Adobe Summit. Lots of announcements, good stuff happening there. If you’re not able to attend in person, it is free to register for the online version. Some of the sessions you’ll get later, but you’ll have live access to the keynotes and some of the other sessions. So definitely recommend signing up for that.

Like I said, lots of announcements and things happening there. So it’s good to, you can always sign up and review those sessions later. I’m sure there’s some great sessions on Fusion, things like that.

If you go to the next slide, I think we have events.

Because of Summit, we’re a little lighter this month on events, but we do have the second quarter release webinar. There’s a lot of stuff in this release. Know that it’s going to go really fast, so you might want to start looking over those notes today if you haven’t yet. But that is April 9th. We just talked about Summit. That’s later this month. And then we have Kat Shondek doing a session.

She’s with Penn State. She’s going to do a session on how she manages a whole Workfront instance, all the project management, all this stuff all by herself. She’s got a lot of really cool use cases. I love seeing stuff like that. Great inspiration to see how other people are using Workfront to do interesting things. So if you ever want to speak, let us know. You can reach out to us at csatscaleatadobe.com. We’d love for you to share your story or interesting things that you’re doing. We’d be happy to have you. So the next slide, I want to call out, we have a survey. This gives us feedback on this session. I’m going to make sure to share all of that with Jen. So please leave any notes there for us. We would love that. Cynthia did pop that in the chat. So if you could take a few minutes to do that, we would greatly appreciate it. So with that, oh, I’ll call out. We don’t have to go to the slide, but at the end of the deck that you’re going to get a copy of, there is a slide of resources.

So you’ll get that as well. And there it is.

So lots of great stuff there if you’re getting started on your Fusion journey. Let’s see if we can get another question or two in. Harsh? So hi. A great presentation that I have, that we have. But the issue is that we are facing right now that whenever we are changing the status on the work front and with the help of Fusion, we are updating certain fields with the dates. So that particular status is hitting the Fusion scenarios twice, thrice.

So is there is any way where we can control it, that particular instance that it could only hit the scenarios only once? Because that status that we have, it is a custom status, which is mapped with the, I can say, inbuilt status that we have in work front. So is there is any way where we can stop that so that it can hit the scenarios once and it can update that particular field once only? There are a lot of reasons why that can happen.

Why don’t you send an email to the CS, is CS at scale? Yes. Yeah, send an email over there and we’ll look into it and we’ll deal with it. Because there’s just so many ways that that could actually happen that I want to make sure that I’m giving you the right instructions on exactly what’s happening there because it’s a lot.

Yeah.

OK, so I will share the email because we are building many scenarios on the basis of status and now we are at a point that the scenarios are hitting again and again in a continuous loop. Yeah, you want to fix that.

All right, Prasanna? Yeah, one question, one challenge we are having is like we have a lower environment. Within Fusion, we have created two teams, one for the sandbox and one for the production.

The one challenge which we have is like in typical application development or anything, right, we will have a CI CD where we have a promotion of code from lower environment to higher environment. This will be an automated CI CD pipeline. Is there any such process which can be introduced in Fusion so that this deployment, I mean blueprints in production environment, can it be automated? Because if we are working around probably around 10 to 15 scenarios and we have all the modification and then if you do manual deployment, right, it takes a lot of time and also migrating data stores and establishing the connections and all those stuff.

Yeah, it’s a challenge actually.

Yeah, Prasanna, that is similar to a question we had a few minutes ago and also in the thread related to environment promotion and the APIs. Currently, you have to manually clone scenarios across teams and align teams with your pre-production environment. The API to automate that cloning is what we are planning on releasing at the end of this quarter and so for planning purposes, you can expect that automation capability to be available around June timeframe.

Okay, so that will be integrated with some Azure DevOps or some other, can be integrated with that with like a regular pipeline? It will be an API that will perform the same actions that you do when you clone manually in the system and how you implement that in the CI CD would really be up to you, but the assumption there is an API that can perform those actions would work with whichever pipeline you configured.

Yeah, definitely look for some more guidance to that. You may have noticed it’s a popular topic.

Thank you so much. Yeah, for sure.

Jen, do you still have some time or do we need to wrap? I want to make sure I’m mindful of your schedule.

I do. I don’t know about Sam.

Sam’s a busy person. My next call was starting, but please, if you pick up any questions that I can help product and let me know afterwards and we’ll follow up. And thank you so much. Jen really, really do appreciate you do fantastic work and you are definitely one of the two template leaders you and you and are the ones making these happen for us. So thank you so much.

Yes, thank you. Take care. Thanks, Sam. You too.

All right, Sumit.

Yeah. Hi, Jen. Hi. It was a great session. Thanks for so much information.

I had two questions, actually. So one of the scenario we were building in the past is that had work front integration with the dam.

So we were creating a… So what we did is we created a link folder and we were trying to upload an asset to the link folder through Fusion. But I think we tried a lot, but we were not somehow successful there.

So that is one thing. Is there any module that supports uploading an asset to a link folder in a work front? That is one of my questions. And another one is that even now we are doing plenty of things where suppose we are creating updating the content fragments in AM sites. So I understand there is no direct module or direct connection to the AM sites. We have to go through the APIs. So what I was wondering if that is in future, can we have any such releases where we will have modules related to the AM sites? So the second one I think we’ll take back to Sam just as a piece of feedback. But are you aware of any modules, Jen, for uploading documents? Have you… Okay, it’s sounding like you’re describing what the native integration can do. So we do have a native integration with work front over to AM assets. Have you explored that as an option because that’s kind of one of its hallmark features? Yeah, we have tried to explore that, but somehow that was also not working. The assets were not getting uploaded properly. The folder we intended to upload assets, it was not going to, since it was a link folder. It was moving into the parent folder. So we had a hierarchy of folders. So it was moving somehow into the parent folder that didn’t work actually.

That actually sounds like a support ticket to me.

And it depends on how long ago you tried, because I know they just revamped the integration last fall. So if you tried it before that, it might be worth trying again just to see if it works a little bit better now. But I agree with Jen, maybe that’s a support ticket. And you’re not talking about the enhanced connector, correct? Yeah. Yeah, you’re talking about the native integration. Yeah, I would check again. And if it doesn’t work, I would absolutely put in a support ticket for that, for sure.

And then if that doesn’t suit your needs, then you can email the same email, the cs at scale email, and reach out to me and we can talk about what to do after that.

Sure, sure. Thank you. All right, Michaela, round us out.

All right, hopefully it’ll be simple.

So I’m going to go ahead and open up the CSV and scenario number six. Just want to confirm that I would set up the CSV, pull the IDs from Workfront, put them in the CSV, and then upload that into the scenario. Yes, and what you’ll see, like when you go and you start to use that template, all of the instructions are in the wizard for that. So even when you upload the document up into Workfront, you’re going to get two different IDs, and it’s going to tell you to take the first ID to make sure that it’s going to ingest the correct document. It’s all the info is there, but if you run into some trouble, head on into that email and I’ll help you out. Okay, I appreciate that. Thank you. I’m going to try to test it this week.

Awesome. Well, thank you, Jen. So appreciate your expertise and taking the time to just kindly walk us through these scenarios and how we can use them in our day-to-day life. So thank you for that. If you’re still on, you’ll get a copy of the recording, the slides, and some notes later today. So just give us some time to get that all compiled and we’ll get that out to you. But thank you for your time and we’ll see you at the next one. Thanks so much, everybody.

Take care.

Bye.