Create a DNS A Record (Infoblox) - Workflows

Now that we’ve got a JSON Form and a Transformation (JST), we’re ready to put things together in our Workflow.

Workflow Video

Step 1

Let’s create a new workflow.   Click the + button at the top of the left navigation panel.

Step 2

The Create window opens.  We will create a workflow and name it Lab – Create a Record – Infoblox – [Your Initials].

Click Create.

Step 3

A fresh workflow canvas opens. In this use case, we would like to build our workflow horizontally, so we will click and drag our Terminator tasks so they are aligned horizontally.

Step 4

Now that we are aligned horizontally, open the Task Palette by clicking highlighted button.

Step 5

The first task we need is the Transformation task.  Enter Transformation to filter the task list.

Step 6

Drag the task to the canvas.

Step 7

Next we need our first Get A Records task.

Step 8 

Enter GetaARecords in the filter box.

Step 9

The list filters and we drag the Get A Records task to the workflow.

Step 10

Next, we need an Evaluation task.   Enter Evaluation in the filter box.

Step 11

And drag the task to the canvas.

Step 12

Let’s add a Create A Record task.   Enter Create a Record in the filter box.

Step 13

And drag it to the Canvas.

Step 14

Because we are running out of room, we will close the task list and expand the workflow. We click the X to close the list.

Step 15

And we expand the workflow to give us more space.  The next task we need is a second Get A Records task.  Click the Task list button.

Step 16

And enter Get A Records in the filter box.

Step 17

The list is filtered and we add the Get A Records task to the workflow.

Step 18

We repeat these steps to add the final three tasks: a second Evaluation task and two View Data tasks.

Step 19

Now that we have all the tasks in the workflow, we need to add transitions to bring them all together.   Transitions are added by clicking a task, a shaded area will appear around the task, and then clicking and dragging from the shaded area to the next task in the workflow.  

Step 20

We would like to connect the Start task to the Transformation task.  Click the Start task.

Step 21

Now we can click the shaded area and drag to the Transformation task.

Step 22

A green transition appears, connecting the two tasks.

Step 23

Repeat this process to connect each task in the workflow.

Step 24

Notice how the success transitions are green.  Next, we need to add failure transitions to each of the View Data tasks.  

Step 25

Creating a failure transition is the same as creating other transitions except you hold the F key as you drag.  We clicked the Evaluation task and holding the F key, we drag to the first View Data task.

Step 26

Let’s do the same for the Evaluation task to the View Data task.

Step 27 

Notice the transitions are purple, representing failure paths.

Step 28 

Next, we need a revert failure transition from the first View Data to the first Get A Records task.  To draw a revert transition, simply drag from a task to a prior task in the workflow.

Step 29

Select the View Data task.   Click and drag holding the F key from the shaded area to the Get A Records task.

Step 30

Notice how the transition is a dotted line.  This represents a revert transition.

Step 31

The last transition for the first View Data task is a success transition to the End task.

Step 32

For the second ViewData task, we need a revert success transition from the second View Data task to the second Create A Record task.

Step 33

The final transition for our workflow is a failure transition from the View Data task to the end.

Step 34

The workflow is complete.    Now we need to configure each of the tasks.  

Workflow Video (Part 2)

Step 35

Let’s start with the Transformation task.  Double-click the highlighted task to open the configuration window.

Step 36

For the Transformation task, click the drop-down arrow and choose the JST file we created titled Lab – Create A Record - Infoblox JST – [Your Initials].

Step 37 

Verify the formData input has a Source of Job and a Job Variable of formData.

Click the Save icon. 

Step 38

Next we need to configure the first GetARecords task. We first give it a name of Pre Check and add a description on the Details tab.

Step 39

Enter Pre Check Using Infoblox Adapter for the Description.

Step 40

Returning to the Input tab, we select Task under Variable Source.

Step 41

The Previous Task stays the same and for Task we select fqdn.

Step 42

We save it and double-click the first Evaluation task.

Step 43

Name the task Record Not Found? and click +Add Evaluation Group.

Step 44

Click + Add Evaluation.

Step 45

Set Operand A Source to Task.

Step 46

Verify the Previous Task is set to Pre Check and Task Variable is set to result. 

Check the Enable Query checkbox.

Step 47

For the Operand A query, enter response and change the Operator to equals.

Step 48

Select Static for Operand B Source and Array for the Type. Enter [ ] for the Value.

Step 49 

Next, we need to configure the Create a Record task.

Step 50

For this one, the title of the task will remain Create  a Record but we need to add a description.  Click the Details tab.

Step 51

Enter Create A Record Using Infoblox Adapter for the Description and then return to the Data tab.

Step 52

Set the Body Variable Source to Task and View Data to Lab – Create a Record – Infoblox JST.

Step 53

For Task Variable, click the drop-down and select fqdn.

Step 54

The Create a Record task is ready.  Click the canvas and drag to the left to view the remaining tasks.

Step 55

Next to configure is the second GetARecords task.

Step 56

Click the Details tab and change the Description to Post Check Using Infoblox Adapter.

Step 57

Returning to the Data tab, set the Variable  Source for name to Task.

Step 58

Set Previous Task to Lab – Create A Record – Infoblox JST, and for Task Variable, click the drop-down and select fqdn.

Step 59

The Post Check is ready.   Let’s configure the second Evaluation Task.

Workflow Video (Part 3)

Step 60

Change the Summary to Record Found? and click +Add Evaluation Group. 

Step 61

We want to add an evaluation.   Click + Add Evaluation.

Step 62

Change Operand A Source to Task.

Step 63

Set Previous Task to Post Check.

Step 64 

Check Enable Query and enter Response for Operand A Query.  Set Operator to does not equal.

Step 65

For Operand B, the Source will remain Static but the Type will change to Array and the Value will be empty [ ].

Step 66 

The last two tasks to configure are the View Data tasks.  We will start with the first one.

Step 67

Change the  Summary to Record Already Exists. Click the Details tab to add a description.

Step 68

Enter Record Already Exists and return to the Data tab.

Step 69

For Header, select Static for the Variable Source and enter Record Already Exists for the Value.

Step 70 

For message, select Static for the Variable Source and enter DNS A record already exists for the Value.

Step 71

Scroll down and accept the default values for both body and variables.

Step 72 

Scroll to the bottom, leave btn_success as Static and give it a Value of End Automation.

Step 73 

Btn_Failure will also remain Static. Enter a Value of Retry Pre Check.

Step 74

For the second View Data task, change the Summary to Record Not Found.

Step 75

Click the Details tab and enter a description of Record Not Found.

Step 76 

Click the Data tab. Select Static for the header Variable Source and enter Record not found for the Value.

Step 77  

For message, select Static for the Variable Source and enter DNS A Record not found for the Value.

Step 78 

Scrolling to the bottom, we will leave the Variable Source for btn_success as Static and give it a Value of Retry.

Step 79  

The Variable Source for Btn_Failure will also remain Static and will be given the Value End Automation.

Step 80  

Let’s take a look at the input schema.  Double-click the Start Node.

We know that users will be submitting data using our form, but when doing that the values, or variables, are not sent to the workflow individually; they are sent as a single variable called formData. Here, we can see the only required input for our workflow is formData.