---
sourceDocument: Brazil API Reference
sourceDocumentLink: https://www.servicenow.com/docs/r/api-reference

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil API Reference

ft:clusterId :

    - crapiref

bundleId :

    - crapiref

workflow :

    - Creator


---

# Schedule pages

# Schedule pages {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read  
A schedule page is a record that contains a collection of scripts that allow for custom
generation of a calendar or timeline display.

Creation of timeline schedule pages requires understanding of the page/event flow and the
ability to write client and server side JavaScript.

## Schedule pages form {#ariaid-title2}

To access schedule pages, navigate to System SchedulerSchedulesSchedule Pages.
The form provides the following fields, depending upon the View Type selected:{#r_SchedulePagesForm__table_i4p_34j_lp__entry__3}

| Field | Field Type | Description |
|-|-|-|
| Name | String | General name that is used to identity the current schedule page. |
| Schedule type | String | The 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_type=gantt_chart&sysparm_timeline_task_id=d530bf907f0000015ce594fd929cf6a4` Alternatively, the schedule page can also be accessed by setting the "sysparm_page_sys_id" URI parameter to that of 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: * Calendars * Timelines {#r_SchedulePagesForm__ul_ynk_t4j_lp} |
| Description | String | General description that provides additional information about the current schedule page. This field is not necessary. |
| Init funciton name | String | Note: This functionality is only used by Calendar type schedule pages. The init function name specifies the name of the JavaScript function to call inside the Client script function for calendar type schedule pages. |
| HTML | String | Note: This functionality is only used by Calendar type schedule pages.The HTML field is a scriptable section that is parsed by Jelly and injected 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. |
| 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 and is discussed below. |
| Server AJAX processor | String | Note: This functionality is only used by Calendar type schedule pages.The Server AJAX processor is specific to calendar type schedule pages that is used to return a set of schedule items and spans to be displayed. |
[Table 1. Schedule pages form]

{#r_SchedulePagesForm__table_i4p_34j_lp}

## Timeline schedule pages {#ariaid-title3}

A Timeline Schedule Page is a specific record that contains configuration information
for displaying time based points and spans in a "timeline" like fashion.

The timeline schedule page references a script include that extends from the AbstractTimelineSchedulePage class to perform dynamic modification to the timeline based on different events and conditions. Both the
schedule page and the script include for timeline generation support customization and have a corresponding application programming interface (API).  
The following steps outline the series of events that occur when a timeline schedule page is accessed. Once the timeline has been loaded, all subsequent events, such as events resulting from timeline interaction (for example, moving a timeline span), follow the same logic described with the getItems event.

1. The client browser accesses a schedule page. The request is sent to the server.
2. The server interprets the schedule page HTTP request and obtains information about the specific schedule page from either of the following URI parameters:
   * sysparm_page_sys_id
   * sysparm_page_schedule_type
   {#c_Timelines__ul_egh_tqv_r3c}
3. The server returns an HTTP response that contains the client script information from the specified schedule page.
4. The client browser immediately parses the Client script section of the schedule page when loading the page and:
   * sets configuration and display options
   * registers event listeners
   {#c_Timelines__ul_o12_xqv_r3c}
5. With the getItems event:
   1. The client timeline makes an AJAX request to the corresponding script include for the event registered with getItems to retrieve the set of items and spans to display on the timeline.
   2. The server receives the request and executes the getItems code block inside the specified script include, which is an instance of the AbstractTimelineSchedulePage class. The server returns an XML document with TimelineItem objects.
   3. The client receives the AJAX response with the specified TimelineItem objects and appropriately displays them on the screen.
   {#c_Timelines__ol_plr_1rv_r3c}
{#c_Timelines__ol_jvf_kqv_r3c}

### Applications that use schedule pages to generate time lines

* Project Management
* Maintenance Schedules
* Group On-Call Rotation
* Field Service Management
{#c_Timelines__ul_nbs_srj_lp}

*[\>]: and then