Data-driven schedules

Data-driven schedules provide flexibility in scheduling one or more tasks. Tasks can be run once, or on a recurring basis. In addition, tasks can be run on a specified frequency (such as every two hours between 12:00 and 18:00, for example).

Data-driven schedules require the configuration of Occurrences. These are the dates and times that you schedule the tasks to run. Tasks that don't require data may start right away. Other tasks may interrogate the database, discover a lack of required data, and wait until that data arrives before continuing to run.

Occurrences allow you to change some of the task parameters of a task assigned to a schedule for a given occurrence. For example, you have a cycle that performs remote interrogation on a daily basis and on each occurrence it performs a partial read. You would have a schedule with a remote interrogation task template assigned that performs a partial read. However, on the last day of each month, you may want to reset the billing period. Instead of creating a new scheduling that happens once a month to reset the billing period, you can change the template parameters on a specific occurrence to perform the billing period reset.

You define occurrences as follows:

• Calendar. Manually select days by clicking in the calendar. You can specify a single schedule time for the selected days, or the task(s) can run repeatedly at an time interval between certain times on the selected days.

• Frequency. Tasks run repeatedly on an interval in days between specific dates; or a certain numerical day of the month; or a specific day of the week. The calendar is filled appropriately.

• Single Date. Specify a single date and time.

Related topics:

• Defining occurrences

• Data-driven task schedule occurrence statuses

• Data-driven schedule task types