Schedules

The Schedules function is similar to the Task Scheduler in that they both trigger specified tasks to run at a defined point or points in time.

• Use Schedules to run one or more defined tasks one or more times on either a recurring basis or on a data driven basis, without further user interaction.

• Use Task Scheduler schedule one task to run on a one-time basis. The Task Scheduler requires user interaction when the tasks are scheduled.

  Schedules start all tasks simultaneously, not sequentially. Tasks that do not require data can start right away. Tasks that do require data first interrogate the database. If the task does not find the required data, the task waits until the data arrives before continuing to run.

• Data-driven schedules provide flexibility in scheduling one or more tasks. Tasks can be run once, or on a group of specific calendar days. You define the frequency for the schedule (for example, every two hours between 12:00 and 18:00, or every 45 minutes between 13:00 and 15:30). See Data-driven schedules.

• Recurring schedules run one or more tasks on a regularly scheduled basis. You define the start date and end date for the schedule. See Recurring schedules overview.

  In general, tasks supported by recurring schedules are not supported by data-driven schedules.

• Data-driven schedules must include the entity ID or IDs and a data time span. See "Data driven schedule task types" in the IEE MDM Help.

• Recurring schedules cannot support tasks that require entity IDs and data time spans. See "Recurring schedule task types" in the IEE MDM Help.

Note: For schedules to work properly, verify that you set the correct time zone on the IEE application server.