51ºÚÁϲ»´òìÈ

Transcript

Hi, hello everyone.

Thanks for joining. We will be getting started in the next couple of minutes.

Just waiting for the rest of the attendees to join.

While we wait, today’s session will be focused on, as you can see here in the screen, about Workfront Fusion basics and best practices.

And it will be led by my colleague, who’s in the call, Alex Pafli, and by me.

And again, let’s wait just one minute or two. Victoria, can you reshare the screen? I have a message in chat that there’s nothing on the screen. Of course.

Oh, then there’s another message that there’s something on the screen, but still, can you just reshare it? Yeah.

Are you able to see my screen, Alex? I can’t yet. And I see thumbs up from the people, and yes, so yeah.

Good thing.

There’s one person that’s not able.

But normally, I think it’s a yes.

Okay, perfect. Thank you.

Okay, then. So just for the people that just joined recently, I will be repeating myself for those who joined the beginning, but this session will be focused on Workfront Fusion basics and best practices. So before we start, just wanted to show the upcoming virtual events we still have for Ultimate Success for this quarter. Okay, so we still have from April 30th onwards.

And we also have these events coming in May for those who want to join this event and register. Don’t forget to register.

So, I will be starting then. Good morning. For some people, I imagine. Good afternoon for other people.

And welcome, and thank you for joining today’s session. Again, focused on Workfront Fusion basics and best practices. My name is Victoria Jill in English, Gil in Spanish, and I’m a field engineer in Workfront.

And I will be leading this presentation webinar with my colleague, Alex, which he is a technical solution manager in Workfront as well.

And we’re going to go ahead and kick off our session today. So first and foremost, thank you for your time and attendance today. Just know that the session will be recorded. And we will be sending a link to the recording out to everyone who has registered.

This is a live webinar as a listen only format, but do feel free to share any questions into the chat and Q&A pod. We will answer as soon as possible. In addition, we also have reserved time to discuss questions that are surfaced at the end of the session.

Just previously, before we start, I just want to give you an overview. I imagine most of you are already very familiar with the Success Accelerators activities. But just wanted to give you an overview of our activities and their categories, since they’re here to help you plan your value, enable your teams and execute against your roadmap efficiently.

As you know, we have technical readiness, organizational readiness, adoption and enablement. And finally, we do have a new accelerator designed to help teams deploy Gen Studio efficiently for performance marketing and campaign setup.

Remember that these are accelerators delivered as part of your ultimate success plan and can be scheduled with your CSM and TAM.

But without further ado, I will be passing on the microphone, the imaginary microphone to my colleague Alex. So you can go ahead, Alex.

Thanks, Victoria. Hello, everyone. Thank you for joining us this afternoon for our Fusion best practice session. So as Victoria said, my name is Alex Pavloff. I’m the technical solution manager here for Workfront and AEM. And now to kick things off, I want to show you an interesting slide and probably analyze it a bit together, especially the numbers we see here. So overall, today, information is spread across so many different applications, right? It’s harder than ever probably to find access and use it efficiently. Probably you had this experience, I had this experience before, we probably all had this experience. So if you think about typical marketing or creative ecosystem, teams are often working across dozens, if not even hundreds of different tools, usually even different departments.

So without a way to consolidate that information, it becomes nearly impossible to get a clear, transparent view of projects and its content.

Overall, to be honest, fragmented processes is not something new, right? But today, connecting those processes is kind of crucial. And the amount of marketing content, campaigns, and the need of personalized customer experience has made it even more urgent, in my opinion.

And let’s even see the numbers. Let’s be honest, the tech stack isn’t really helping us. Companies today have on average 371 SaaS applications in their portfolio. And well, that’s a staggering number, to be honest. And managing all of them, knowing which tools to use, of which tasks, and keeping all the data connected, to me, it sounds practically a full-time job now. And it’s, I mean, not the worst yet. Most of these tools don’t naturally talk to each other. They don’t easily integrate, right? It’s not a surprise that in a recent survey we had, 70% of all employees said their managers aren’t providing the right technologies to day-to-day work. 62% said that it’s harder to coordinate with colleagues, understand their responsibilities, track project statuses, or even find the information they need. Right? So also pretty big number. 30% said that they spend only a third of their time on actual creative work. The rest is lost meetings, searching for files, and handling manual tasks. A lot of us had similar experiences. And maybe, probably most concerning in my opinion, that 22% said that they don’t truly understand their company’s goals. Well, as they said, just enough to prioritize their own work efficiently.

So this is interesting numbers, if we’re going to think, and it’s not just about too many tools, right? If we think, the reality is that these tools often don’t integrate. They create barriers to collaboration. And because one tool does everything, teams end up juggling far too many systems, and obviously it’s time consuming.

So based on that, we can see why perhaps seamless integration is so important. And that’s why we need to bring these tools together in a way that’s probably transparent, easy to manage, and ultimately empowers teams to collaborate better. It will drive real efficiency. Organizations today are increasingly looking to kind of a no-code load solution. That’s, can you come back please? I’ll just tell when. Yeah, yeah, yeah. I just want to talk slightly more about the key takeaways. What I see, and I think you’re all going to be in line with me here, it looks like organizations today are increasingly looking to kind of a no-code, low-code solutions. And you could ask, what is the goal, right? Why we do this? Kind of there is a logical answer to this. At first, it is the pressure on IT departments, right? We have a lot of so-called citizen developers, right? So we want to empower those citizens and developers inside the businesses. That’s going to help us build smarter, more connected ecosystems, and what’s important without heavy technical lifting. Right? So obviously, just because I’m coming from a work-front side, I need to mention this, that a true system of record, a centralized source of truth is still crucial, right? When you can track progress, understand where the project stands, and clearly see what’s happening across teams and overall tools. But we will, and we can unlock real potential here. Well, also, what I want to talk about the key takeaways is like, if we think no one wants to spend their time engaging the same data into multiple systems, right? We’re checking, I don’t know, five different places just to get their work done. So for people to do their best work and to be as efficient as possible, their systems and applications need to be integrated. That’s where tools like Workfront Fusion comes in. And we’re going to talk about Workfront Fusion more, but for now, I just want to say that basically helping organizations drive real success by making it easy and fast to connect the tools they already use. We’ll dig more into this, but let’s talk slightly about integration.

And overall, this integration can be done days, not weeks.

Yes, so now let’s align slightly, probably. Before we jump into the Fusion nuts and bolts, let’s take a moment and align on terminology. Probably that’s a good best practice. So the terms automation and integration, right, are often used, I would say interchangeably, right? But in the context of Fusion, they mean two slightly different things. Automation is about executing a business rule within a single application or solution. Integration, I would say, connects multiple applications or solutions together. Both automations and integrations may include logic, right? So it’s like, it can involve functions, formulas, to manipulate data while it’s moving between systems. But the key difference, I would say, in the scope, right? Because automation stays within one system, while integrations connect across systems. Knowing that difference will help us to dive deeper into the Fusion. Can you go to the next slide, please? So, again, probably it’s a good time to answer that question. What exactly is 51ºÚÁϲ»´òìÈ Workforce Fusion, right? At its core, Fusion is, like we discussed previously, a low-code automation tool. So it’s designed to make it easier to connect systems, automate work, and move data between applications, right? Without needing heavy development work. So kind of citizen developers friendly. In other words, I would say Fusion is our automation and integration superhero or additional employee. It enables you to connect multiple applications and web services together in a, like you see, visual way. Giving you all the building blocks, let’s say, that you need to build effective automation and integrations. So Fusion sits on top of APIs, making it simple for both traditional developers and citizen developers to focus on solving real business problems. Without actually even getting stuck into the technical complexity of it, right? Under the hood, Fusion execution kind of engine handles all your automations securely and reliably. Making sure they run exactly when and how they’re supposed to run, right? How you set. So Fusion helps you move faster, basically. Work smarter and spend less time on the plumbing, I would say.

And obviously that gives us delivering real results, right? Can we go to the next slide, please? So like I said, building blocks. When we talk about Fusion, the first building block which comes to mind is actually, we call them connectors, right? Here you can see just a subset of them. Connectors are basically wrappers of an application’s APIs. So meaning you don’t really need to write your lines of code or fully understand the APIs altogether just to get started. And if we’ve got a variety of different like pre-built connectors, like you can see here, some of them are more native to our infrastructure, some of them are less. But they cover a wide range of common tools and we’re constantly adding more along the pre-built templates that we’re going to talk slightly later today. And all those connectors, they have basically, well, basically most of the connectors have kind of differences. There’s so-called triggers and there’s so-called actions. So triggers, what kicks off the automation, like a new request being submitted, let’s say. And the action is what happens after, right? So like, let’s say, create a project, update the record. If you’re familiar with the APIs, basically that’s all the requests you can imagine, like get, update, put, delete, right? So all those are actions. And triggers, in other words, can be some event trigger or can be a verb hook as well that will trigger this scenario. So if needed, Fusion can also connect to any systems that accept HTTP or web service requests. So if we don’t have this connector right out of the box, and if that system supports APIs, you always can use that HTTP request just to connect it to your system.

So that’s about the first building blocks that we call connectors. Can you move to the next slide, please? Yes. So let’s say you’ve got your building blocks. Now let’s put them together, right? And in Workforce Fusion, workflow is called a scenario. So we made it simple kind of to create a completely connected 51ºÚÁϲ»´òìÈ ecosystems using Workforce Fusion. And here you kind of see an example of a scenario. The blue icon is basically a trigger. Then you have also filters and you have specific actions, which in our case, yeah, project. I also have update a record, which is basically, if you know APIs, that’s an update request, right? Put. So if you see on the right side, you have additional modules, which you can pick. That’s what connectors are. So basically here, we’re just showing you that it’s not only about the 51ºÚÁϲ»´òìÈ infrastructure, we obviously have another ones, but we also had a slide before which showed you examples. So you can connect Workforce with tool across the 51ºÚÁϲ»´òìÈ Experience Cloud, right? And Document Cloud portfolios, creating seamless workflows that drive real results basically. And we’re going to demo you one of examples later on. So as I said before, most integrations are supported by pre-built a few Fusion connectors. So we can get up and running pretty quick. If we need something that’s not available out of the box, and your system supports REST APIs, you can use HTTP request module. Yeah, please move to the next slide. I would say like, okay, so we kind of know what is Fusion now, right? We know what the building blocks are. We know that this is modules that are connectors. We know that if you want to build a workflow, we’re going to use as scenario. What should we automate probably comes at one point. And so listen for keywords like repetitive tasks, right? Copying and pasting, so much human errors, and maintaining standards, too many systems, too many steps, right? These are signs of manual error prone time consuming processes, and exactly what Fusion can fix here. So as example, imagine that we have tasks, right, in Workfront. And we have users, aka, let’s say, designers or content creators that need to create a specific asset. It can be anything in the Word document, it can be PDF, PowerPoint, or just an image. But basically, the idea is that as soon as designer or content creator will create this asset, they will need someone from a team will need to approve this asset. As soon as they approve this asset, what happens next? Usually, the job is done, right? Because the asset was approved. However, the task and task status is still in progress, right? Because it was approved. So now, designer needs to go to the task and manually close that task. Do we really need this process? It sounds like a process for Fusion, right? Because if that asset was approved, most probably means that this task is already completed. So why not make a process where we check if the new proofs exist, then we check on what status that proof approved, not approved. And if it’s approved, let’s check what status of the task and if the task status is still not complete, let’s change it to complete. But for lock purposes, let’s also add a comment inside that task like, hey, this task was approved by this person at that specific time. And then let’s say another comment, this task was marked as completed because this asset was approved. So a real example, we’re going to go through the demo today to show how to do this and actually how quickly can it be achieved. Can we go to the next slide, please? So some of you might be thinking, okay, well, if I just want to code everything using API calls, right? And while APIs are great, coding everything directly to APIs can and I would say will introduce challenges. How to maintain without extensive knowledge sharing, right? Barriers to adoption, I would say, only technical experts can extend integrations, right? So we lose that citizen developers completely. Frequent needs to rebuild when changes occur, very possible, can be time consuming. Now I’m not talking about things like a data mapping, right? With Fusion, it also really simplifies processes and we have a lot of additional things that we’re not going to cover today, but like data stores and et cetera, that really helps us. But Fusion captures and shares connection keys and important elements, basically, all that needed for a fast, sustainable development without heavy coded coding. So probably now when we kind of know what this tool is and that it exists, we learned what is connectors and how they work, basically. We can probably go to the next slide and think where to start.

And I’m also going to give a microphone back to you, Victoria. Thank you, Alex.

So yes, now that Alex has talked a little bit just about what is Workfront Fusion and the benefits of using Fusion and how it can address a lot of pain points that companies are having nowadays. Now let’s go into Fusion itself and how it works.

First of all, when we go into Fusion, we have this higher level that’s called the organization. The organization basically will refer to that workspace that will contain all your different teams that you create, all your users, all your scenarios, all your data stores, for example. The organization will be this higher level that contains everything in your instance.

Then we have teams and users.

So organization is the higher level in your organization, you would have as many teams as you desire. So the teams is in the area where you will be able to provide a more granular level access. Each team will consist, as you can see here in the image, of its own scenarios, its own connections, where we connect to the different tools that we need to connect, the different webhooks, which are our triggers that initiated our scenarios, keys, data stores, data structures. So each of the teams will have its set of own capabilities.

Users will be added to Fusion and then users are added to the corresponding teams that they need access to.

So if we move on, how do teams actually work? And just a couple of best practices here for us to give you.

Basically, teams will help you give a proper administration and governance to your Fusion instance, where first and foremost, it’s very important to understand that when you grant access to a user to a team, they will have access to everything I just mentioned, to all the capabilities I just mentioned in the previous slide. The users that have access to the team will have access to all these features in the team.

So we need to understand that users inside a team will have access to all these capabilities of their own team, but not of the other teams that they don’t have access.

Second thing, very important, is to have naming schemes set up. And what do we mean by that? It’s very important to have naming schemes for the scenarios that we build, for the connections that we create, webhooks as well. If not, we will have confusion and clutter along in the instance and not be able to understand which connections are inside which scenarios, what webhooks are doing.

So it’s very important to maintain naming schemes, and it’s also best practice. Also, we recommend using a folder structure for your scenarios for those that are active scenarios, depending on the processes that we are building scenarios integrations. So also having a folder structure. And also, we invite you to do recurrent cleanup practices at a team level. And why is that? Sometimes we do have users that we add to our teams that eventually don’t need access. So always try to maintain the users that do need access to the team and take away the access of those users that don’t need access anymore.

And also, scenarios that are built maybe during our testing mode, a phase that are not needed anymore. And actually, we don’t need to archive. So making sure that we do delete those scenarios. Very important as well in connections. While we’re testing normally, we tend to create a lot of connections that we don’t use in the future as well as webhooks. So try to maintain only the relevant and active connections and webhooks that we are using in the instance. If not, afterwards, it will start to have a lot of confusion and clutter in your Fusion instance.

Another best practice that’s actually not added here in the slide but that we will talk about is when recommendation is normally have, let’s say, a team per environment. And what do we mean by that? We know that normally in Workfront, let’s say that you have your production environment, your preview environment, and your sandbox, either sandbox one, sandbox two. Let’s say that we just have one sandbox. We would go ahead in Fusion and have a team created per environment. So I would have a team for sandbox. I would have a team for preview, and I would have a team for production. And why do we recommend this? First and foremost, maybe it’s because of access. Only certain people need access to preview, to sandbox, or to production.

But again, what we mentioned is that each team has its own set of scenarios, connections, and webhooks. If we create a team per environment, we maintain the connections. If we’re talking about the team of sandbox, we will only be having connections to sandbox environment and if we are in the team of preview, we will be having connections to the preview environment, same as production.

So during the testing phase, we will be minimizing any error or anything that could happen in the production area, for example, when we’re using another team in sandbox and preview.

So, moving on, which Alex already mentioned before about Fusion templates.

Normally, a lot of customers actually don’t know that Fusion has a predefined template that can be used for very popular automations, for administrative tasks, as Alex said. Also integrations including Marketo and Anaplan.

So if you’re new to Fusion and you don’t know where to start, we would recommend for you to use a Fusion template in order to start building the scenario that you desire and then you would just customize it to meet your specific needs, but you won’t need to build it from scratch.

Actually, the demo that we will be presenting, we will be using a template so you see how you can set up a template and customize it for your needs.

As well, while building scenarios and running those scenarios and testing them, you will come along with a couple of errors, which I want to mention here. There are three types and let’s go with the first one, which are the 2x error codes, which basically mean that you will have a successful completion of the scenario, but sometimes you can get a runtime error if it’s too long, which may be because there’s a problem with the response of the endpoint.

Also, we have the 4x error codes, which refer specifically when there are errors from the endpoint applications of the API. So basically, the data needed from the other applications that we’re using is either not received or not in an acceptable format, or also it could be a broader issue where the endpoint could have unavailable service. Finally, we have the 500 error codes, which are server issues, which basically could mean two things. First and foremost, if I have the 500 error code, I would check and verify the connections of my fusion scenarios because normally it’s because maybe the credentials are not working anymore, maybe they have changed. If I have already checked and verified the connections and they are working fine, I would then contact support and check the connections because maybe there is an issue with fusion directly and that would refer to the server issues.

So now I imagine this is the part that everyone is waiting for more, the demo part.

And before we go into the demo itself, I will be explaining what the scenario will consist of. Alex already gave you a heads up of what it consists, but basically what we will be seeing in here is this scenario at a high level, let’s say, consists of decisions and proofs that are made in WordFront that eventually, depending on the type of decision, if it’s approved, if it’s a changes required or other decision, it will be making updates to the task where the proof is attached. So let me dig a little deeper here and explain a little bit more how it works.

First, what we’re doing here is that a fusion is reading all the decisions, all the proof decisions that have been made in the instance. Once it has all the decisions, it will be reviewing, okay, is this a new decision or it was just a past decision that was in the instance? If it’s new, it will pass the filter and check which type of decision it is. So maybe if it’s approved, if it’s changes required or if it’s another decision. It’s for us to understand which decision type it is.

Then it will check if it’s not appending a proof. For those of you who are not familiar with proofing in WordFront, when you have created a proof and a decision has not been made, your proof, let’s say, that has like a pending status. That’s what we mean by pending here. So we’re double checking that the proof has a decision made and it’s not still pending. Then what we’re doing is we’re setting variables for the type of decision and who made that decision in here.

After that, what we do is basically we are reading some information that we need later on to perform the actions that we have later on. But basically we’re reading the document version, the task ID, very important, some project details in this module.

Then what we do is basically we review the task ID that we just read in this module. We are going to review and filter if it really exists in WordFront. And if it does, then it will pass the filter. And what it will do is just FYI, users in WordFront have an ID as well. So what I will be doing here is getting the ID of the user who made that decision.

And after I have all of this, then I will be routing in the scenario, depending on the type of decision the proof had. So if the decision was that it was approved, it will first verify if the status of my task is completed.

Then it will complete my task.

After that, what it will do is it will create an update in the task itself saying that the proof has been approved. And it will create the update in the task directly. That is for the approved part. Let’s imagine that, OK, no, my decision is not approved. It’s changes required. So if it’s changes required, what it will do is it will create, again, a comment in my task where my proof is attached that the decision of changes required has been made. And finally, my last filter would be if it’s the case that it’s not neither approved or changes required, but another decision, same will happen. It will create, again, an update in the task saying that another decision has been made in my proof. So basically what we’re doing here, I make a decision in my proof and then if it’s approved, I complete my task. And also because of blocks, I leave a comment. If it’s changes required or another decision, I would just leave a comment of the decision that has been made in my task. Eventually what I’m doing, I’m taking away the manual task of after approving my proof, going in and completing my task.

So I will pass on to Alex for him to do the demo. Just one more thing. Can we go back slightly? OK, so first let me answer the legacy modules. So legacy modules are the modules that had some updates, right? Why do you see legacy modules here is because, as we’re going to show later on demo, we created this from a template. So the template itself is not updated with new modules yet. But we’re going to do later on. They still work fine. It just gives you an idea that this is outdated module.

Then about the naming conventions and basically best practices about the naming. We have a couple of suggestions. For example, if we talk more about the work front, the idea is there that name the fields, with FUSION, they kind of like if it’s a Pascal case, but also the best idea is to write the naming the way that someone outside could read this. That’s why we usually try to watch all proof decisions. It gives you a straight idea what this module is about. It checks the overall decisions, right? It checks what decisions are for those proofs. And also we have those filters. Those filters are also named. For example, if you’re going to go to yes, exactly. Are they new? Are they pending? If they not, then you have a router there. You have filters as well. If it’s approved. Yes. So also inside FUSION, each FUSION scenario, we have such a thing as notes. And best practice is to try to explain the use case, what you’re trying to achieve here inside the notes for future people who are going to read this basically.

Yes. So they were always going to say legacy unless we can edit them. So for example, if I would now go delete this get work from users ID module, right? And would add a new one, you wouldn’t see this legacy anymore. Yes, I’ll give you… Imagine a module version is, I don’t know, 1.0, right? If we have a new version of a module, you will see a legacy title there. So it’s a good practice sometimes periodically to check and if we need to update them. Also, if it’s something super important that will be deprecated at least some amount of time, we’re always going to inform you through many different channels. I’m going to spam you basically everywhere.

So yeah, now can we go into the next slide and we’re going to have a Q&A session after this one. So this is a prerecorded demo for a simplified reason basically. But when you just join your work front and again, like Victoria said, we have a team already here. I’m in Alistair’s marking team. We have also an organization, work from solution, advisory, legacy, again, non-production, right? So that’s the organization name. In your case, that would be obviously your company name, most probably, and team is what you’re going to choose and what type of people you’re going to assign to the team. All those things you see on the left side are related to this team. As Victoria said, if you can press play, I’ll just talk on top of it. So basically, you can see the statistics here, which are related to your team. You can create a new scenario, but we’re going to go to templates.

And obviously from here, we can choose the template we want. Just because we talked about work from proof, work from task updates and all that, you can see that we’re going to have that. I think the video is paused.

I think I’m going to choose this one now. That’s the proof. Again, we’re choosing templates because what I’ve noticed and what we notice, and I love users actually ignoring templates, but that’s the best way to teach yourself how to use Fusion. Right now, templates are showing you with animations basically how the flow is going, how the flow would work, right? We’re going to just create a new scenario. And as soon as we create a new scenario, basically the first thing, just because it’s a pre-made one, a template, it will ask you to connect all those modules. The first thing, as Victoria said, are organizations. So if you’re going to press play button, we’ll see how I just updated here.

How I just updating here the organization. In our case, if you recall, I told this is work from Solution Advisory. Legacy, I’m going to choose this one, which is going to give me now basically a first step to connect to Workfront now. Because like Victoria said, we haven’t watched event. We need to check what proofs were made. Now we need to make a connection. If you’re going to press play, I’m going to know what’s happening. Go to the next slide.

Yeah. So basically what’s happening here, we’re going to connect to proof instance. Again, if you don’t have this proof instance connection, you can press an add button there. Now we choose from when, from now on, because we just created a scenario. The second step is kind of same. So basically, to be honest, through the configuration of this scenario, most of the steps here is just you connect to the solutions. In our case, this is Workfront proof. Again, I’m choosing the same account. Then we’re going to go to the step three, which is basically when we check the user details. So this is now a different instance. This is now proof HQ instance, but rather than the Workfront instance. So we’re going to choose a connection to connect to the Workfront instance. In my case, it’s Alex Alistair-Malkin. Pay attention that I’m using here actually my personal account.

We’ll see why this is a bad idea at the end. But I just want to show you why it’s the best practice to use things like that as a service account. So we can go to the next stage, which is basically going to give us the same thing. We need to connect this module to the tool we want. And we can, it’s going to stay for quite some time because you can see the circles there and it moves now to complete task. Basically our first module, which will do something. So if you’re going to go to the next slide, which is step five, you see that again, I need to connect to my Workfront instance. I’m going to press continue here and it will open me now the first interesting part where we actually update a comment. As you remember, I said that when we, you can move to the next slide. I’ll just talk about what’s happening. So basically, again, we need to connect to the instance we want. I’m using my own connection, Alex Pavlovich connection. So I have here obviously chose that this is a task and I want to comment to the task. And if you see all there was a mapping to specific parts because again, we have a lot of different data here. Proof ID, what version of this proof and so on and so on. And then at the end, you can see who we need to notify. We brought all that data from those modules. You can go to the next slide. So basically now I just want to show you here the idea in Workfront. So if you remember, we have a task now in my case, it’s just an image and I want to open a proof. I am a prover myself here. Right. So all I need to do here is just to make a decision. As soon as I’m going to make a decision approved, we can go and trigger this scenario to see that this scenario actually going to pick it up. I pick this decision, we’ll filter this decision and we’ll make adjustments and the adjustments will be that these tasks will become a complete. And we’re also going to have a few comments inside the task for log purposes. So if you can move now to the other slide and again for demo purposes, I’m running this manually. Right. Obviously in real life, it would be just all this on if we have some kind of a watch event. Right. Or if we need a schedule event, basically, let’s say each day or each X amount of time, each 15 minutes, I don’t know, usually you choose. We can do that. In our case, I’m pressing run once. It will go and remember just because we had recently an approval, we had a decision. And if you see the flow here, it actually gives you a nice idea what’s happened. So first we checked what decision is then we went through the filters. We realized that this is approved. So we went at the top and we also noticed that it’s complete task. So we actually changed the status to complete. And we also added two comments there. The one which states that we changed it to complete and the other one that this was approved. Obviously, you are the boss here. Right. So if you don’t need those two comments, why you need to spam or you just need one, you can basically remove one of those branches or change slightly your text the way you want, which will make well, basically you can adjust it the way you want.

Now we can go to the next slide. Just by looking at the time. Sorry. Yes, sorry, I was on mute.

Thank you, Alex, for explaining the demo. And just to finalize before we go into the Q&A, I wanted to mention in case you want to dig deeper, anything fusion related, talk about data stores, for example, or dig deeper in any matter with fusion, we would recommend you to talk with your team or CSM to open a desk side coaching with our team so that we can help you and enable you more on the topic of Workfront Fusion.

So now we will be open the Q&A section. And while we’re doing that, I will be launching a poll for everyone. If you can reply, you would much appreciate it.

So hopefully the poll has been launched now for everyone.

Meanwhile, if you have any questions, I mean, I was trying to answer them on a go, but I could miss something if you want time.

So going to the Q&A section, I see that Javier Reyes Alonso has asked if it’s possible to create a custom new module to be used in a scenario as the others provided. So, if you’re If you think about the whole module, about the whole connector, then the answer is no, there is no such option. However, if you need something very much, you can always ask Tams or CSM and they might be able to connect with engineering to discuss this. But if it’s related to just HTTP requests, right, custom custom API calls, then yes. If you want like a custom module, Thank you, Alex. Yeah, if you have anything to add. No, I was going to say the same.

For the other question from Dichanc, if there are any predefined fusion templates to create programs, campaigns or updates, emails in Marketo, since there are 30 plus templates, I don’t know them all by memory, but I will be sending the recording and I will be replying to your question once we review all the fusion templates that we have.

Yeah, there’s another one, which is the best practice in fusion for launching a scenario automatically by watch event or scheduled one. I would say this is really depends on the use case, right? Personally, I would prefer watch events if it’s possible just to have less operations, right? Instead of checking everything each time we trigger this scenario only when we need this. But that’s not obviously as possible. So in that case, it’s a schedule. That’s what I would say. Yes.

I see that questions are being asked in the chat and not in the Q&A.

I haven’t covered this before, but basically, yes, the demo we showed here is templates, right? So we use templates. And as I said before, why I’m showing the templates, it’s because it looks like templates are kind of ignored by our users. But this is a great way to start learning how professionals, how experts are building those scenarios. But yes, you always can.

I mean, and usually you will create scenarios from blank. So there is a button on the right side when you’re going to go through, when you’re going to access to fusion where you have an empty empty scenario and you choose trigger first like we discussed, right? What’s going to trigger that scenario? What’s going to start this scenario? And then we have, we can start adding actions. Another question.

I just replied in the chat for service accounts, how to set up a connection instead of using your own personal account. So best practices always not use your own account as Alex mentioned before. So you should create a user, let’s say an automation user, automation fusion user in Workfront. We would recommend for that user to have admin rights and to use that user as a connection in the scenarios that you build in Workfront. Yes, because now when our scenario and let me just quickly share screen while we still have some time.

If you notice that exactly the task we changed, right? So imagine can you see the status complete? So that was done by fusion and also these two comments were added to this task by fusion. Notice it’s me and why it’s me because I used my own personal account in fusion. So obviously fusion going to use my account to post all those comments which can lead to nonsense basically. So that’s why we prefer if it’s a service account, it’s more cleaner in that case.

Let me stop sharing the screen. Yes, I don’t think well, we will be sending the recording and reviewing if we missed any of the questions. Just quickly. Yes. So to add users inside to add users in fusion. That’s that’s through admin console and you have 51ºÚÁϲ»´òìÈ admin console. You will have a fusion product there. You can assign those users to that product and that’s how they’re going to get access to fusion as a whole. And then they have access to that organization. And then you can create specific teams and you can start putting those users inside those teams and some of those users can be admins of those teams that can manage the team. So you would assign them as a team admin access inside fusion. But at first it’s done through admin console.

For those who have migrated to the admin console, there’s another question for those who have still not migrated. You would add the user in fusion directly, not in the admin console.

OK, then.

Again, we will be sending the recording. We will review the questions in case we missed anything from the chat. Thank you all for attending today. Thank you, Alex, for explaining everything perfectly. And hopefully this has helped you have a better understanding on what’s fusion and how it works and how it can benefit you all. Thank you.

Thanks a lot.