| \n\nName\n\n | \n\nName of the scheduled report.\n\n |
| \n\nReport\n\n | \n\nReference to the report you are scheduling. You can use the Search icon \\[Omitted image \"SearchIcon.png\"\\] Alt text: Search icon to locate the report.**Note:** Automatic email support is not available for Calendar, Map, and Single Score reports.\n\n |
| \n\nUsers\n\n | \n\nIndividual users who receive the report at the scheduled date and time. Users must have **Notification** set to **Enabled** on their user records to receive reports.\n\n |
| \n\nGroups\n\n | \n\nGroups that receive the report at the scheduled date and time.\n\n |
| \n\nEmail addresses\n\n | \n\nComma-separated list of email addresses of report recipients who are not users on your instance.\n\n |
| \n\nApplication\n\n | \n\nName of the scoped application that contains the report. **Global** appears if the report is in the global scope.\n\n |
| \n\nActive\n\n | \n\nWhen active, scheduled reports are delivered.\n\n |
| \n\nRun\n\n | \n\nTime interval to use for running the scheduled job:\n\n- **Daily**: Runs daily, at a designated time.\n- **Day and Month in Year**: Runs yearly on a specific day and month \\(for example, July 14\\), at a designated time.\n- **Day in Week in Month in Year**: Runs yearly on a specific day of the week in a specific week of a specific month \\(for example, the second Monday in October\\), at a designated time.\n- **Week in Month**: Runs monthly during a specific week of the month \\(for example, the third week of each month\\), on designated days and at a designated time.\n- **Weekly**: Runs on a weekly basis, at a designated time and day of the week.\n- **Monthly**: Runs on a monthly basis, at a designated time and day of the month.\n- **Periodically**: Runs on a designated repeating interval.\n- **Once**: Runs for a single occurrence only.\n- **On Demand**: Runs immediately on demand.\n- **Business Calendar: Entry Start**: Runs on the starting entry dates for the business calendar that you select in the **Business Calendar** field. A scheduled job runs for the starting date of each of the business entries that you defined for the business calendar.\n\nFor example, if the business calendar represents a fiscal year, and the starting date of each entry is a fiscal month, the scheduled job runs on the first day of each month.\n\n- **Business Calendar: Entry End**: Runs for the ending date for the business calendar that you select in the **Business Calendar** field. This selection runs in the same manner as **Business Calendar: Entry Start**, but for the end dates of the associated business calendar entries.\n\n**Note:** When you select **Business Calendar: Entry Start** or **Business Calendar: Entry End**, you can apply an offset factor to schedule the job to run before or after the time span of the selected business calendar. If you select a business calendar and all its business calendar spans are in the past, the job would never run since that is an invalid configuration. To learn more, see the **Offset type** and **Offset** fields.\n\nTo learn more about creating and using business calendars and defining business calendar entries, see [Creating business calendars](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/business-calendars.md) and [Define business calendar entries](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/define-business-calendar-entries.md).\n\n |
| \n\nTime zone\n\n | \n\nTime zone to use with the **Time** field entry when you specify the time at which the scheduled job should run. Select a time zone entry:\n\n- **-None-**: Use the default time zone for the logged-in user who is creating the scheduled job.\n\nFor example, the scheduled job runs at 04:45 p.m. US/Pacific time if it’s the user's assigned time zone, and you enter `16:45` into the **Time** field.\n\n- **Use System Time Zone**: Use the default system time zone that is specified for the instance in which it runs.\n\nFor example, the scheduled job runs at 10:15 p.m. London time if Europe/London is the default system time zone for the instance, and you enter `22:15` in the **Time** field.\n\n- Actual time zone.\n\nFor example, the scheduled job runs at 1:30 p.m. in the US Eastern time zone if you select **US/Eastern**, and enter `13:30` in the **Time** field.\n\n |
| \n\nTime\n\n | \n\nTime of day at which the scheduled job should run, expressed in hours, minutes, and seconds on a 24-hour clock. The selection that you make in the **Time zone** field determines the time zone for this entry.\n\n |
| \n\nDay\n\n | \n\nDay on which the scheduled job should run.\n\n- If **Run** is set to **Weekly**, select the day of the week. For example, select Wednesday.\n- If **Run** is set to **Monthly**, select the day of the month. For example, select 25 for the 25th day of the month.\nThis field appears only if you select **Monthly** or **Weekly** in the **Run** field.\n\n |
| \n\nRepeat Interval\n\n | \n\nDuration of the repeat interval for each scheduled job execution. Enter the duration in the number of days, hours, or minutes. For example:\n\n- To run the scheduled job every four days, enter `04` in the **Days** field.\n- To run it every 26 hours, enter `26` in the **Hours** field.\n- If it should repeat at an interval of 13:30:25, enter `13` in the **Hours** field, and then enter `30` and `25` in the two unlabeled fields after it.\n\n\n |
| \n\nStarting\n\n | \n\nAllows you to define the beginning window of time when you would like your job to start running. The job will actually run at the time specified in **Run time**. Select the calendar date and time. The **Starting** field appears only if you select one of the following **Run** types in the **Run** field:- **Daily**\n- **Day and Month in Year**\n- **Day in Week in Month in Year**\n- **Monthly**\n- **Once**\n- **Periodically**\n- **Week in Month**\n- **Weekly**\nFor the run type **Periodically**, the **Starting** time is the date and time of the first scheduled job generation.\n\n |
| \n\nBusiness Calendar\n\n | \n\nBusiness calendar entry that you’re using to determine the business calendar start or end date for the scheduled job. This field appears only if you select **Business Entry: Start Date** or **Business Entry: End Date** in the **Time** field.\n\n |
| \n\nOffset type\n\n | \n\nType of time offset, if any, to apply to the business calendar that you selected for scheduling this job:\n\n- **Past**: Apply an offset factor to schedule the job to run before the start of the time span of the selected business calendar.\n- **Future**: Apply an offset factor to schedule the job to run after the end of the time span of the selected business calendar.\n- **--None--**: Don’t apply a time offset when scheduling this job.\nAdding an offset factor enables you to schedule the job to run before or after the formal time span that is defined in the business calendar for the following use cases:\n\n |
| \n\nOffset\n\n | \n\nAmount of time offset, expressed in days, hours, minutes, and seconds, to apply to the business calendar that you selected for scheduling this job. For example, if you want to schedule the job to start three days, 14 hours, 10 minutes, and 45 seconds before the business calendar start date, do the following actions:\n\n- Select **Past** in the **Offset type** field.\n- Enter **3** in the **Days** field.\n- Enter **14**, **10**, and **45** in the **Hours** field.\nThe **Offset Days** and **Hours** fields appear only if you select **Business Calendar: Entry Start** or **Business Calendar: Entry End** in the **Run** field, and **Past** or **Future** in the **Offset type** field.\n\n |
| \n\nPriority\n\n | \n\nNumerical priority for the scheduled job:\n\n- Set essential jobs to a priority value below 100.\n- Set nonessential jobs to a priority above 100.\n- If 70 percent or more of all scheduled jobs are **Overdue**, any jobs that are marked with a value above 100 don’t run.\n\n\n |
| \n\nConditional\n\n | \n\nWhen enabled, specify a scripted condition for generating the report.\n\n |
| \n\nOmit if no records\n\n | \n\nWhen enabled, empty reports are not distributed.\n\n |
| \n\nCondition\n\n | \n\nA conditional script that determines if a scheduled job should run. The last expression of the script should evaluate to a Boolean \\(true/false\\) value. This text box appears only if you select **Use conditions**. For more information about scripts on the ServiceNow platform, see [Scripts](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/scripts/c_Script.md).**Warning:** Conditional scripts for scheduled emails are executed in the sandbox. Therefore, function definitions aren't allowed. Some API calls and keywords are also not allowed. For more information, see Script sandbox property.\n\n |
| \n\nSubject\n\n | \n\nText that appears in the subject line of the distribution email.\n\n |
| \n\nIntroductory message\n\n | \n\n\\(Optional\\) Add a message to the report. If the report output type is Embedded PNG,\n\n- Use the tag `${report:png}` in the message body to position the report in the message. Otherwise, the report appears at the bottom of the message.\n- Use the tag `${report:include_with}` to position other reports included with the email. Otherwise, these reports appear at the bottom of the message.\n\n\n |
| \n\nType\n\n | \n\nReport output type. Graphical reports can be PNG or PDF files. List reports can be PDF, Excel, or CSV files.When scheduling a graphical report, select the output type **PDF** or **PDF-landscape** to include the chart grid data. When scheduling a List report, select output type **Excel** or **CSV**.\n\nSelect **Embedded PNG** to embed the report visualization in the body of the email. Large images are scaled to fit the email.\n\nFor more information, see the section Report output formats.\n\n**Note:** It is only possible to schedule multilevel pivot reports in PDF output.\n\n |
| \n\nZip output\n\n | \n\nWhen selected, the report is sent as a zip file attachment to the email.\n\n |
| \n\nInclude with\n\n | \n\nOne or more additional reports to include with the email. It is not possible to order the reports within the email. You can use the Search icon \\[Omitted image \"SearchIcon.png\"\\] Alt text: Search icon to locate the additional reports.\n\n |
| \n\nPage size \\(Multilevel pivot report only\\)\n\n | \n\nChoose from A3, A4, Letter, or Legal size. To specify a different paper size, select **Custom** and enter the **Page height** and **Page width** in pixels.\n\n |
| \n\nPage height \\(in pixels\\) \\(Multilevel pivot report only\\)\n\n | \n\nShows when **Page size** is set to **Custom**. For non-standard paper sizes, multiply the page height in inches by 72 and enter the value in this field.\n\n |
| \n\nPage width \\(in pixels\\) \\(Multilevel pivot report only\\)\n\n | \n\nShows when **Page size** is set to **Custom**. For non-standard paper sizes, multiply the page width in inches by 72 and enter the value in this field.\n\n |
\n