---
sourceDocument: Xanadu ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/platform-administration

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Domain support and schedules

# Domain support and schedules {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Domain separation is supported in schedules. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data. Activate the Domain Support \[com.glide.domain\] plugin to enable the domain
separation functionality for schedules.

## Support level: Basic {#domain-support-for-schedules__section_n2m_zxr_xkb}

{#domain-support-for-schedules__domain-sep-supported}  
* Business logic: Ensure that data goes into the proper domain for the application's service provider use cases.
* The application supports domain separation at run time. The domain separation includes separation from the user interface, cache keys, reporting, rollups, and aggregations.
* The owner of the instance must set up the application to function across multiple tenants.
{#domain-support-for-schedules__ul_yhr_g2j_xkb}

Sample use case: When a service provider (SP) uses chat to respond to a tenant-customer's
message, the customer must be able to see the SP's response.{#domain-support-for-schedules__p_lsc_nfg_h1c}

For more information on support levels, see [Application support for domain
separation](https://www.servicenow.com/docs/access?context=domain-separated-apps&version=xanadu&pubname=xanadu-platform-security&ft:locale=en-US).{#domain-support-for-schedules__p_msc_nfg_h1c}

## Overview {#domain-support-for-schedules__section_vdz_kjs_1kb}

The records in the Schedule \[cmn_schedule\], Schedule Page \[cmn_schedule_page\], and Timeline Page \[cmn_timeline_page\] tables have a defined domain.

* The child tables use the domain_master attribute to derive the domain from the parent table.
* You can find the domain_master attribute on the dictionary record for the respective table.
{#domain-support-for-schedules__ul_nzv_rqy_jjb}  
The following diagram illustrates the scope of domain separation in different schedule tables: Figure 1. Domain support for schedules

## Custom domain support implementations {#domain-support-for-schedules__section_pck_gsq_bbb}

Domain separation support does not automatically occur when you migrate
to a new release containing a custom implementation of domain
support for tables such as Schedule Entry \[cmn_schedule_span\]. This
action avoids changing any specific configurations that you may have
in place.  
To implement the base system domain support for schedules, a sys.script utility is provided. To run this utility, navigate to BackgroundScripts -- Background. The script is listed under the com.glide.schedules plugin as fix_schedule_domain_support.js.

* The utility attempts to add the Domain \[sys_domain\] column to the Schedule \[cmn_schedule\], Schedule Page \[cmn_schedule_page\], and Timeline page \[cmn_timeline_page\] tables.
* It then attempts to add the domain_master attribute to the Schedule Entry \[cmn_schedule_span\], Other Schedule \[cmn_other_schedule\], Timeline Sub Item \[cmn_timeline_sub_item\], and Timeline Page Span Style \[cmn_timeline_page_style\] tables.
* If the script finds existing records between a child and parent record that have differing domain, the script does not introduce the domain_master attribute to the child table.
{#domain-support-for-schedules__ul_w1t_nsy_jjb}  
For example, consider the relationship of the Schedule \[cmn_schedule\] (parent) and Schedule Entry \[cmn_schedule_span\] (child) tables. If the Domain \[sys_domain\] column is available on both tables in the upgrading instance, the utility must migrate to the base system implementation of domain support for schedules.

* If the script detects records where the child Schedule Entry \[cmn_schedule_span\] domain differs from its parent Schedule \[cmn_schedule\] domain, it stops executing and logs a warning message.
* If the script does not find differing records, it deactivates and limits read access to the Domain \[sys_domain\] and Domain Path \[sys_domain_path\] columns on the Schedule Entry \[cmn_schedule_span\] table.
* Finally, the script adds the domain_master=schedule attribute to the dictionary file for the Schedule Entry \[cmn_schedule_span\] table.

{#domain-support-for-schedules__ul_js5_rsy_jjb}  
Note:  
The domain_master attribute ensures that the child and parent record domains remain the same as the domain for the child that is derived from the specified reference field.
**Related concepts**   

* [Holidays](https://servicenow-prod.fluidtopics.net/_cQrm97jSjlXa34mz_mNCg "You can define each individual holiday as a schedule entry to create exceptions to existing schedules.")
* [Parent and child schedules](https://servicenow-prod.fluidtopics.net/8xlXhLrY1MPNmCM1Y~fF7Q "Schedules can have one of two parent-child relationships with other schedules.")  
**Related tasks**   

* [Create a holiday schedule for multiple regions](https://servicenow-prod.fluidtopics.net/hSxlerHYGQ_V4jteoSwnmg "You can create holiday schedules for multiple regions that follow the same work schedule but have different holidays.")
* [Define a schedule](https://servicenow-prod.fluidtopics.net/x_GlRiXKo7M7vUp04Z8flw "Configure schedules using schedule and schedule entry records.")
* [Schedule for the fifth instance of a week date](https://servicenow-prod.fluidtopics.net/mZH6X8GQiJeTmN6fIQBqOA "You can select a date that computes to the fifth instance of a weekday for a date near the end of a month for a repeating monthly schedule,")
* [Repeat a monthly schedule](https://servicenow-prod.fluidtopics.net/tjPFtps7JidQ5rriUx0NaA "Repeat a monthly schedule to reduce the amount of time required to define schedules and to provide consistency in scheduling.")  
**Related reference**   

* [Default schedules](https://servicenow-prod.fluidtopics.net/jxHK79vaUHNPIVz85_F0SQ "Default schedules are available in a base system.")
* [Using schedules and calendars](https://servicenow-prod.fluidtopics.net/s2dx9jQAsxywi6kPrnPnaA "Specific applications within the ServiceNow AI Platform generate graphical calendar displays based on schedule pages.")

*[\>]: and then