Field

Description

How do you want to schedule this?

Schedules the batch on a daily, monthly, or periodic basis. Select one of the following options:

Daily On. Select the days you want the batch to run.

Weekly On. Select the day of the week on which you want the batch to run.

Monthly On. Select a month.

Every. Select how often you want the batch to run in minutes.

At what time do you want to schedule this?

Enter the start and stop times for the batch.

Use Business Calendar with source

Select this check box and then select a business calendar. Select a business calendar to use if you do not want to submit the batch on weekends or holidays.

Use Date Rule for Effective Dates

Select this check box and then select Click here to select date rule to define the effective date of the batch.

This allows you to submit a batch with a create date that is different than the effective date. For example, a batch that is scheduled to run at the start of the month, but run with an effective date of the prior months end. The date that the batch is scheduled to run becomes the create date of the batch. That date is passed through the selected date rule to determine the effective date of the batch.

To add business calendar logic to the effective date calculation, select a business calendar in the date rule. This allows you to adjust the effective date for holidays and weekends.

Due Date

Click this link to specify a due date for the batch. This allows you to set up a due date for scheduled batches and send notifications when the batch is past its specified due date.

Enter the number of days, time, or number of minutes and click OK

Define Dependent Events

Click this link to schedule batches as dependent on other PACE events.

Use default time zone as on server

Click this link to select a time zone.

For example, a user in the Boston office can edit a batch created and scheduled in the London office. The batch looks the same to the user in each location. The time zone is stored in the user_data column of the PACE_MASTERDBO.SCHEDULE_DEF record.

Client Reporting recognizes Date Rules with a non default time zone setting configured in the underlying PACE Concentration Report. When overriding or passing the effective date from the Advanced Reporting engine to the Concentration engine, it considers the time zone selected in the Date Rule of the PACE Report Profile.

For example, if the underlying PACE Report Profile contains a Date Rule with a time zone of GMT plus ten hours and a batch is submitted at 4:00 p.m. on the first of the month from an environment where the PACE Server is configured with a time zone of GMT minus two hours, the Concentration report will be submitted for the second of the month.

The profile_from_date and profile_two_date values in the pcre_rpts table of the package will contain the adjusted effective date. The eff_date value in the pcre_pkg table, however, will contain the effective date before the time zone adjustment. This is because the pcre_pkg table represents the package as a whole and situations may exist where not all of the underlying reports contain a time zone adjusted Date Rule. The effective date of the batch itself does not reflect any time zone adjustments.