Creating a generic job

This topic describes general instructions and features related to creating any type of job.

To create a generic job

On the Network > Actions > Jobs page, click Add and do the following:

1. In the Details tab, enter information in the following fields:

   The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
   This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
   

2. If you want to add actions to the job, click Add Actions and select the type of action. A pop-up window appears that allows you to specify parameters for that particular type of action. For example, the following window appears for a Deploy to Active action.
   
   
   
3. Enter information for the action in the displayed fields and click OK to add the action. For more details, see To run the Deploy to Active action.
4. The job actions are displayed on the Actions tab.
   
5. Click Report  to view the proposed configuration changes for a span action. When the Remediate, Deploy to Active, or Deploy to Stored action enforces one or more rules, the Compliance Summary report is shown in a pop-up window:
   
   For an action that remediates all assigned rule sets, the report shows results only for the rules that have been actively tested against the device (that is, rules for which there is stored compliance status from a previous Refresh Device Status, or from the rule checked at the most recent configuration change). For an action that remediates selected rule sets and rules, the report shows results only for those rules. The Failed results indicate which rules would be corrected by this action.
   
   When the Deploy to Active or Deploy to Stored action is not configured to perform rule remediation, the Configuration Comparison report is shown instead. You can review the differences between the current configuration and the proposed configuration for each device.
   
   
6. On the Add Job page, click Preview  to preview the change scripts built for the Remediate, Deploy to Active, Deploy to Stored, and Scan Syntax actions.
   Depending on the action, the Preview Sub-Actions and Scripts window shows the full configuration, the incremental merge script, or the resolved template that is to be deployed. These are review copies of the scripts. The actual scripts are generated again at execution time, to ensure that the current data is used. Some template substitution parameters might resolve differently at the execution time. For example, any login credentials entered with the job are not used here, however, they are used at execution time.
   
   The left pane shows a tree of the action, any sub-actions, and the devices in the network span. The right pane shows the corresponding details. If you click an action or a sub-action, the settings are displayed. If you click a device, the script to be deployed to that device is displayed.
   Sub-actions appear only when an action performs remediation. For a non-remediating action, that level of the tree is absent. For this type of action, the action is displayed at the top with its owned devices directly underneath it.
7. (Optional) Click Save As Template in the right pane to save the script as a template.
8. When you are ready to save the job, choose one of the following options on the Add Job page:
   • Save as Draft: Job is saved but not submitted for approvals or scheduling. You can edit the job multiple times when in Draft state.
   • Save and Submit: When job approval is required, select the job approval type. Even when the Enable Job Approval option is set under Admin > System Admin > System Parameters (see Testing-rules), job approvals are not required for passive actions. These actions include Snapshot, Assign as Target, Log Event, Send Email, Send Trap, and the custom actions configured for no approvals.