Using schedules and calendars
Summarize
Summary of Using schedules and calendars
Within the ServiceNow AI Platform, specific applications generate graphical calendar displays based on schedule pages. These schedule pages support daily, weekly, or monthly views and are integral to applications such as Project Management, Maintenance Schedules, Group On-Call Rotation, and Field Service Management.
Show less
Schedule pages are records containing scripts that determine the calendar's functionality and appearance. Due to the complexity and heavy scripting involved, it is recommended to use the default schedule pages provided in the base platform for most instances.
Accessing and Configuring Schedule Pages
Schedule pages can be accessed via System Scheduler > Schedules > Schedule Pages. Each schedule page record includes key fields such as:
- Name: Identifies the schedule page.
- Schedule type: A unique string used in the URL parameter
sysparmpagescheduletypeto access the schedule page. Alternatively, the schedule page can be accessed using thesysparmpagesysidparameter with the page’s unique system ID. - View Type: Choice between 'Calendars' or 'Schedule Pages', each displaying different field combinations.
- Description: Optional field for additional information.
- Init function name, HTML, Client script, Server AJAX processor: These scriptable fields are primarily used for Calendar type schedule pages to customize initialization, HTML content injection, client-side behavior, and server-side data retrieval.
Using Schedule Pages and Calendars
You can invoke a schedule page calendar using URLs with parameters, field decorations, or UI Actions linking to showschedule.do. The Schedule calendar enables creating, viewing, and editing events interactively.
Practical Importance for ServiceNow Customers
- Graphical Calendar Displays: Easily visualize schedules in multiple views for better management of projects, maintenance, on-call rotations, and field services.
- Customization: While default schedule pages suffice for most needs, advanced users can customize calendar behavior through client and server scripts, tailoring the display and data retrieval.
- Integration: Schedule pages support domain and holiday considerations, parent-child schedule relationships, and repeat patterns such as monthly scheduling.
Related Concepts and Tasks
- Creating holiday schedules for multiple regions
- Defining schedules with specific recurrence rules (e.g., fifth instance of a week date)
- Understanding domain support and parent-child schedules
- Using default schedules for rapid setup
Specific applications within the ServiceNow AI Platform generate graphical calendar displays based on schedule pages.
- Project Management
- Maintenance Schedules
- Group On-Call Rotation
- Field Service Management
- Because of the heavy degree of scripting involved in a schedule page, you should, for most instances, use the default schedule pages in the base platform.
- The schedule page uses a URL with a series of parameters attached to generate the graphical display.
- A schedule page controls calendar content (
cmn_schedule_page) record.
To access Schedule Pages, navigate to System Scheduler > Schedules > Schedule Pages. The Schedule Pages form provides the following fields:
| Field | Field Type | Description |
|---|---|---|
| Name | String | General name used to identity the current schedule page. |
| Schedule type | String | Schedule type is a string that is used to uniquely identity the schedule page
via the "sysparm_page_schedule_type" URI parameter. For example,
a schedule page could be accessed as follows: /show_schedule_page.do?sysparm_page_schedule_type=gantt_chart&sysparm_timeline_task_id=d530bf907f0000015ce594fd929cf6a4 Alternatively, you can access the schedule page can by setting the "sysparm_page_sys_id" URI parameter to the unique 32 character hexadecimal system identifier of the schedule page. |
| View Type | Choice | Each view type displays different field combinations. There are two options
available:
|
| Description | String | General description that provides additional information about the current schedule page. This field is not necessary. |
| Init function name | String | Note: The init function
name specifies the name of the JavaScript function to call inside the
Client script function for calendar type schedule pages.This functionality is only used by
Calendar type schedule pages. |
| HTML | String | Note: Jelly parses the
HTML field, which is a scriptable section. It then injects it into the display
page prior to the rest of the calendar. It can be used to pass in variables from
the server and define extra fields are necessary.This functionality is only used by
Calendar type schedule pages. |
| Client script | String | The client script is a scriptable section that allows for configuring options of the schedule page display. The API is different depending on the schedule page view type. |
| Server AJAX processor | String | Note: The Server AJAX
processor is specific to calendar type schedule pages that is used to return a set
of schedule items and spans that display.This functionality is only used by
Calendar type schedule pages. |