[Index]

Model: data/Schedule

Scheduling

To access the latest documentation, go to Documentation and Resources at: https://voss.portalshape.com

Single or Multiple actions can be executed on one or more resources. The actions can be scheduled to take place at a specified time or to repeat.

Currently, the action is to execute.

The resources that can be executed are:

• Data Sync
• Script
• Provisioning Workflows
• A schedule can be created during the Bulk Load process. Bulk loaded files that are not set to Execute Immediately can be scheduled by Execution Date, -Time and -Timezone. A scheduled bulk load is shown on the Schedule as a Single Execution schedule type and with the Resource Type as data/BulkLoad.

Care should be taken when transactions are scheduled. For example, data synchronization should be scheduled outside of peak times. The size and scope of the transactions that run determine the length of the time that they need to run. This therefore impacts on the start time. The number of clusters on the system and their size need to be considered as part of a data sync approach.

Create or Update a Schedule

1. Choose the hierarchy at which the schedule is to be created.

2. Open the Scheduling form (default menu Administration Tools > Scheduling to view existing schedules (if configured).

3. To Create, click Add open the Scheduling input form to create a new schedule. To Update, select a schedule to modify.

4. On the Base/Details tab, complete the following:

   1. Enter a mandatory Schedule Name.
   2. Enter the Owner (the user who created the schedule).
   3. From the mandatory Schedule Type drop-down list, choose either the Multi Execution or Single Execution option. This enables the respective Multiple Executions or Single Execution tab on the input form.
   4. Select or clear the Active check box to enable or disable the entire schedule.

5. Click + next to Scheduled resources to specify actions to execute on resources (if required). More than one action on more than one resource type can be scheduled, with specification of a resource attribute.

6. Select the Resource Type. The resources that can be executed is data/DataSync.

7. For a selected Resource Type, select a unique identifier as Resource Attribute, often the name of the Resource Type, typically name.

8. For the Resource, select the value of the Resource Attribute. For example, if the attribute is name, then the name of the resource.

9. The Perform Action check box is used to enable or disable a specific scheduled resource action.

10. On either the Multiple Executions or Single Execution tab, enter the scheduling time information according to the selected schedule type.

    • Date format: YYYY-MM-DD in Local time - an Execution Timezone is selected
    • Time format: HH:MM:SS in Local time - an Execution Timezone is selected

    1. For Multiple Executions, select or clear the following check boxes for execution options on the Multiple Executions tab:

       1. Use Specific Executions - Allows one or more specific schedule times: an Execution Date, Execution Time and Execution Timezone is added for each specific schedule.
       2. Use Calender Executions - Allows one or more calendar times (Calendar Hour and Calendar Minute) and dates (Calendar Month and Calendar Day). If no time is entered, the current time is used.
       3. Use Timed Executions - Allows one or more specified number of repetitions (Number of Repeats) at intervals (Repeat after (x) Days, Repeat after (x) Hours, Repeat after (x) Minutes) from a specified start time (First Execution Date, First Execution Time, First Execution Timezone).

       If more than one of these options is selected, the first scheduled time will take priority.

    2. For Single Executions, provide the Execution Date, Execution Time and Execution Timezone on the Single Execution tab.

11. Click Save to create the schedule.

The scheduled task is displayed on the Schedule list view.

The Schedule model allows scheduling of execute actions. Scheduling can be performed once, or multiple times, depending on the choices given to the schedule instance.

Model Details: data/Schedule