Upload Job Expiry

Upload Job Expiry is applied consistently to upload jobs created from multiple workflows across NCCM. Regardless of how the job is initiated, once it is created through a change request, it becomes subject to the same expiry rules.

Note: The configured expiration time for an upload job is 5 days.

If the job is not approved or executed within this period, it is automatically marked as Expired.

The following job sources are covered under Upload Job Expiry:

Simple Script Execution

It allows you to run a selected configuration template directly on one or more devices without creating a scheduled policy. This option is commonly used for ad-hoc troubleshooting, diagnostics, or immediate configuration actions.

Upload jobs created through simple script execution are typically initiated manually by users to push configuration or scripts to devices.

• The script execution request generates an upload job via a change request.

• If the job is not approved or executed within 5 days:

  • The upload job is marked as Expired.

• An expired job cannot be executed and must be recreated if the script needs to be applied again.

This ensures that manually requested changes are executed only within a valid operational window.

Add Job

• Navigate to Network Configuration → Configuration Templates.

• Locate the required configuration template from the list.

• Click the Simple Script Execution action for the selected template.

• In the Simple Script Execution window:

  • Select the IP Address of the target device.

  • Verify the selected Configuration Template.

  • Choose the appropriate Agent responsible for execution.

  • Select the Shell type (for example, Remote).

  • (Optional) Enable Overwrite Credentials if execution requires overriding stored credentials.

• Click Request to submit the execution

Once submitted, the upload job is created through a change request and executed on the selected device. The job is tracked under the Upload Jobs module and follows the configured Upload Job Expiry rules.

Event-Based Upload Job

An Event-Based Upload Job is created automatically when a predefined system event or alert condition is met. This is configured using the Trigger Configuration module, where specific conditions are mapped to an Upload Job action.

Event-based upload jobs are created automatically in response to system events or detected conditions, such as:

• Event analysis results

• Configuration rollback actions triggered from events

• Upload jobs initiated through event triggers

In these cases:

• The upload job is created as part of an automated workflow and routed through a change request.

• If the job is not executed within 5 days of creation:

  • The upload job transitions to Expired.

• This prevents outdated event-driven actions from being applied after the original event context is no longer valid.

Add Job

• Navigate to Notifications → Triggers.

• Click Add Trigger (or edit an existing trigger).

• In Trigger Details:

  • Provide a trigger name.

  • Select the required customer/entity.

  • Choose when the trigger should fire (for example, Alert Raises).

• In Conditions:

  • Define the filter criteria that should invoke the upload job(for example, Alarm Message in “Download Job Failed”).

• In Actions:

  • Select Create Upload Job.

  • Choose the Configuration Template.

  • Select the Agent.

  • Configure execution parameters such as shell type, retry count, retry interval, user, and approval requirement.

• Review the configuration and click Submit.

Once configured, the upload job is automatically created through a change request whenever the trigger conditions are satisfied.

Policy Remedy Job

It allows NCCM to automatically execute a remediation action when a rule violation is detected. The remedy can trigger a script execution or configuration template to bring the device back into compliance.

Policy remedy jobs are generated when a policy violation is detected, and a remediation action is configured.

• The remediation process automatically creates an upload job.

• The job remains pending until approval or execution.

• If the remedy job is not executed within 5 days:

  • The upload job is marked as Expired.

• An expired remedy job does not retry automatically and requires a new policy execution or manual intervention.

This ensures that policy-driven remediation actions remain controlled and time-bound.

Add Job

• Navigate to Network Configuration → Rules in NCCM.

• Select the rule for which remediation needs to be configured.

• Complete the Rule Information and Match Criteria steps as required.

• In the Remedy Action step:

  • Set the Violation Severity and Rule Violation Message.

  • Select a Notifier (optional).

  • Under Remediation, choose Script Execution.

  • Select the User who will execute the remediation.

  • Choose a Configuration Template or provide direct command execution.

  • Configure additional options such as continuing execution on error, if required.

• Click Submit to save the rule and enable the remedy action.

When a rule violation occurs, the configured remedy triggers an upload job through a change request. If the job is not executed within 5 days, it automatically expires and is marked accordingly in the system.

MSP-Based Visibility

MSP-based visibility for Upload Jobs ensures that users can view and access upload job data only for the customers or entities they are authorized to manage. This applies to upload jobs created through all supported workflows and controls how upload job data is displayed in reports and audit views.

This enforces data isolation, role-based access, and customer or entity-level visibility across upload job–related reports.

MSP-based visibility is applied to upload job data in the following reports:

• User Activity Report

• Device Upload Job Statistics Report

• Upload Job Approval Audit Report

The visibility rules remain consistent across all these reports.

Visibility

User Type	Visibility	Description / Example
Admin User	All upload jobs	Admin users can view all upload jobs across customers and entities. Both public and private upload jobs are visible, regardless of assignment. Global MSP filters and custom filters apply without restriction.
Non-Admin User (Single Customer)	Public jobs + assigned private jobs	Non-admin users can view upload jobs marked as Public. Upload jobs marked as Private are visible only if they are assigned directly to the user or to a team the user belongs to.
MSP User	Customer/Entity-scoped jobs only	MSP users can view upload jobs only for the customers or entities mapped to their account. Within this scope, public jobs are visible, and private jobs are visible only if assigned to the user or their team.
Multi-Customer User	Jobs for mapped customers/entities	Multi-customer users can view upload jobs across all customers or entities they are assigned to. Visibility within each customer/entity follows the same public and private assignment rules as MSP users.

• MSP-based visibility applies only to data display, not job execution.

• Visibility rules do not override job approval or execution permissions.

• Admin users always retain full visibility.

• Upload job visibility remains consistent across reports and audit views.