Creating a predefined job
Predefined jobs enable a user to create, edit, and execute named sets of common and repeatable tasks. By working with predefined dobs, users can make available a set of reusable job definitions that can be prepared and executed when needed.
Predefined jobs are like jobs, which have been described in detail under Creating-a-job. They are, however, different from jobs in the following ways:
- Predefined jobs are reusable, stored components and are displayed on a separate Predefined Jobs page.
- To convert a predefined job to a job, on the Predefined Job page it is necessary to run a Prepare Job wizard.
- When creating or editing a predefined job and adding an action, instead of specifying a span (for example, realm, group, devices, or multiple devices) you can optionally select to be prompted for the span value when you run the Prepare Job wizard.
- The system maintains references to all the jobs created from a predefined job. A table of jobs is displayed on the predefined job view page and contains hyperlinks to the job detail page for each job listed.
To create a predefined job
- Open the Add Predefined Job page by navigating to Network > Actions > Predefined Jobs > Add.
- Fill out the Add Predefined Job dialog box the same way as you create a job. See Creating-a-job.
- (Optional) If you want to add an action requiring a Network Span value (for example, Deploy to Active), select Define At Runtime.
Specify a prompt for the span value by using descriptive text (for example, Enter Span Name).
- (Optional) If the action requires other runtime values, you can leave them as blank or accept the default values. For example, the target device IP address for a Ping custom action.
If you use a predefined jobs often, you can create and save shared runtime parameters with default values. See Creating-shared-runtime-parameters. - Click Save.
The predefined job is displayed on the Predefined Jobs list.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*