Fusion Decoded: What It Is and Why Every Org Can Use It

Transcript

All right, let’s go ahead and get started. Real quick, I’m Leslie Spear. I’m part of the Scale team. I also have Cynthia here with me today. We’re gonna be hanging out in the chat, trying to answer or at least gather questions. Jen is our expert. We have maybe one other person joining us to help answer some questions, hopefully. If not, we’ll gather those and do our best to answer those later, but we’re really, really happy you’re here. We have Jen with us today who is going to share all about Fusion, why you want it, all the good things it can do for you, what that looks like. And real quick, we will share a copy of the recording and the deck with you after the fact. So feel free to take notes, but know that you’re also gonna get these slides and a copy of this recording. So anything she demos, you’ll get to see that in replay if needed at a later date. So, oh, yep, there’s Sam in the chat. So he’s gonna be helping us answer some questions there. Thanks, Sam. So glad you’re here.

All right, with that, Jen.

Yeah. Thank you, Jen.

Thank you, Sam.

Sam is my parachute, I guess you could say here because he is the true expert.

Yes, yay, Sam. Okay, let’s get started. Enough of me being thankful. I love to be thankful, but I’m taking a little over the edge here. Okay, hello, everyone. I’m Jen Desmond and I’ve been a customer success architect for Workfront with Adobe for four years now. I can’t even believe it’s been four years. Here we are. I was previously a customer and one of the reasons I wanted to make the leap over to Adobe was so that I could learn Fusion. Yep, that’s the reason. As a customer, I self implemented.

I did my own really awesome little journey there, which basically means I learned a lot about Workfront the hard way, but all of those experiences have stuck, given me the empathy I have for customers today. And it’s important to note that I did not have any direct API or automation experience before I joined Adobe. So as a customer, I did oversee the automations and integrations we had, but they weren’t with Fusion and I didn’t develop or maintain any of them myself. Why am I telling you this? I think it’s really important to understand that all of the Fusion knowledge I’ve gained is from scratch and only from the time since I joined Adobe. And I understand my privilege here in being surrounded by so many Fusion experts at my fingertips, but I’m really stubborn and I’ve tried to learn Fusion as much on my own as possible so I can see it through your eyes. And again, we also have Sam Taylor here, who is our Senior Product Manager over Fusion. He’s gonna be hanging out in the chat. He’s gonna join us in the Q&A. He can tell me if I’m wrong. Come off mute, tell me I’m wrong. If I’m wrong, Sam, use my parachute here. All right, let’s move on. Okay, so today we’re gonna cover what feels like a simple set of topics, which are, what is Fusion? What can it do? How do scenarios work? And then we’re gonna get right into Fusion for a live demo and then wrap it up with how to get started in Fusion. And then finally, Q&A. My goal here, demystify Fusion for you so you can not only understand it yourselves, but also frame it for anyone who asks. I want you to see what it can do firsthand and inspire you to think how it could fit into your organization, and if it does already, how you can utilize it even more. So my intention is to speak to Fusion beginners, but my hope is that even you Fusion veterans, and I know some of you are here, I want you to gain a different perspective on what you already know. And with that, let’s go. Okay, so what is Fusion? So maybe you’ve seen this slide before, but we’re gonna start here with what we usually say about Fusion, because I wanna build on that for your understanding. So Fusion is a low-code I-PASS automation integration tool, replacing the need to build a custom API integration with code only. The Fusion interface makes designing automations and integrations easy and fun, easy enough for me with no experience working with APIs.

So of course, once you begin using Fusion, you will need to learn how to tell Fusion what to do using the API for the system you’re working with, and that’s definitely technical, but the barrier to entry is so much lower. The scenario builder is intuitive and takes away the need to write each and every line of code yourself. So Fusion also securely handles all the connections to the systems you’re working with, whether that’s Workfront or something else, and you can reuse those connections as you build more scenarios. It also contains within it all of the history of what Fusion has performed and ways to mitigate and surface execution errors.

All right, so let’s mark this up a bit. So I-PASS is just a way of saying an integration platform as a service, which Fusion is, and now here’s a really important distinction that I wanna talk about. So automations instruct Fusion to do things for us, while integrations connect systems together. Fusion does both of those things. And let’s talk about this design experience here in pink. Fusion is a modular UI. There’s less code, there’s still a little bit of code, and it’s more visual in its setup experience. You’re not just writing blocks and blocks and blocks of code.

Working with APIs is easier. We’re gonna talk about that the entire time. We’re gonna talk. So I won’t go into that here.

Processes automation securely and reliably. It handles all that authentication stuff and credentials for you. I can’t imagine doing that in code. Fusion just takes care of it.

Okay, so I have a five-year-old who asks me all the time what I do for work, and this is how I describe Fusion as a little robot that I tell what to do and it just does it. So if you’re looking for a statement of value, that’s what the second paragraph is. It’s basically taking the burden off of you and your users so you can all focus on other things. But I think it’s kind of helpful sometimes to frame Fusion in a really, really simple way if you need to explain it to somebody else. Okay, let’s get more specific about what Fusion can do now that you know at the highest level.

So how are customers using it? So customers are using Fusion as a connective tissue to help systems work together in their marketing or otherwise system of record. Just imagine all the applications in your tech stack here with Fusion connecting all of them. Within all of those Lion icons, can be happening inside of Workfront and within the other applications, automations can be happening inside them as well. And so this is a fantastic way of thinking about how Fusion can connect these systems and their data to positively impact so many users from all parts of your business, not just inside of Workfront.

Okay, the most asked question I get is, can Fusion do this or that or this thing? And really, if you wanna know if Fusion can perform an action it starts with that being available in the API you need to interact with. So for Workfront, it uses the REST API for most things, including some proof. And then the REST of proof is handled by the ProofHQ soap API. The Workfront planning API is relatively new and will be added to in the future. And the board’s GraphQL is unpublished because that connector is still in beta for all other applications.

You might find that we have connectors to make working with those APIs so much easier. But if not, you can connect Fusion using an OAuth2 application with an HTTP or SOAP connector. So it’s basically dependent upon that application if they have an open API or not. We’re gonna talk more about that.

So speaking of connectors, remember when I said Fusion makes working with APIs easier? Well, in part that’s due to our extensive library of over 70 connectors for both Adobe and other third-party applications. A connector is a set of modules that makes it easy to tell Fusion to take action on a given API and it handles authentication for you when you choose a connection. For Workfront, there are connectors for Workflow, which are the modules you see on the right there.

Proof, planning, and boards, which align to their separate APIs that I mentioned in the previous slide. And as you can see, there are lots of other Adobe and non-Adobe applications listed in that left-hand screenshot. Even if there isn’t a connector available for the application you want Fusion to work with, you can use the generic connectors as long as the application has an open public API. So to recap what you’re looking at, you’ve got connectors on the left and you’ve got modules on the right and the modules on the right are specifically for Workfront. Also note that if you find that the available modules don’t get to what you need in the API, many connectors include custom API call modules where you can get anything available in the API. I use the custom API module all the time.

Often working with Workfront and also with Proof.

Okay, now you know you can use these modules within a connector to work with data. But Fusion doesn’t just get data, move it around and take action based off of what it finds. It can change and manipulate it in a myriad of ways. Along with the create, read, and update and delete, we call those CRUD operations. There are tools and transformers as modules themselves, so you can use those alone. And they are going to aggregate, iterate, work with variables, parse text, route data now past separate actions, calculate math expressions, utilize data stores. Oh my gosh, work with CSV files, JSON, XML, blah, blah, blah, blah, blah. You can use many of these in a module itself as well through the mapping panel. So as you can see from this, there is so much more available inside of Fusion to work with the data.

Okay, so we’re still trying to answer the question, what can Fusion do? So let’s get even more specific. Reducing manual effort. This is huge, huge, huge. What are users complaining about? They have to do manually. Does it make sense for Fusion to do it for them? Maybe it doesn’t. But here are some of the examples where most of the time it does. So request a project conversion. It’s probably our number one use for Fusion. And yes, in most cases, it makes sense to implement that. Let Fusion do it. Why do people need to do it when Fusion can? Completing a task when another action occurs, like a proof is approved, you’ll see this later. Cleanup. Have some annoying data conditions you want to clean up? While there is a setting, and this is an example, there is a setting for auto-completing projects when they reach 100% completion, but maybe you don’t want to use that setting, or you want to, and now you have a bunch of complete projects that aren’t any complete status.

Let Fusion take care of that. Governance and process compliance. User’s not filling in a required field that comes later in a process, so you can’t make it required in the custom form? Let Fusion send a notification. Have users changing project names to something not in compliance? Let Fusion change it.

Integrations and supplement native integrations. So we have a bunch of native integrations, but sometimes you have additional things that need to happen. Fusion can do that. Also, you saw several slides ago how Fusion was powering the system of record, so dream big on those integrations. Go wild.

Reporting.

Now, Fusion can’t create reports in Workfront per se, but it can move data to other parts of Workfront to aid Workfront’s reporting capabilities.

Data migrations. Fusion can move data from one system to another as a one-time migration or as an ongoing effort, but do note that if you’re looking to move a lot of data out of Workfront for use in a business intelligence tool like Power BI or Tableau, Data Connect is probably a better product for that use because of the level of effort to do it with Data Connect is much lower, but Fusion can handle smaller use cases of ongoing data migration.

Okay, I know I’m kind of beating you all atop the head about this, but finally, let’s talk about the value of Fusion across personas because I’m trying to arm you to think through Fusion’s value and what it can do. So for assignees, again, we’re reducing manual efforts here. Let Fusion convert requests. Make sure the data is there. Complete tasks when something happens, all of which you’ll see later. I’m gonna show you all those things. Reduce context switching. So when you integrate with other systems, it allows users to stay in Workfront and let Fusion move important data in and out of other systems.

People managers, better allocation.

Let Fusion assign tasks for you, and in doing so, you’ll have better visibility into bottlenecks. And my favorite benefit.

Fusion’s enforcement and adherence to process is gonna be a game changer for them, and then it’s gonna bring you cleaner data. You’ll be able to quantify efficiencies, both Fusion and Workfront bring. Integrations are always helpful with cross-org alignment, and Fusion helps you scale as your business grows and changes. Most importantly, Fusion will help your employees focus on work that matters.

Okay, we’re getting closer to the ground here and not just talking about Fusion, but seeing how it works. So how do scenarios work? Oh wait, what is this scenario? One of the benefits of Fusion is it’s easy to use, and dare I say, fun UI. Yes, we have fun here. And it allows you to create a flow for what you wanna do in an interactive and modular way. A scenario is the container for this. You tell it how and how often it starts, what happens in each module, how it handles errors. You can move these modules in a different order, delete them, add more, change your scenario as you build it. Remember, modules are organized by connector, which speaks to that specific API. In each module, you specify the object where the action happens, what the action is, and what data you need to return.

What are connections? Well, each time you add a module that connects to an application, you’re asked to choose your connection. Remember when I said authentication is easy? Fusion stores these connections to be used whenever you need them. They also point to a specific environment.

The thing I wish was explained to me simply when I first started using it, because the documentation just completely tangled up my brain. You’ll hear a lot about webhooks, and webhooks wake up Fusion to act instantly when something happens, and they rely on event subscriptions. So when you set up a watch events webhook for the Workfront connector, you’re registering an event to the Workfront event subscription API. There’s also a custom webhooks module available to use with other applications outside of Workfront, if that’s an available option for that application. So in short, webhooks are instant triggers for Fusion to take action.

Next, you can schedule Fusion to run on an interval of your choosing with polling triggers or otherwise. There’s a couple of other ways to do it. So watch records and watch fields are two polling trigger modules for Fusion. Fusion checks in with those modules on whatever cadence you specified and takes action if necessary. And it does nothing if it finds nothing. You can also schedule many other modules if you want.

So on-demand is how we’re gonna be running scenarios today, simply because I can control the data I wanna work with, and I just like this method better for demos. There are use cases actually for true on-demand scenarios, like certain data uploads or cleanup efforts. There are several others.

Okay.

So I wish someone had done this for me. And so I’m doing it now.

To illustrate the difference between an instant trigger webhook and a polling trigger watch field or a watch record module, I have this cartoon.

And there’s another one on the next slide. So when you create a watch events module, you specify what you want it to deliver to Fusion, which creates that event subscription in that event subscription API. So whenever it happens, the event subs send it straight to Fusion so it can take action. It’s like sitting in a restaurant, and if you ordered a burger and fries, the event subs waiter is gonna bring you that burger and fries whenever it becomes available, like forever and ever and ever and ever, until you turn off the scenario, which probably would equate to leaving the restaurant, I guess. Okay.

Watch field and watch record. With these, it’s quite different. So when you set up one of these modules, you specify how often Fusion is gonna go check for those conditions in Workfront. If you’ve ever had a person or dog or cat waiting for supper, you know what this is like. For said person, dog or cat, asking you a million times if that supper is ready. That’s a polling trigger. They’re polling for what they need to be ready. And then Fusion is doing that to Workfront. I hope that landed.

Okay.

So now let’s talk about execution. Now you know how scenarios start. So when a scenario runs, it’s called an execution, initialization, and then it goes through as many cycles as you specify of running through each module, commit if it’s all successful, rollback if it’s not, and then finalization.

Inside of each module, you also have the initialization, commit or rollback, and finalization, but you also have operations.

And so those are successful actions performed by a module, and they’re counted at the end of the scenario. Each module would get a number of operations, and in the example video above, like right here, you’ll see that each module was one operation.

So I’m just gonna let this run while I keep talking.

Go.

So there’s also an execution log. You can see it down here in this bottom right. And so what that’s gonna do is it’s gonna run while the scenario is running, and then when it’s over, you can kind of scroll up and down and see what was going on there.

So a little bit more on operations.

An operation in Fusion is a task performed by a module. So for tracking purposes, anything that’s successful that happens is actually considered an operation. And the number of times the rest of the modules run depends on the number of bundles they must process. So one run of a module for one bundle is one operation. I know, very confusing. And there are exceptions for things like aggregators.

JavaScript, so it’s not. It’s all a complete lie. But this is just to illustrate the fact that you are not doing on the left when you’re working in Fusion. You’re having fun in modules on the right.

Okay, we are so close to getting to Fusion and having some fun, but we’re going to talk through a few key points on what I’m going to show you first.

So I have some goals here with this demo. I want to show you how to start a scenario from a template and edit it. I want to show you the value of the magic of Fusion and jumpstart your brainstorming. I’m giving myself a disclaimer here about these scenarios. These are real use cases, real customer asks, and they all started from templates. We’re going to talk more about templates in just a second. I’m starting these manually, so these are on demand, but in the real world you’re going to want to set these to trigger on their own, either instantly or schedule.

The data in my work environment is very much test data. Imagine it with what you’re used to seeing. That’s basically apologizing for my mess.

Okay, so it’s important to note that all the scenarios I’m going to show you are started from publicly available templates. They are available to you if you have Fusion. Most of these my colleague and I built based off of feedback from real customers, and they’re very real use cases. You can implement these. You can implement anything you’re going to see today and change it however you want.

That’s kind of the point. That’s what I want to show you.

These are the automations that I’m going to show you. There are seven. I don’t know if we’re going to get through all of them, but what we’re going to do is I’m going to start through here and I’ll assess the time. If I think we’re going to run out of time, I will let you all pick what we do as the last one.

In the real world, some automations that I’m going to show you would be blended together to form more cohesive automations. I’m singling them out here because they’re from templates, number one. Number two, because it will make more sense to you, it’s easier to digest these in smaller chunks. For all of these, Fusion sends updates about what it did to the objects. This is such a key best practice in terms of when you’re working with Fusion because it helps everyone in Workfront understand and appreciate how hard Fusion is working for them. It gives you an insight as to what Fusion is doing in there. We’re going to save this as a reference. I’m going to start the demo. Let’s get started.

Switching screens. Everyone is seeing the template area. Cool.

We are actually going to start from this very, very popular template right here, which is the Workfront Convert Approved Issue to Project. Again, probably our number one use case. To start from this template, click on it. It’s telling me a little bit about the template on the right. It’s loading. Now we’re going to use it. I’m going to open it up. It’s going to ask me for my organization. I’m on a few orgs, so I have some stuff in my dropdown, but you probably won’t. Off we go.

The first thing I need to do here is I need to change the connection to my instance. As you notice, this little wizard is walking me right through what it is that I need to do here. I’m going to change this. I don’t want to go to preview. I want to go to production. Off I go.

This is just telling me about my limit. It looks like I have a maximum number of results set at 200. I’m fine with that. We’re not even going to get close to it. I’m going to hit continue. You can kind of ignore this because we’re going to change it later anyway. I’m going to hit okay. Let’s see. Let’s look at my filters here. The first filter is going to be for making sure that I don’t have any resolving objects on my issues. Perfect. That’s exactly what I’m looking for in this use case. I didn’t even talk about the use case. We’re converting an approved issue to a project. This is conversion, but it’s conversion of an approved issue. First part of my filter, making sure it doesn’t have a resolving object because it wouldn’t need to be converted. The second part is looking at old text value that has this colon a. What this is making sure of is it’s looking for an issue that had been approved. That’s what that means. Then this third portion here that I have is to make sure that this issue is closed. We want it closed. Let’s move on. Our last and second module here, first thing it’s indicating is change your connection. Yes, I need to make sure it’s prod, which is what I had before. Now I’m able to go through here and I can make some changes based off of what we have here. What I know is I’m taking this timestamp out right now because this threw an error this morning. I’m going to change this right now. Open up my mapping panel. I want now. Then it says plan start date. Now sounds good to me. Add in your preferred template. I could add a template there if I wanted to. I won’t right now. Then this preserve issue, this is so that it doesn’t delete the issue as we’re converting. This is a choice. You get to say I’m going to delete or I’m not going to delete it. Let’s hit continue. Now I have my scenario set up. Now I need to go into work front. I need to go look at my data and make sure I have an issue that falls into all these parameters.

I’m going to go over here to this request queue. Really? Really? The demo gremlins. Here they come. Okay. Back online. Let’s go to this convert project I have here. Here are my issues. I’m just going to go ahead and I’m going to add an issue right here.

We’re going to call this demo. Here’s what I know. I know that I need to have an approval on this because that was my first condition that I had there. I’m going to do a single use. We’re going to make this quick. I want this to start when it’s convert. We’ll call this one. I’m going to be the approver. Perfect. Here’s what I know. I need to get this into my convert so that I can approve it.

Now my next condition for Fusion to convert this was to get this in a closed status. It’s approved and now I need to get it closed. Where are you closed? There’s closed. Here we go. Perfect. Love it.

Back in my scenario. Now what I want to do is I want to not hit run once because if I hit run once and this is on demand, this is me running it on demand, I want to choose specifically the issue that I just worked with because that’s the only one I care about. That’s my test case. I don’t want to go through the rest of my system and mess up all the data in my system. To do that, I’m going to right click here, choose where to start, choose manually. What this is doing because this is a watch field, it’s a watch field on issues. What you’re seeing are all these different statuses. You aren’t seeing in this list different issues because we are focused on the statuses. Here’s what I know. I need to catch when that status moved into approved, which is right here, and then that’s where I want Fusion to start. That’s where I’m going to start. Okay. Now I can run it. Let’s see what happens. We’ve got one operation here. Scenario run was completed. Everything was successful. Everything’s green. Now I can show you what we have here for the operation. You can see that in my output, I have more than one bundle. Here are all my bundles. Over here, this is the actual conversion. My result here is the project that was created from Fusion. I’m going to go back to Workfront, back to this project. Now you’ll see demo, resolve project name. It gave it an owner, all that fun stuff. Let’s go over to this project because we sent it an update that didn’t go through.

That’s because there is an update. That’s my next use case. Just kidding. Got a little ahead of myself there. Okay. Here’s the thing. This came from a template and honestly, it doesn’t quite fit my use case. I’m going to make some changes to this scenario because I don’t really like that whole approval thing. I don’t really need it. I’m going to get rid of that. That’s the first thing I’m going to do. I’m going to go, yeah, old text value to approve. I don’t want to do that. We’re not doing that. I want to keep the resolving object ID does not exist because I want to make sure I’m not converting things that are already converted. Then I like this to closed. That’s fine. That works for me. It doesn’t matter. That’s cool.

I also want to go over here to the conversion part of things and take a look. Is there anything over here that I would rather change? Let’s see.

I’m looking for, and as you can see, there’s a lot of options here. This name, I don’t, I’m not really crazy about this. What if I add in here the assigned to ID after this right here? That’s an ID. I don’t know if I really want to do that. Nah, we’re just going to leave this as is. That’s fine. At least I know I have the options to change that there. I think I’m good. I am going to add one more thing over here to my filter. Let’s try this. I want to add the project ID. As you can see in my mapping panel, I don’t see a project ID here. Interesting.

Here’s the thing about Fusion. You can’t work with data you haven’t gotten yet. In order to go get that data, I have to go over to my first module. In my outputs, I’m looking for project ID. Where are you project ID? There it is. Now you’ll see what happens. Once I added that, I’m refreshing my metadata.

Then I can add project ID here. That was one of the things that took me a really long time to understand was that you couldn’t work with data that you hadn’t already gotten. Now I can come back here. I can grab this ID. Copy that. Put it in here. Now I’ve enhanced my filter. Now I can just run this. I no longer have to worry about choosing manually because I already have this confined to this one project. Let’s do another one. Remember, I didn’t have to go through all of that approval stuff again because now I’m just looking for a status of closed.

Now I can run it. Now I’m going to convert another project. There’s my project. That is just an example of taking a template, starting from a template, and then making some really, really quick changes to it.

Now what I’m going to do is I’m going to start demoing some of the other scenarios that have been built from templates that are going to speak a little more deeply to use case. This is coming from the same template, but this is adding a project template based on a convention.

We’re watching our statuses. This is the same. What’s different here is now I’m looking for that convert status. That’s the status that I want in order to tell Fusion to convert. Then I’m doing a couple of things. Because of the way that the owner comes through in this module, I need to parse that to get the owner ID so that I can use it later because I want to use it down here when I convert. Then in the middle here, what I’m doing is I’m mapping how I want Fusion to choose what template to use on these projects. Basically, this is saying if the marketing ownership equals growth and the level of effort is large, use this as the template ID.

Then again, this is the same convert to project that we just saw. I’ve made some different changes to it. Then this is where I got lost in the last scenario. This is where I’m going in and I’m creating an update to say, yay, you have a project.

Let’s go into Workfront and I’m going to create another issue. I’m doing it from this button instead because I want these custom fields. I’m going to call this CNV demo. We want Buzz Lightyear working on this. Large submit. Now I have my issue. It needs to be in a convert status or Fusion is not going to notice. Here we are in convert. Now I can run this. I’m going to get my project. I’m going to get my update that gets sent to the marketing lead.

Perfect. Now let’s go over to Workfront and let’s refresh. Here you can see there’s my project name that I wanted and there is Buzz. Here’s my custom fields that you saw. Then there’s my template that I wanted.

Let’s take a look at this Resolve project and then you can see in our update, yay, you have a project now. I am moving so much slower than I expected to. I think let’s assess out of these scenarios that I have where I want to go next because we’re not going to make it through all of these. I think let’s hear some love for proof. Do we want to see some things on proof? Give me some icons. Give me some hands. Want to see some proof? Let’s do some proof. I’m going to do this task update and completion if approved. This is one of my favorites. As you know in proof, if you have a proof on a task and that proof is approved, nothing happens with the task. The task is not completed. This template aims to handle that.

We’re watching for proof decisions. We’re checking on the decision and we’re going through and if it’s approved, we’re going up this route and then we’re completing the task. That’s the highest level of what’s happening here. I’m going to go into Workfront and I’m going to go into this task right here. As you can see, I have this pending right here. I’m going to open up my workflow. Sometimes this takes a minute for proof to realize, but I’m going to go ahead and approve this.

Now we’re working with a different API. We are now working with the proof soap API. I’m going to choose where to start because I’m looking to make sure that that approval that I just did has come through. It looks like it has not.

Let’s refresh this. Give it a minute. Sometimes it needs just a minute.

We’re going to try this one anyway. Let’s see if it works.

Aha! This is a good, good learning. Essentially, because that data isn’t ready yet from that change that I just made, when I tried to choose another one, nothing happened because it didn’t make any of the data conditions and it wasn’t actually ready to move past. I got one operation on the first module, but nothing else happened because it couldn’t. Are you there yet? Still not there. Well, there’s a lag in this one. We’ve got a choice. Either we can wait or we can move on. Should we wait or should we move on? I’m moving on. We’re waiting. Moving on. I’ll try one more time and then I’m out. In real life, this is not going to happen because Fusion is just going to do this for you when it’s ready, but it’s not ready. Moving on. Let’s do it. Let’s do the other proof one. This one doesn’t have that problem.

Let’s do this gigantic one. This one is a blast. This is proof delegation without calling it proof delegation. What I’m doing here, and it’s starting with this multiple variables here. What it’s doing is basically in this find approver name, what you’re able to do is you are going to put in the person that you want to replace all of their approvals with and the person you want to replace them with goes in the replace.

Maybe this person’s going out of office and you want to replace them with this person is Peppa Pig and Super Potato. They’re not people. Then you add their emails down here. Then what this is going to do is this is going to go find and replace based off of what is available in the UI. The reason that I say that is if it’s an owner, you can’t just do that. Even if they’re the approver, you have to actually switch the owner. This is going to follow, like all of these routes are going to follow the behavior that’s allowed in Workfront in terms of how all of this is handled.

Let’s go over to proof delegation here. What I have here in this workflow, as you saw, we want to replace Peppa with Super Potato. That’s exactly what we’re going to do. Off we go. We’re going to watch this travel. It went up this route right here. This route is automated and not owner or creator, meaning this was an automated workflow. Peppa was not the owner of the proof. There you go. There’s Super Potato. There’s our replacement.

That specific automation is from a template that I released last quarter very quietly. Some of you might be like, I’ve never seen that one before. That’s because it’s relatively new.

Now what I think we can do is we can go back to, and I’m trying to be mindful of the time because I want you to have enough time for questions. I want to just go back to this other proof one and see if we can get this thing to fire.

You can do it. Still not there. That’s very odd. Anyway, don’t you just love those demo gremlins? They’re my true favorites.

Let me pop back into the deck. I thought I had so much more time for playing around in Fusion. I guess not. I know. It kind of applies when you’re having fun. It’s still so helpful to see your process when you’re walking through those things, what you look for when things get stuck. What do you look at? I think that’s so helpful to see, especially for folks that are newer.

Maybe I just need to talk faster. Maybe that’s what the problem is. You’re all good.

Okay, so let’s get down into how do I get started? Okay.

For those of you wanting to get started using Fusion, this section is totally for you. This is my advice to anyone who wants to start using Fusion to protect your instance. Start small. I mean this in a few different ways, but start small in your scenarios. Don’t make your first scenario some sweeping integration. Don’t do that.

Then you want to get familiar with webhooks, watch events, all those things. Just start small. Also start small and using small sets of data. You kind of saw me doing that and using filters. Don’t try to bite off more than you can chew. Also, you can roll back from those things a lot easier.

Process mapping. So process mapping is a game changer because as you’re building these scenarios, you’re going to get lost and like I forgot what I was supposed to do. Where am I supposed to go? That will help you build your scenarios and then when you’re done, you have documentation on what exactly it is that you built, which is really helpful later on. Connect to sandboxes. I feel like we talked decently enough about this that I’m going to skip what I was saying here so we can get to some questions.

But test intensely. I mean this. I really, really mean this. If you know Workfront and you know its behavior, you’re on your way to successful scenarios. But do create test cases around how it behaves. Make sure your scenario is built to handle it all the way around. So you saw that in that last scenario, how many routes I had. And that’s because of how many different ways that proof delegation is going to work based off of the proof role and all kinds of things. Error handling. Learn about it now. You will need to know lots of things about error handling. Fusion governance. What I mean by this is understanding your distribution of teams, who’s in them, what connections they have to one environment, how are you managing your scenarios and folders, all of that stuff. We didn’t talk about this, but once you understand the elements of your Fusion org, you’re going to be able to think this through. If you’re beginning your Fusion learning in an already established organization that has running Fusion scenarios, please talk to your teammates. Tell them where they want you to go so you keep everybody safe because you want to be able to feel safe in your learning too to be able to make mistakes. Templates. Just use them. Have fun with them. We’ve loved building them, but we know they’re not going to be perfect for everybody. And they have learnings inside of them too. There’s little bits and pieces and things you can learn from those. Experience league. Hey, follow documentation. Videos. Get comfortable. You’ll be there a lot. Community. You might be surprised at how much help is available over there. Search the posts. Create your own. Watch past webinars. There are some amazing webinars that go much deeper than I was able to go. Go check them out.

I do know that there’s one instructor led course for Fusion, which is on demand as well. If you have the learning.adobe.com learning subscription, you can check that out.

Finally, lastly, support isn’t going to build you a scenario, but they’re going to help you if you have really specific questions. Okay, Q&A. We made it. Let’s do it.

What do you have? Tell me all about it. Let’s see. I’m going to go ahead. I’m going to.

Enable.

My.

Cameras in case I want. I know Sam’s are doing a great job of answering questions in the chat. If anyone has a question, feel free to put your hand up. Sam, if there’s anything you want to address that’s coming up in the chat that you want to talk through live. I do need just a couple of minutes at the end, but we have like a minute or two here that we can chat through a couple of things.

I’ll just mention my shared a video link that includes a lot of topics, including some that came through, and I didn’t quite get a chance to talk to all of those, like a request to look at web hooks more. And there was an intro to web hooks and more of an advanced web hooks there, along with some other topics that people might find helpful.

Awesome. Thank you.

I know lots of folks are excited. Maybe we can do a part two. Jen people are like, this is so helpful. So I’m down for a part two. All right. We’ll get that scheduled.

Mm hmm. Mm hmm.

Mm hmm.

Mm hmm.

Mm hmm. Mm hmm. Mm hmm.

Mm hmm.

Mm hmm. Mm hmm.

Mm hmm.