Starting with Gen 2 Automation Studio

Automation Studio

This segment of the tour introduces you to the core functionality of Itential Automation Platform (IAP), and since the word "automation" is built right into the product name, it only makes sense sense to jump in and create an automation using Automation Studio.

Automation Studio is where most of the magic happens in IAP. It's an all-in-one application suite where your automations are created and edited. Without Automation Studio, there's not much point to having IAP in your environment.

More information on Automation Studio can be found in the application user guide on the Itential docs site. Also be sure to check out the Automation Builder guide to learn more about arranging and connecting the tasks that go into building your automation.

Note: This tour guide uses the Gen2 Automation Builder canvas.

Create an Automation

Creating an automation using the Itential platform is simple:

1. From the IAP home screen, click the Automation Studio option in the navigation bar on the left. The Automation Studio page will open.

2. In the Quick Start card, click + Create A Workflow. A dialog box opens.

3. Select Workflow from the "What would you like to create?" menu. The canvas selector displays.

4. Select the Generation 2 (Cloud) image to utilize the Gen2 Automation Builder.

   Figure 1: Gen 2 Automation Canvas
   

5. For this tour, let's give your automation the unique name "EnlightenMe". Of note, the Name is a required field.

6. Next, click the CREATE button. A relatively blank canvas will then display that contains a START and END task.

   Figure 2: EnlightenMe Workflow Canvas
   

Add a Task to the Canvas

When an automation is first created, a New Node box is already provided. This is an empty node and needs to be populated with an actual task item. Click the New Node box on the canvas. On the right side of the screen, you are presented with a list of nodes/tasks that can be used in your automation. This area is called the Task Menu Sidebar. Itential refers to the items listed in the sidebar as tasks (or steps) that must be completed within your automation.

The docs.itential.com site contains a collection of Task Reference guides for the various tasks listed in the Task Menu Sidebar.

1. In the Search box at the top of the sidebar, type "restCall" and the search results should include a task named "restCall".

2. Click the restCall task and observe that the "New Node" on the canvas has been replaced with the REST Call node/task. Also notice that the Task Menu Sidebar is now replaced with details and configuration options for the restCall task.

3. Click the Save icon button at the top of the canvas to save your work.

   Figure 3: Add REST Call
   

The REST Call task is a flexible task by which information can be obtained or published across available APIs in a network, including the Web.

Configure Reference Tasks and Reference Variables

Next, let's configure the variable information for your task. In our example, we'll leverage a simple, yet fun, "Chuck Norris" API.

If you already have experience using REST Calls in other systems or scripts, the variables available for the REST Call task will look familiar to you.

1. If not already selected, click the REST Call task on the canvas to view the details for the task in the right-side menu.

2. From the Details tab, change the value in the Summary field from "REST Call" to "FetchFact". This will help us distinquish this restCall task from others later on.

3. For the Description field, enter "Obtain A Chuck Norris Fact".

   Figure 4: restCall Details Tab
   

4. Click the Variables tab. Tasks typically have Incoming and Outgoing variables. Depending on the tasks selected from the Task Menu Sidebar, the number of configuration variables in a task will vary. The restCall task pictured below has seven (7) Incoming variables that can be configured: uri, verb, user, password, headers, body, and responseHeaders.

   Figure 5: restCall Variables Tab
   

5. For the uri variable, leave the Reference task as "Static". For the value, add this (without quotes): http://api.icndb.com/jokes/random.

6. Click to expand the Verb variable, and leave the Reference task as "Static". Change the Value field to the GET option from the dropdown list.

   Figure 6: restCall GET Value
   

7. For this example, there is no need to populate the "user", "password", "headers", or "body" variables.

8. For the responseHeaders variable, change the radio button "Value" from "None" to the pill slider option. Leave the slider in the left position so that the 'X' continues to appear.

   Figure 7: restCall Response Headers
   

9. Click the Save icon (upper-right of the canvas) to save your work.

Figure 8: restCall Save Icon

Notice that the REST Call task on the canvas now reads FetchFact.

Test Run Workflows

To test the workflow and see if it works:

1. To the right of the Save icon is the Play icon (►). Click the blue play arrow. A Job Options modal window will open.
2. For now, ignore the entries for "Description" and "Groups".
3. Click the START button. The Run Workflow modal opens and displays a message that the workflow has started.
4. Within the modal, click the View Job button. A new tab opens in your browser to display the Job Details (within Operations Manager) of the running job you just started.

Figure 9: Job Details in Operations Manager

Viewing Job Details

In the newly opened Jobs view, take a moment to study the page to see the different types of information available in this view. One item you should notice is the restCall task named "FetchFact".

Click the view icon that's located at the end (far-right) of the "FetchFact" task. This will open the Task History for "FetchFact"; you will also see tabs for Task Data and Task Details.

Figure 10: Task History

Task Data

The Incoming tab shows information that was provided to the Task. In this example, you'll observe the variables (uri, verb, etc.) that were specified when you initially created the task. The Task Data tab is the ideal tab to reference when you're troubleshooting a task and need to verify if the task received the information you believe it should have. Essentially you can use this tab to check for incorrect input/faulty output (i.e., garbage in/garbage out).

Figure 11: Incoming Task Data

The Outgoing tab shows the output that's produced by the task. In this example, the restCall task produces a response variable that contains the API's response value, which is in the form of a JSON object. It's important to know that depending on the task's function, the output information will vary from task to task.

Figure 12: Outgoing Task Data

Task Details

The Task Details tab show basic information about the FetchFact task such as Name, Task Id, Task Status, etc.

Figure 13: Task Details

Summary Wrap-Up

Congratulations! In this section of the tour, you did the following:

• Created a Gen 2 workflow that utilizes Tasks to obtain data from a remote system.
• Viewed Jobs in Operations Manager and the task results that were presented in the Outgoing tab of the Task History.

Next, we're going to explore how to pass data between tasks. Keep the Jobs application open for now and continue reading.