You can link a job prototype component to a TriggerSchedule for scheduled execution. For convenience, the provisioningNiagara palette provides a TriggerSchedule for drag and drop copying (Figure 28).

This is a standard TriggerSchedule component, identical to the one found in the schedule palette.

To schedule, you link the “Trigger” slot of a source TriggerSchedule to the “Submit Job” (action) slot of the job prototype component, as shown being done in Figure 29.

Do not link a job prototype to the default “Backup Schedule” under the ProvisioningNwExt—that TriggerSchedule is already linked to the “Start Backup” action of the extension. Those components are not recommended for regular provisioning jobs that include station backups. For background details, see Why the Start Backup action is typically NOT recommended.

To define the schedule, double-click on the linked TriggerSchedule for its Scheduler view. You can set up a one-time trigger in the future, or define regular (repeating) triggers, or define any combination of such trigger events. For more details, see the “Trigger Scheduler view” section in the User Guide.

If desired, you can copy a TriggerSchedule under a job prototype component (using it as the container), and make this same link. This provides portability. Remember if you duplicate/copy the parent job prototype after configuring the schedule, all copied job components will have that same scheduling configuration.