Initial scenario design walkthrough

Transcript

The purpose of this first walkthrough exercise is to give you basic navigation tips when you first log into the Fusion system, as well as building your first scenario. For this first scenario, we’re going to download a CSV file from Workfront, parse it to get information about each row and then create a project in Workfront from each row. To be successful as you build the scenario, you want to be logged into your Fusion system, be logged into your test drive and have the project list spreadsheet open. We’re going to teach you how to build the scenario and best practices for leaving notes, naming your modules and saving frequently. Have fun.

Let’s start by signing in to the Fusion system.

Once I sign in, I’m brought to the team section, which gives me a quick glance of active scenarios in my system, operations being run and a couple of other things. We’ll talk about this more in future training. For now, I’m going to go to the left hand panel and choose Scenarios.

Once I click in this Scenario section, I have a new left-hand panel that allows me to organize my scenarios into folders.

On the right, I see a list of all scenarios built in my system, a list of active scenarios, inactive scenarios and concepts, which are scenarios that haven’t saved well or need some additional editing before they’re considered active or inactive. Let’s create a folder to house all the practice exercises you’re going to create as you continue going through the training.

I’m going to call it Fusion enablement exercises.

Once I add the folder, I want to click into that folder to create my first scenario.

Once I click that Create a new scenario button, I’m brought to a landing page where I can preload any apps that I want to use in my scenario that I’m building. For this first practice exercise, go ahead and click Workfront and then Continue.

Now I’m brought into the Scenario Designer, which gives me an empty module in the center and a couple of options down in the toolbar. Best practice whenever I start creating a new scenario is to give it a title by double clicking into the blank or generic title at the top left and calling it something meaningful for this first practice exercise.

Let’s call it Initial scenario design.

Clicking away will save.

In the middle of my screen, I have what’s considered a blank module. Initially, it’s our trigger module and I can tell that it’s a scheduled trigger because of the clock icon tied to it.

If I was doing a webhook or some sort of event subscription trigger, I’d see a lightning bolt instead but this first module is where my scenario starts. Left clicking the scenario is going to give me an option. Which app do I want to choose? Here we already pre-selected Workfront, so it appears in the list but I can add another module or search for keywords into other modules that I have access to. Go ahead and click Workfront and then you’ll see a list of modules that are available in the Workfront app that I can use in my scenario. For this scenario, I’m going to click on Download Document.

Once I do that, I need to establish a connection or authenticate myself to my Workfront account. I’m going to do that by clicking the Add button and giving my connection a meaningful title.

Clicking Continue and moving through the authentication window that pops up.

Once I establish my connection, I’m going to be able to download a document from Workfront. In order to download a document, I need to provide the document ID. I can find this in Workfront in the folder where you were instructed to upload all Fusion exercise files in a previous video. By selecting a document, you can get the document ID.

In this case, I want to select the project list.

Click on Document Details, and the ID is right here after the word Document. There are two IDs in here. I want the first one, copy that, and I paste it in the Document ID section here. And click OK.

Best practice is to name your modules as you create them. This will make your scenario easier to follow when troubleshooting. We’ll name this Get project list. To do that, we right click, choose Rename, and click OK. Many of the documents we use in these exercises are spreadsheets. In order to get the information we need from them, they need to be in a CSV format. When we parse a CSV file, we’re going to take each row in the file and create a bundle in our output bubble. So in this example, we will parse the project list file and create 20 bundles. Then we will create 20 projects in Workfront. Notice that the first row here just contains the column headers so our next module will be Parse CSV, which I can get by clicking on the right-hand side of the current trigger module here.

I don’t see the CSV app, so I’ll type in CSV in the search area.

I’m going to choose Parse CSV as our module.

We’ll set it to parse six columns.

The top row is a header row, so we’ll tell it to treat it as such. The delimiter type is comma, and we want to put the data from the download module in the CSV field, and we’ll rename this Parse project list.

We’ll save and then we’ll click Run once to view the output. You could ignore this warning that a transformer should not be the last module. This is true but it doesn’t matter for this test.

Click Save anyway.

We’ll get the same message for run once. Click Run anyway. We’ll click the execution inspector to see the inputs and outputs of the Parse CSV module. There is one bundle, a CSV file as our input and 20 bundles as outputs, one bundle for each row in the CSV file.

Now we’ll add another module to create the projects.

This will be in the Workfront app and will be the Create Record module.

I need to choose a record type for this practice exercise. We’re going to create a project in Workfront for each row in the project list, so the record type I want is Project. I can click the drop down list and scroll to find project or if I start typing P-R-O-J, it’ll get right to the project.

Once I choose project, it’s going to load the available fields that I can map into. If you type in a Command + G on your keyboard and then type the word Name, you can see we’ll find all of the fields with the word name in it. Control + G again. It’ll keep going down through all the names. So this is the one I want. Once I find the field that I want, need to click on that little checkbox to the left to select it and notice that it appears down here below as well.

Then we’ll choose the other fields we want to include, which are plan, start, date, and priority.

Once we’ve selected the fields, I can click in each one to map it to the appropriate column in the project list. I’ll click on the the name field to grab the project name in the panel that pops up and drop it into that field to map over. The next thing I want to do is map over priority.

Notice that priority isn’t going to be something we map over just yet, but we have a list of the default priority fields that I can choose from. For this, I’m going to say it’s a normal priority.

The last thing I want to map over is the plan start dates. I can pull the plan, begin date from the CSV file and select that as my project plan start date. Once I do all that, I want to be very careful to select OK at the bottom right-hand corner.

If for whatever reason you accidentally click outside of the panel that pops up for a Create Record module it won’t save your progress and can be pretty frustrating until you get in the habit of always clicking OK.

Again, best practice to right click and rename this Workfront module.

I’ll call it Create Workfront projects and click OK.

I’m going to save it again, and if I come down here to the left corner and click Run once in my designer window, I’ll see the wheel spin and I’ll see that in each module something has occurred. Above each module, there is a bubble that pops up as I’m testing and running my scenarios. We’re going to call these the execution inspector and if I click on the first Workfront execution inspector, I can see that the input to the operation was the document ID, and the output bundle was the CSV document.

If I click on the Execution Inspector for Parse CSV module, I can see that the input was a long string and the output was 20 bundles, one for each row in the CSV file.

If I click on the execution inspector of the second Workfront module, I can see that 20 operations were performed. I can open Operation 1 to see one bundle as input, which came from the Parse CSV module and one bundle as output, which is the ID of the project that was created.

I can go to Workfront and see the project. In the All Projects section of your Fusion training, we’ve actually created a shared filter, new projects this week, and a shared view of newest projects added.

These allow you to sort and organize the projects by entry date that you’ll be creating as you go through your training week by week. This makes it easy to find and or delete projects or any information you put into the system as you’re testing and playing around with practice exercises.

Other best practices to teach you now that we’ve created our first scenario is that we want to continually save as we’re building. So down here at the bottom, we’ve already mentioned this. We have one of the controls here in the toolbar. That’s the save option. Another great tool to utilize as we’re building out our scenarios is the notes feature. If I right click on a module, I can see the Add a note option, which opens up a panel. Here I can type in a note that creates a more meaningful overview of what’s happening within the module so someone doesn’t have to continually open and close it to understand what’s happening.

I can also add multiple notes to the same module or to other modules in my scenario by right clicking and using add a note.

You’ll notice that after I add some notes to my scenario down in the control panel, I have a Notes button with an orange icon that appears when notes are added to the scenario. Clicking this notes icon makes those notes appear and I can see which module those notes are connected to by this thin gray line.

We’ve now created our first scenario and we’re going to continue building on this in future exercises. -