[Index]

Model: relation/HcsTimeScheduleREL

Time Schedules

Full HTML Help

Overview

A time schedule includes a group of time periods. Time schedules are assigned to partitions to set up time-of-day call routing. Time schedules determine the partitions where calling devices search when they are attempting to complete a call during a particular time of day. Multiple time schedules can use a single time period.

Configure Time Schedules

This procedure assigns a time period to a time schedule.

Prerequisites:

Note

VOSS Automate provides one 'All the time' schedule. The 'All the time' schedule is a special, default time schedule that includes all days and hours, and cannot be deleted.

Perform these steps:

  1. Log in to the Admin Portal as a Provider, Reseller, or Customer administrator.

  2. Set the hierarchy path to the node where you want to create the new time schedule.

  3. Choose an appropriate option, based on your login:

  4. Choose an appropriate action:

  5. If the Network Device List popup window appears, select the NDL for the time schedule from the drop-down menu. The window appears when you are on a nonsite hierarchy node. If you are at a site hierarchy node, the NDL associated with the site is automatically used.

    Note

    The Network Device List drop-down only appears when a time schedule is added; it does not appear when you edit a time schedule.

  6. Enter a unique name for the new time schedule in the Name field, or modify the existing Name if desired. This field is mandatory. The name can comprise up to 50 alphanumeric characters. The name of the time schedule can contain any combination of spaces, periods (.), hyphens (-), and underscore characters (_).

  7. (Optional) Enter a description for the time schedule in the Description field.

  8. Click the Plus icon (+) to open the Time Periods form.

  9. From the Time Period drop-down box, choose a time period for the time schedule.

  10. Repeat Steps 8 and 9 to add another time period to the time schedule.

    Note

    • If multiple time periods are associated with a schedule where the time periods overlap, time periods with Day of Year settings take precedence over time periods with Day of Week settings. Day of Year is applicable when Year Start value is set and the End value is left blank.

      Example: If a Time Period configured for January 1 is configured as No Office Hours and another time period is configured for the same day of the week (for example, Sunday to Saturday) as 08:00 to 17:00, the time period for January 1 is used. In this example, No Office Hours takes precedence.

    • Time interval settings take precedence over No Office Hour settings for the same day of the year or day of the week.

      Example: One time period specifies for Saturday as No Office Hours. Another time period specifies Saturday hours of 08:00 to 12:00. In this example, the resulting time interval specifies 08:00 to 12:00 for Saturday.

    • If multiple time periods are associated with a schedule where the time periods overlap, time periods with Day of Week settings take precedence over time periods with Range of Days settings. Range of Days applies to when Year Start and End values are set, even if they are configured for the same day.

      Example: If a Time Period configured for Day of Week (for example, Sunday to Saturday) is configured as No Office Hours and another time period is configured for January 1 until December 31 as 08:00 to 17:00, the time period for Day of Week is used. In this example, No Office Hours takes precedence.

  11. To save the new time schedule, click Save, or to update time schedule, click Update.

  12. Repeat Steps 3 to 11 to configure another time schedule.

Next Steps

You cannot delete time schedules that partitions are using. Before deleting a time schedule that is currently in use, perform either or both of the following tasks:

Warning

Before you delete a time schedule, check carefully to ensure that you are deleting the correct time schedule. You cannot retrieve deleted time schedules. If you accidentally delete a time schedule, you must rebuild it.

This relation wraps the default CUCM Time Schedule element.

Model Details: relation/HcsTimeScheduleREL

Title Description Details
Name *
  • Field Name: name
  • Type: String
  • Cardinality: [1..1]
  • MaxLength: 50
Is Published TimeSchedule cannot be published if it has a todOwnerId assigned to it. Only Administrative Time Schedule can be published.
  • Field Name: isPublished
  • Type: Boolean
  • Cardinality: [0..1]
Time Schedule Category Default: Regular
  • Field Name: timeScheduleCategory
  • Type: String
  • Cardinality: [0..1]
  • Default: Regular
  • Choices: ["Regular", "Holiday or Vacation"]
Members
  • Field Name: members
  • Type: ["Object", "Null"]
  • Cardinality: [1..1]
Member
  • Field Name: member.[n]
  • Type: Array
  • Cardinality: [1..n]
Time Period Name *
  • Field Name: members.member.[n].timePeriodName
  • Type: String
  • Cardinality: [1..1]
Tod Owner Id Name
  • Field Name: todOwnerIdName
  • Type: ["String", "Null"]
  • Target: /api/device/cucm/User/choices/?field=userid&format=json&hierarchy=[hierarchy]&auth_token=%3D%3D%249rcuAo7pc3FVeUDd%24CTi5AMo1UxVr0pDe/VsHMDuJSKIZlWx15K9RBYKirglox4rq9SqBJGT/e1ikXV6Niel2sN6A1%2BQzfbVHiDS%2BDmQPxB96Vt0oLrcryKZk4s9t7ErTtixcc8yLLWXF%2B3aYyal4M166FYTOHOTUfQNoZ97n264FeD5vz%2BfLDH0xy47I8Wa1l1UvMV2w0/sB8a%2BqY7KmC%2BaCnVk36A9u9SnMdkJaZfkMLtSeKyowG//ed6LD7f7veYh%2B1XraJQ/BMOXuvVH3R1grHGgq9pyxBHWtk5TWYOXdOP3d7UUtMZVPX1dyuYQ/toiZsPMMvqhd%2BJrB76HNxRnY6McXcp8ffl/n/jua5IzrKNLPf%2B%2BNqhbQ/8lgikTfg9hVqoXRrqLevoE%2B6p7D%24%3D%3D
  • Target attr: userid
  • Target Model Type: device/cucm/User
  • Cardinality: [0..1]
  • Format: uri
  • Choices: []
Description
  • Field Name: description
  • Type: String
  • Cardinality: [0..1]
  • MaxLength: 255
Shadow
  • Field Name: shadow.[n]
  • Type: Array
  • Cardinality: [0..1]
Name *
  • Field Name: shadow.[n].name
  • Type: String
  • MaxLength: 1024