We have now completed the construction of your first NetBrain Triggered Automation. This document has highlighted the suggested bottom-up approach to create automation. Let’s now review what we’ve built, how it relates to one another, and what gets sent to NetBrain.

▪The NetBrain Automation Trigger Rule defines the condition(s) in the ServiceNow Incident Record, which will make the automation happen. Inside this rule, the appropriate NetBrain Automation Template is specified.

▪The NetBrain Automation Template defines the informational payload (Domain ID, Tenant ID, Device Name, etc.) that will be sent to the NetBrain system to properly process the triggered automation request. Inside this template, the NetBrain Map Template “Stub” is specified.

▪The NetBrain Map Template “Stub” defines the base look and feel characteristics of the map that will be generated as a result of the automation trigger coupled with the data delivered by the NetBrain Automation Template.

What you will see in the next section is that this daisy chain approach to triggered automation will result in a NetBrain Device Map being inserted into the ServiceNow Incident Record.