What you see on the screen

This is a privilege-based feature: The user will be able to access, view, add, edit, delete, execute, and export only if the administrator has given them privileges. This will be defined under roles and privileges.

The Configuration Template Grid page lists all templates created by the user and also the templates assigned to the same user by an admin or template management full-privileged user.

The Access Control List feature in this module lets admin-privileged users decide who can view, edit, or delete any specific templates in NCCM.

Configuration Template Grid shows

Template ID - To know the creation sequence (recently created or old).
Name of Template - The name will be unique and will be used in other features while using the Template.
Vendor – The Vendor Device where this template can RUN (Vendor Specific).
OS Type – The Vendor Device OS Type where this Template can only RUN (OS specific).
- In case the Template can RUN on all OS Types of the same Vendor, Input the OS Type as ‘ALL TYPE.’

For example, CISCO IOS, IOS XE, NXOS, IOSXR, and ASA may use different command 
syntaxes for the same operation.

Type of Template—NCCM supports 9 Types of Templates, each of which will be explained in detail in the following sections.
Active Status—Enabled/Disabled—During execution, this flag does not impact Jobs set as Disabled (template disabled) but already assigned to an Upload Job. On the other hand, Disabled Templates will not be allowed to be used in New Upload Job Creation.
Execution Ready or Production Status—It should be in the Ready State to use in the Upload Job for a configuration change.
Approval Required Flag - The value will always be Yes (Approval is always required).
Actions – There are two action icons displayed here – Execute & Quick Execute.

Note: When the Template is used in the Upload Job by a whitelisted user or Approver, the Approval Process is bypassed, and the job is executed directly.

Created User – The user who created the Template.
Description – Template description that defines the operation purpose.

PreviousConfiguration Template NextHow to write Command Portion in Template

Last updated 8 months ago

Was this helpful?

Configuration Template Grid shows

Template ID - To know the creation sequence (recently created or old).

Name of Template - The name will be unique and will be used in other features while using the Template.

Vendor – The Vendor Device where this template can RUN (Vendor Specific).

OS Type – The Vendor Device OS Type where this Template can only RUN (OS specific).

In case the Template can RUN on all OS Types of the same Vendor, Input the OS Type as ‘ALL TYPE.’

For example, CISCO IOS, IOS XE, NXOS, IOSXR, and ASA may use different command 
syntaxes for the same operation.

Type of Template—NCCM supports 9 Types of Templates, each of which will be explained in detail in the following sections.

Active Status—Enabled/Disabled—During execution, this flag does not impact Jobs set as Disabled (template disabled) but already assigned to an Upload Job. On the other hand, Disabled Templates will not be allowed to be used in New Upload Job Creation.

Execution Ready or Production Status—It should be in the Ready State to use in the Upload Job for a configuration change.

Approval Required Flag - The value will always be Yes (Approval is always required).

Actions – There are two action icons displayed here – Execute & Quick Execute.

Note: When the Template is used in the Upload Job by a whitelisted user or Approver, the Approval Process is bypassed, and the job is executed directly.

Created User – The user who created the Template.

Description – Template description that defines the operation purpose.