Contents Saved in a Runbook Template

The following components will be saved in a Runbook Template (RBT):

• Map for Template
  A runbook must be instantiated using a map; therefore, each RBT is associated with a specific map. Users can use the default map or modify it as needed.

• Reference Runbook
  Each RBT stores a reference runbook, which is displayed in the editor to maintain consistency between the RBT and the standard runbook editing interfaces.  The RBT stores template variables that  are used to replace specific parameters in the reference runbook, enabling the template functionality.

• Template Settings by Node

  Refers to the static (fixed) parameter values defined for each node in the template. These settings remain unchanged unless explicitly edited in the RBT.

• Template Variable:

  Settings that need to be parameterized during the transformation of a runbook into a runbook template. These settings will be converted into template variables. These Variables allow flexible input at the time of runbook creation from the template. 
  Example: In the Execution CLI Command, the command with variable is show ip interface $intf, where $intf is a template variable.