> For the complete documentation index, see [llms.txt](https://docs.infraon.io/infraon-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraon.io/infraon-help/infinity-user-guide/infraon-configuration/it-operations/network-configuration/service-template/service-job.md). # Service Job A Service Job is an execution instance of a Service Template. It allows users to select devices, define tasks, and schedule service execution. Service Jobs can be created in two ways: 1. **From the Service Template page** – use the "Add to Upload Job" option. 2. **From the Upload Job page** – select an existing Service Template. ## **Add Service Job** The service Job (Add Job) page is used to select devices, define tasks (select devices for specific tasks), and set a schedule for service execution. When adding a service job from the Upload Job page, the service template must be selected before the device is selected. **Job Details |** Add Service Details | **Label** | **Action** | **Description/ Example** | | ------------------------------------------------ | ------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Job Name**\* | Enter a unique name for the Service Job. | The name should be descriptive enough to identify the job's purpose. **Example:** "Firmware Upgrade – Core Switches" | | **Description**\* | Provide a summary of what the Service Job does. | Clearly explain the job's purpose and impact. **Example:** "This job upgrades firmware on all core switches to version 2.0 for security compliance." | | **Service Template**\* | Select the relevant **Service Template** from the drop-down list. | The selected template defines the execution steps. **Example:** "Compliance Check – Routers" | | **Job Type**\* | Choose the job type from the drop-down list. | **Options:** Regular Job, Configuration Rollback Job, OS Rollback Job, OS Upgrade Job, OS Upgrade for Vulnerability. | | **Notifier** | Select recipients who should be notified about the job. | Notifications ensure that relevant stakeholders are informed. **Example:** "Network Admins, Security Engineers" | | **Agent**\* | Choose the appropriate agent responsible for executing the job. | The agent acts as the execution engine for the job. **Example:** "Infraon\_NCCM\_Agent\_1" | | **Job Status** | Toggle the switch **ON/OFF** to enable or disable job execution. | **Note:** The job must be **enabled** for execution. **Example:** "ON (Enabled)" | | **Download Configuration Before & After Upload** | Toggle the switch **ON/OFF** based on requirement. | If enabled, it captures device configurations before and after the job runs for auditing purposes. **Example:** "ON (Configuration snapshots taken before and after execution)" | | **Device Selection** | | | | **IP Address** | Select an IP address from the drop-down list. | Choose the device(s) to which the service will be applied. **Example:** "192.168.1.10" | | **Asset Tags** | Select tags to filter and categorize devices. | Asset tags help identify and group devices. **Example:** **Switches, Firewalls, Routers** | | **Load IP Address from CSV** | Click **Download Sample CSV**, fill in IP addresses, and upload using **Import from CSV**. | Use this option to add multiple devices at once. **Example:** "Upload a CSV with 100+ device IPs." | | **Device Account** | | | | **Username** | Enter the username required for device authentication. | The username should have sufficient privileges to execute the service. **Example:** "admin" | | **Password** | Enter the device access password. | The password is required for login. **Example:** "**(Hidden for security reasons)**" | | **Enable Password** | Enter the enable password for privileged mode access. | This is needed to execute privileged commands on the device. **Example:** "cisco\_enable\_123" | Once done, click on **Next** to Add Task details. **Task Details |** Add Service Job Task details are updated as per the selected service template. Device details can be changed for individual tasks to suit the requirement. Multiple devices can be selected. * Select Configuration Profile using the dropdown menu. * Select Connection Protocol using the dropdown menu. * Select Connection Protocol using the dropdown menu. * Select device credentials accordingly. Click **Next** to continue. **Schedule Details |** Add Service Job | Label | Action | Description/ Example | | ---------------- | ------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | | **Execute Now** | Click to select the **Run Immediately** option. | The service job will be created and executed instantly upon submission. | | **Schedule Now** | Click to choose a scheduling mode: **once, every, Daily, Weekly, or Monthly, and** then specify the execution time. | The service job will be created immediately, but execution will occur per the selected schedule. | | **Visibility** | Select either **Private** or **Public**. | **Private**: The job is accessible only to the creator. **Public**: The job is visible to other authorized users. | Once done, click **Submit** to add the service job, or click **Request** to proceed with additional approvals. ## **MSP-Based Visibility** For upload jobs created via Service Jobs: * Customer/Entity is inherited from the Service Template and cannot be modified. * Data Collector, User, and Notifier selections are filtered based on Customer/Entity. * Device selection (IP Address, Asset Tag, CSV import, runtime variables) is filtered by: * Customer/Entity * Vendor * OS * User visibility All upload jobs created through Service Jobs follow the same MSP visibility rules as standard upload jobs. {% hint style="info" %} * MSP visibility applies consistently across: * Upload Jobs * Upload Job Reports * Service Templates * Service Jobs * Cross-customer or cross-entity access is restricted. * Visibility rules ensure tenant-level data separation and compliance. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.infraon.io/infraon-help/infinity-user-guide/infraon-configuration/it-operations/network-configuration/service-template/service-job.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.